Closed Bug 525007 Opened 15 years ago Closed 15 years ago

mac debug everythingelse is red most of the time

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dbaron, Assigned: nthomas)

References

Details

The Mac debug everythingelse machine is now red most of the time (I think last week it was only red about a quarter of the time). The last two failures have both been the following build step failing: 'bash ../tools/buildfarm/utils/installdmg.sh ...' failed though there have also been other failures (which may or may not need to be split into different bugs; I'm starting with this one).
I see four builds with the unpack error, and it looks like they're all on bm-xserve17.
Assignee: nobody → nthomas
Priority: -- → P2
Ok, this definitely looks like it's slave specific. The "OS X 10.5.2 mozilla-central test debug everythingelse" builds starting at * Wed Oct 28 13:39:41 2009 * Wed Oct 28 07:39:13 2009 * Wed Oct 28 06:31:21 2009 * Tue Oct 27 09:39:53 2009 all failed to unpack the dmg. Taking the 13:39 dmg and manually calling hdiutil attach ... works fine on bm-xserve19, which is nominally equivalent spec. There are also a couple of failures in "OS X 10.5.2 mozilla-central test mochitests-N/5" where N = 2 and 4.
Whatever the problem was, it seems to have gone away. I wonder if we might not have been killing processes properly if the build failed because of hitting the log size limit? (Going over the log size limit was fixed by bug 525100.)
Yeah, I left bm-xserve17 disconnected from the buildbot master so it couldn't re-offend. I doubt it can be anything to do with logs because the runs that were failing were packaged unit tests, and we reboot the slaves after every job. I've dug around on bm-xserve17 and can't find anything out of the ordinary, so we'll reimage it to get back to a good state.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Bug 525398 for that.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.