On Monday, May 14, 2012 08:23:04 PM Anthony Liguori wrote: > On 05/14/2012 08:03 PM, q...@buildbot.b1-systems.de wrote: > > The Buildbot has detected a new failure on builder default_i386_rhel61 > > while building qemu.> > > Full details are available at: > > http://buildbot.b1-systems.de/qemu/builders/default_i386_rhel61/builds/ > >263> > > Buildbot URL: http://buildbot.b1-systems.de/qemu/ > > > > Buildslave for this Build: kraxel_rhel61_32bit > > > > Build Reason: The Nightly scheduler named 'nightly_default' triggered > > this build Build Source Stamp: [branch master] HEAD > > Blamelist: > > > > BUILD FAILED: failed test > > > > sincerely, > > > > -The Buildbot > > Did something change in buildbot recently? I'm having a hard time > interpreting what's going on here.
Few weeks ago we introduced xen 4.0, xen 4.1 and xen-unstable buildbot- factories / build-slaves. And the buildbot naster got restarted. But no other changes I am aware of from buildbot master site ... This one looks interesting: http://buildbot.b1-systems.de/qemu/builders/default_s390 Test runs passed with 9f3484, 94d19 - at least tow times. And failed immeditally with f4f7d. The tests get aborted due to a timeout of the testsuite - they expire the 1200 seconds limit (buildslave testdriver is setting this limit). Before f4f7d the default_s390 passed in approx. 9 seconds the testsuite. Since a lot of other slaves - but not all - timeout in the testsuite step with f4f7d there seems to be a infinite loop somehow or something blocking the testsuite. Maybe the last testcase: check-qtest-sparc64 does not finish in time? Best Regards, Daniel -- Daniel Gollub Linux Consultant & Developer Tel.: +49-160 47 73 970 Mail: gol...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: This is a digitally signed message part.
