Versions Compared

Old Version 23

changes.mady.by.user Andrew Kennedy

Saved on

compared with

New Version 24

changes.mady.by.user keith wall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Publishing SNAPSHOT versions of Maven artefacts to the Apache repository after a successful nightly build

Issues

The initial testing of the CI configuration is being carried out using the qpid-java-build job only, until any issues are sorted out.

Currently, there seems to be a problem with the exclusion of various tests. For example, AcknowledgeAfterFailoverOnMessageTest should not be running under the default test profile.

This appears to be caused by spaces in the job name. A copy of the original job named qpid-java-build works as expected.

All JMX based tests are failing on Solaris instances. The operational profiles have been locked to Ubuntu Hudson instances to try and fix this.

No Format

java.rmi.server.ExportException: internal error: ObjID already in use
	at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:169)
	at sun.rmi.transport.Transport.exportObject(Transport.java:74)
	at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:229)
	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
	at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
	at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190)
	at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
	at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68)
	at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222)
	at org.apache.qpid.server.management.JMXManagedObjectRegistry.start(JMXManagedObjectRegistry.java:218)
	at org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:294)
	at org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:154)
	at org.apache.qpid.test.utils.QpidBrokerTestCase.startBroker(QpidBrokerTestCase.java:472)
	at org.apache.qpid.test.utils.QpidBrokerTestCase.startBroker(QpidBrokerTestCase.java:403)
	at org.apache.qpid.test.utils.QpidBrokerTestCase.setUp(QpidBrokerTestCase.java:301)
	at org.apache.qpid.server.security.acl.AbstractACLTestCase.setUp(AbstractACLTestCase.java:120)
	at org.apache.qpid.server.security.acl.ExternalACLJMXTest.setUp(ExternalACLJMXTest.java:57)
	at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:234)
	at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:120)

Monitoring

I propose creation of a new mailing list, qpid-build@apache.org which would receive a copy of all output from every CI build. Additionally, the results of failing builds should be mailed to committers that checked in the breaking changes, and a nightly (or weekly) summary from the release and/or interop test builds should be sent to the qpid-dev list.

...