Closed
Bug 719326
Opened 13 years ago
Closed 13 years ago
Run disk diagnostics on w32-ix-slave30
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: coop)
Details
(Whiteboard: [buildduty][badslave?][hardware])
If you've forgotten (it's been more than a month since the last round of this game), we wait a few weeks, then if I haven't been heard from again it's WFM, otherwise you say "check memory and reimage" and relops says "yeah, here's your reimage, if it breaks again we'll send it back to iX."
+++ This bug was initially created as a clone of Bug #686131 +++
https://tbpl.mozilla.org/php/getParsedLog.php?id=8655524&tree=Mozilla-Inbound
WINNT 5.2 mozilla-inbound build on 2012-01-18 19:12:19 PST for push a904454ebfbb
cd nss; make -j1 libs
0 [main] make 3960 open_stackdumpfile: Dumping stack trace to make.exe.stackdump
make[6]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build/security/nss/lib'
make[5]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build/obj-firefox/security/manager'
make[4]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build/obj-firefox'
make[3]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build/obj-firefox'
make[2]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build/obj-firefox'
make[1]: Leaving directory `/e/builds/moz2_slave/m-in-w32/build'
/bin/sh: line 1: 3960 Segmentation fault (core dumped) make -j1 -C $directory libs
Comment 1•13 years ago
|
||
Disabled in slavealloc.
Assignee | ||
Comment 2•13 years ago
|
||
Need someone to check the disk on this slave. It may need a new disk or a return to ix for repair.
Assignee: nobody → server-ops-releng
Component: Release Engineering → Server Operations: RelEng
QA Contact: release → zandr
Summary: make.exe crashing intermittently on w32-ix-slave30 → Run disk diagnostics on w32-ix-slave30
Updated•13 years ago
|
Assignee: server-ops-releng → mlarrain
colo-trip: --- → scl1
Updated•13 years ago
|
Priority: P4 → P3
Comment 3•13 years ago
|
||
Ran the SMART test on the machine and it completed without errors. I can throw ubcd on it and run some deeper scans if you guys want me to.
Status: NEW → ASSIGNED
Priority: P3 → P4
Comment 4•13 years ago
|
||
Reassigning to releng unless they need to give it back for more testing.
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Assignee | ||
Comment 5•13 years ago
|
||
Taking until we decide what to do with this box: replacement, decommission, ...
Assignee: nobody → coop
Priority: P4 → P3
Comment 6•13 years ago
|
||
We can have iX take the machine for debugging, but we've been unable to find issues with it.
Reporter | ||
Comment 7•13 years ago
|
||
If we're still talking about just the failure from comment 0, um, "put back in service..."?
make.exe crashed, once. Joey's protestations about how mature and stable make is aside, that's make.EXE, brought to you by msys. When I said "we wait a few weeks, then if I haven't been heard from again it's WFM" I meant it - I would have left it in service, waited to see if it was crashing more than once a month, and if not just shrugged and said "msys" in a scornful way, just like with the circular directory structure.
Assignee | ||
Comment 8•13 years ago
|
||
(In reply to Phil Ringnalda (:philor) from comment #7)
> If we're still talking about just the failure from comment 0, um, "put back
> in service..."?
>
> make.exe crashed, once. Joey's protestations about how mature and stable
> make is aside, that's make.EXE, brought to you by msys. When I said "we wait
> a few weeks, then if I haven't been heard from again it's WFM" I meant it -
> I would have left it in service, waited to see if it was crashing more than
> once a month, and if not just shrugged and said "msys" in a scornful way,
> just like with the circular directory structure.
OK, I've put it back in service.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•