Closed Bug 745358 (tegra-149) Opened 12 years ago Closed 10 years ago

tegra-149 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

(
URL
)

Details

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

It used to be just fine, but now it's at 13 reds in a row, every one that I've seen being the bug 686084 "just sits there doing nothing until it times out on the first step that tries to touch the tegra."
tegra-149 renamed to offline-149 and taken offline
Depends on: 744687
Whiteboard: [buildduty][capacity][buildslaves]
restarted tegra-149
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
https://secure.pub.build.mozilla.org/buildapi/recent/tegra-149 - 8 reds in a row and building momentum.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Please disable tegra-149 and enroll it in tegra recovery → tegra-149 problem tracking
ran stop_cp.sh on it
Depends on: 783961
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
https://secure.pub.build.mozilla.org/buildapi/recent/tegra-149 - 17 reds in a row and building momentum.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
stop_cp.sh run will need a reimage Has flaked a lot lately so also please replace SDCard
Depends on: 788367
SD card replaced.
SUTAgent deploy brought it back from the grave, and so far it's doing okay.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Seeing Aurora rc2 crashes that only occur on this tegra.
https://tbpl.mozilla.org/php/getParsedLog.php?id=20660078&tree=Mozilla-Aurora
https://tbpl.mozilla.org/php/getParsedLog.php?id=20639701&tree=Mozilla-Aurora
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://tbpl.mozilla.org/php/getParsedLog.php?id=20814858&tree=Mozilla-Inbound

Please can this tegra be taken out of production.
Severity: normal → blocker
I think I disabled this slave. I followed these instructions: https://wiki.mozilla.org/ReleaseEngineering:How_To:Android_Tegras#Disable_a_tegra

And then manually killed the pid from twistd.pid.
Severity: blocker → normal
Depends on: 858134
back in production
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Monday, October 14, 2013 8:44:25 PM
Status: RESOLVED → REOPENED
Depends on: 944498
Resolution: FIXED → ---
swaped sd card, flashed and reimaged
swaped sd card, flashed and reimaged
Down again already :(
Depends on: 949447
Whoops, my bad! It's actually back up!
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
No longer depends on: 949447
Resolution: --- → FIXED
Depends on: 949447
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
handled in last recovery on Dec 16.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 974917
Resolution: FIXED → ---
sd card replace, tegra flashed and reimaged.

[vle@admin1a.private.scl3 ~]$ fping tegra-149.tegra.releng.scl3.mozilla.com
tegra-149.tegra.releng.scl3.mozilla.com is alive
Depends on: 971859
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 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.