So something somewhere is writing to stdout. I would suggest making the test suite redirect go through a pair of InputStream/OutputStream proxies which would hex dump all data to private files for subsequent review.
Gregg Wonderly On Jun 12, 2014, at 5:50 AM, Peter Firmstone <j...@zeus.net.au> wrote: > The usual suspects for build failures on Jenkins are ClassDep and ports in > use. Haven't seen any concurrency failures lately. > > However I came accross an interesting test failure recently: > > https://builds.apache.org/view/M-R/view/River/job/river-PolicySecurityLoaderUrlTests/10/ > > This error is produced identically by 5 tests in this particular test run, > but I have not been able reproduce it: > > [java] ----------------------------------------- > [java] com/sun/jini/test/impl/start/ActivateWrapperRegisterBadImplClass.td > [java] Test Failed: Test Failed: com.sun.jini.qa.harness.TestException: > Unexpected Exception; nested exception is: > [java] Problem creating service for net.jini.event.EventMailbox; > nested exception is: > [java] Failed to start the shared nonactivatable group; nested > exception is: > [java] NonActivatableGroupAdmin: Failed to exec the group; nested > exception is: > [java] invalid stream header: 4572726F > [java] > [java] ----------------------------------------- > > > The test suite redirects the System.in System.out streams to communicate with > a subprocess, where the exception occurs. > > Interestingly the invalid stream header, when converted from hex to ascii > reads: > > Erro > > Regards, > > Peter.
