Closed Bug 732878 (tegra-075) Opened 13 years ago Closed 12 years ago

tegra-075 problem tracking

Categories

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

ARM
Android

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

()

Details

I was seriously thinking about suggesting retirement instead, because typical green rates appear to be between 80-90% and it has been green 48.5% of its last 200 runs, but abusing buildapi to get back to early January, it looks like once upon a time it wasn't quite so much a cranky and defective old Tegra.
Stopped it.
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Assignee: armenzg → nobody
Depends on: 732966
Priority: -- → P3
Alias: tegra-075
Status: ASSIGNED → NEW
Summary: Please disable tegra-075 and enroll it in tegra recovery → tegra-075
Whiteboard: [buildduty]
back in production
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Summary: tegra-075 → tegra-075 problem tracking
[00] tegra-075.build.mtv1:PING is CRITICAL: PING CRITICAL - Packet loss = 100%
Status: RESOLVED → REOPENED
Depends on: 750787
Resolution: FIXED → ---
According to the dashboard (http://mobile-dashboard.pub.build.mozilla.org/tegra-075_status.log) this was down for over 12 hours, but has recovered as of now... Not sure what happened, but resolving for the moment.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
No longer depends on: 750787
Resolution: --- → FIXED
tegra-075.build.mtv1:PING is CRITICAL: PING CRITICAL - Packet loss = 100% Log looks like it started on the 2nd, though I don't really remember nagios screaming that long, maybe someone downtimed it, rather like I'm about to only without bothering to reopen the bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 783961
PDU cycle did not bring this back.
This tegra did not come back up, DOA.
Sounds like it needs to be removed from our configs, etc. Callek, can you do that?
Assignee: nobody → bugspam.Callek
Depends on: 786966
Whiteboard: [buildduty]
removed from our code in 786966, marked as decom in slavealloc just now.
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Assignee: bugspam.Callek → nobody
QA Contact: armenzg → bugspam.Callek
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.