Bug 838436 (tegra-368)

tegra-368 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
P3
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Callek, Assigned: jhopkins)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

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

Attachments

(2 attachments)

(Reporter)

Description

5 years ago
No jobs taken on this device for > 3 week (< 6 weeks)
(Reporter)

Comment 1

5 years ago
(mass change: filter on tegraCallek02reboot2013)

I just rebooted this device, hoping that many of the ones I'm doing tonight come back automatically. I'll check back in tomorrow to see if it did, if it does not I'll triage next step manually on a per-device basis.

---
Command I used (with a manual patch to the fabric script to allow this command)

(fabric)[jwood@dev-master01 fabric]$  python manage_foopies.py -j15 -f devices.json `for i in 021 032 036 039 046  048 061 064 066 067 071 074 079 081 082 083 084 088 093 104 106 108 115 116 118 129 152 154 164 168 169 174 179 182 184 187 189 200 207 217 223 228 234 248 255 264 270 277 285 290 294 295 297 298 300 302 304 305 306 307 308 309 310 311 312 314 315 316 319 320 321 322 323 324 325 326 328 329 330 331 332 333 335 336 337 338 339 340 341 342 343 345 346 347 348 349 350 354 355 356 358 359 360 361 362 363 364 365 367 368 369; do echo '-D' tegra-$i; done` reboot_tegra

The command does the reboot, one-at-a-time from the foopy the device is connected from. with one ssh connection per foopy
(Reporter)

Updated

5 years ago
Depends on: 838687
(Reporter)

Comment 2

5 years ago
Back from recovery
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
40 days, 19:47:17 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 858134
(Reporter)

Updated

5 years ago
Depends on: 865749
(Reporter)

Comment 4

5 years ago
Sending this slave to recovery
-->Automated message.
Depends on: 889567
(Reporter)

Comment 5

5 years ago
Asked for sdcard swap as well
(Reporter)

Updated

5 years ago
Depends on: 892096
(Reporter)

Comment 6

5 years ago
_still_ has a bad sdcard... recommend decom

tegra-368 -  not running -    enabled - 'Remote Device Error: unable to write to sdcard'
(In reply to Justin Wood (:Callek) from comment #6)
> _still_ has a bad sdcard... recommend decom

Should I proceed with decommission?
Flags: needinfo?(bugspam.Callek)
(Reporter)

Comment 8

5 years ago
Yes, lets kill it, with thermite please so we aren't tempted to plug it back in.
Flags: needinfo?(bugspam.Callek)
(Assignee)

Comment 9

5 years ago
Requested decomm in bug 900507
(Assignee)

Updated

5 years ago
Depends on: 900507
Product: mozilla.org → Release Engineering
(Assignee)

Comment 10

5 years ago
Created attachment 796643 [details] [diff] [review]
[buildbot-configs] add tegra-368 to decommissioned tegras list
Attachment #796643 - Flags: review?(kmoir)
(Assignee)

Comment 11

5 years ago
Created attachment 796644 [details] [diff] [review]
[tools] set foopy to None for tegra-368
Attachment #796644 - Flags: review?(kmoir)

Updated

5 years ago
Attachment #796643 - Flags: review?(kmoir) → review+

Updated

5 years ago
Attachment #796644 - Flags: review?(kmoir) → review+
(Assignee)

Comment 12

5 years ago
Comment on attachment 796643 [details] [diff] [review]
[buildbot-configs] add tegra-368 to decommissioned tegras list

https://hg.mozilla.org/build/buildbot-configs/rev/47ebb40b4709
Attachment #796643 - Flags: checked-in+
(Assignee)

Comment 13

5 years ago
Comment on attachment 796644 [details] [diff] [review]
[tools] set foopy to None for tegra-368

https://hg.mozilla.org/build/tools/rev/a31ced7e9957
Attachment #796644 - Flags: checked-in+
(Assignee)

Updated

5 years ago
Assignee: nobody → jhopkins
(Assignee)

Comment 14

5 years ago
In production.
(Assignee)

Updated

5 years ago
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.