Closed Bug 399641 Opened 17 years ago Closed 17 years ago

qm-win2k3-01 is choking on stuck processes

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rflint, Assigned: bhearsum)

Details

We did a clobber build this afternoon and now qm-win2k3-01 is down in flames, can someone do the Heimlich?
Assignee: server-ops → mrz
Forced a rebuild, will watch.

Error showed :
failed
compile
Page did some work and then showed "failed compile" - I don't know what the recovery steps for that are.  Have paged build.
Rebooted the machine. For future reference, this document shows support instructions: http://wiki.mozilla.org/Buildbot/IT_Unittest_Support_Document
Assignee: mrz → bhearsum
Component: Server Operations: Tinderbox Maintenance → Testing
Product: mozilla.org → Core
Version: other → unspecified
Status: NEW → ASSIGNED
1) Talked to mrz after being paged. This is a QA machine, not a build machine.
I dont even have login access to machine (no LDAP on this machine.)

2) Talked to bhearsum. He's rebooting it now.
I ran through those but nothing there talked about "failed compile".  Which step should I have jumped to?
Step #2 should've been followed. If #1 doesn't work you should try #2, if #2 doesn't work you should try #3.

I apologize for the ambiguity, I'm updating the document to make this clear.
It's gone green.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: justin → release
Version: unspecified → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.