Closed Bug 919011 (panda-0745) Opened 11 years ago Closed 11 years ago

panda-0745 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
Android
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

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

Nothing but RETRY since September 10th.
Depends on: 902657
recovered by "panda-recovery" bug 902657
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Hasn't take a job in months, pdu reboot didn't help.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
its stuck in "start_self_test" with no log in lifeguard. :dustin, :dividehex any clue on next steps for us here? (both code wise, for why it got stuck, and sanity wise for the panda itself)
Flags: needinfo?(jwatkins)
Flags: needinfo?(dustin)
I don't know what a pdu reboot entails for a panda (comment 3), but the fix is probably to do a forced self-test. As for why it got stuck there, it's hard to tell without logging.
I forced state to troubleshooting and then started the selftest. It passed selftest but still not sure why it got stuck in state limbo in the first place. Seems like a transient mozpool issue rather than a pandaboard issue.
Flags: needinfo?(jwatkins)
assuming all-is-well now then.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Flags: needinfo?(dustin)
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.