Not sure what is going on here but there is a bustage before the build is finished. make: Entering directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir/modules/libimg' make: Entering directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir/modules/libimg/png' make: Leaving directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir/modules/libimg/png' make: Leaving directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir/modules/libimg' NEXT ERROR make: *** No rule to make target `png.obj', needed by `png.lib'. Stop. make: *** [libs] Error 2 make: Leaving directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir' make: Leaving directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir' make: Leaving directory `/e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build/objdir' make: *** [libs_tier_gecko] Error 2 make: *** [tier_gecko] Error 2 make: *** [default] Error 2 make: *** [build] Error 2 program finished with exit code 2 elapsedTime=367.172000
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1266624298.1266624895.23409.gz WINNT 5.2 mozilla-1.9.1 unit test [busted] Started 16:04, finished 16:15
What confuses me is that the unit test run http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1266624298.1266624895.23409.gz started _before_ the two builds http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1266624304.1266628999.2690.gz and http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1266624304.1266632833.13910.gz on the second bustage.
This just happened again: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1266802904.1266803283.18010.gz WINNT 5.2 mozilla-1.9.1 unit test on 2010/02/21 17:41:44 s: win32-slave52 make: *** No rule to make target `png.obj', needed by `png.lib'. Stop.
So it looks to me that the last three builds for "WINNT 5.2 mozilla-1.9.1 unit test" were all on win32-slave52, and all burned. The first one was a clobber, but the hey, I set another clobber and set it to run again.
Fixed by that clobber, so lets put this down to the build slave getting into a confused state. A genuine build system error would have been hitting all the nightly builds too. Noticed along the way that the weekly periodic clobbers were not being reported properly, bug 547641 for that.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.