On 23 mai 2014, at 22:04, Mark Thomas <[email protected]> wrote: > On 23/05/2014 21:00, Sylvain Laurent wrote: >> >> Would it be possible to have assertion failures in stdio too ? > > No need. why not ? this would avoid having to jump to different files to find the culprit of a failed build...
> >> 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. ok, I guess this is in the hands of infra team ? > >> 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. I also saw in http://tomcat.apache.org/ci.html#Jenkins a link to an experimental tomcat7 build by Jenkins but this does not seem to work. Are there plans to add a 3rd CI system ? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
