Closed Bug 786332 (tegra-120) Opened 12 years ago Closed 11 years ago

tegra-120 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

()

Details

(Whiteboard: [buildduty])

Needs recovery
Whiteboard: [buildduty]
Back in production.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
[foopy118.build.mozilla.org] run: echo "disable please" > ./disabled.flg [OK] Stopped tegra-120
Sending this slave to recovery -->Automated message.
Depends on: 889567
Successfully recovered.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
QA Contact: other → armenzg
Status: RESOLVED → REOPENED
Depends on: 974917
Resolution: FIXED → ---
SD card replaced, tegra reimaged and flashed. [vle@admin1a.private.scl3 ~]$ fping tegra-120.tegra.releng.scl3.mozilla.com tegra-120.tegra.releng.scl3.mozilla.com is alive
Depends on: 971859
Power cycled, waited a day. error.flg: Automation Error: Unable to connect to device after 5 attempts SD card reformat failed: $>exec newfs_msdos -F 32 /dev/block/vold/179:9 newfs_msdos: /dev/block/vold/179:9: No such file or directory return code [1]
Looking at the job history, this tegra only does about 1 job per day (callek says it's basically dead but we continually try and reboot it so that's enough to get some work out of it). Since it's green, we'll just leave it be.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 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.