On 23/05/2014 21:00, Sylvain Laurent wrote: > Hello all, > > In the last couple of days, several buildbot runs failed because of > intermittent failures in TestStuckThreadDetectionValve. > By following links provided in buildbot emails or the ones in > http://ci.apache.org/builders/tomcat-trunk , I arrived in the large stdio > file of the failing builds, for example > http://ci.apache.org/builders/tomcat-trunk/builds/104/steps/compile_1/logs/stdio > > In such a file, TestStuckThreadDetectionValve was marked FAILED, with a line > that said : > [junit] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 17.436 sec > > So there was 1 failure, but I could not figure out on which test method it > was, not what the failure was. > > After much time lost, I figured out that part of the test output was missing > from the stdio and is actually sent to individual files like > http://ci.apache.org/projects/tomcat/tomcat8/1596888/TEST-org.apache.catalina.valves.TestStuckThreadDetectionValve.NIO.txt > > Would it be possible to have assertion failures in stdio too ?
No need. > I could not find any link to such individual files, actually I had to "guess" > the URL by deriving a link provided by Konstantin a couple of days ago... Or > did I miss something ? Again, the buildbot is placing those files in the incorrect location. Once the correct location is used, a directory listing will be available. > I also came accross this page > http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-nio/ that > looked promising to help me find the failure message but could not find any > failure. Until I realized Gump is a different CI process than buildbot. Why > are there 2 different ones ? Why not use multiple CI systems? You increase your chances of detecting issues. We have certainly had issues that only one of the systems has found. Also, Gump has a slightly different purpose which is to check for interoperability between components. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
