2014-09-06 13:52 GMT+04:00 Bill Barker <billbar...@apache.org>: > To whom it may engage... > > This is an automated request, but not an unsolicited one. For > more information please visit http://gump.apache.org/nagged.html, > and/or contact the folk at gene...@gump.apache.org. > > Project tomcat-trunk-test-bio has an issue affecting its community > integration. > This issue affects 1 projects. > The current state of this project is 'Failed', with reason 'Build Failed'. > For reference only, the following projects are affected by this: > - tomcat-trunk-test-bio : Tomcat 8.x, a web server implementing the Java > Servlet 3.1, > ... > > > Full details are available at: > > http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-bio/index.html >
For a record, as Gump overwrites old log files on reruns: The only failure here is Test org.apache.tomcat.util.threads.TestLimitLatch FAILED [[[ Testsuite: org.apache.tomcat.util.threads.TestLimitLatch Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.753 sec Testcase: testTenWait took 2.373 sec FAILED No threads should be waiting junit.framework.AssertionFailedError: No threads should be waiting at org.apache.tomcat.util.threads.TestLimitLatch.testTenWait(TestLimitLatch.java:92) Testcase: testOneThreadNoWait took 0.151 sec Testcase: testNoThreads took 0 sec Testcase: testOneRelease took 0.101 sec Testcase: testOneThreadWaitCountUp took 0.101 sec ]]] My guess is that this is an occasional timing issue. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
