Closed Bug 882686 (bld-lion-r5-051) Opened 11 years ago Closed 7 years ago

bld-lion-r5-051 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslaves][capacity])

Can't create directories in tmpdir, fails make check, needs reimage.
disabled in slavealloc
No longer blocks: 880003
Back in production.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Was ping down -- had to reboot via PDU info in inventory
went down, trying pdu reboot
No longer blocks: 874642
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 890324
It's taking jobs
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
The "input/output error" in https://tbpl.mozilla.org/php/getParsedLog.php?id=35568331&tree=Maple and https://tbpl.mozilla.org/php/getParsedLog.php?id=35571526&tree=Mozilla-Inbound say it's not happy about its disk. Disabled in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 983237
Reenabled in slavealloc, rebooted.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
https://tbpl.mozilla.org/php/getParsedLog.php?id=37971807&tree=Mozilla-Aurora - again, input/output error, though in fact you can also get that by having defective memory tell lies about what was read, rather than by having a defective disk deliver bad data.
https://tbpl.mozilla.org/php/getParsedLog.php?id=38204698&tree=Mozilla-Inbound - "clang: error: unable to execute command: Bus error: 10" Disabled in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
QA Contact: armenzg → bugspam.Callek
Depends on: 1015415
Reluctantly reenabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
And redisabled for exactly the same sort of failures.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reenabled and rebooted to see how the new logic board fares.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Disabled for suspected bad disk, see bug 1052454 comment 6.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Huh, look at that, I said it had disk trouble in March. Reenabled and rebooted to see how it does with its finally new disks.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
FWIW: filed bug 1101059 for an issue on this builder ("Couldn't clobber properly, bailing out.")
Depends on: 1101059
Can't clobber again, at least twice in the last two days, disabled. Wouldn't think there'd be much left of this one unreplaced, other than the power supply and the case.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Back online after been re-imaged.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Priority: P3 → --
Back online after re-image.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.