Closed Bug 817995 Opened 12 years ago Closed 12 years ago

tegra recovery

Categories

(Infrastructure & Operations :: DCOps, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Unassigned)

References

Details

We have another batch of tegras to recover.
Blocks: tegra-039
Blocks: tegra-046
Blocks: tegra-090
Blocks: tegra-076
Blocks: tegra-110
Blocks: tegra-113
Blocks: tegra-179
colo-trip: --- → mtv1
Blocks: tegra-174
Blocks: tegra-304
Blocks: tegra-293
Blocks: tegra-294
Blocks: tegra-295
Blocks: tegra-296
Blocks: tegra-269
Blocks: tegra-192
Blocks: tegra-258
Blocks: tegra-307
Blocks: tegra-309
Blocks: tegra-311
Blocks: tegra-317
Blocks: tegra-319
Blocks: tegra-321
Blocks: tegra-325
Blocks: tegra-330
Blocks: tegra-332
Blocks: tegra-338
Blocks: tegra-343
Blocks: tegra-347
Blocks: tegra-365
Blocks: tegra-040
Blocks: tegra-052
Blocks: tegra-056
Blocks: tegra-072
Blocks: tegra-074
Blocks: tegra-079
Blocks: tegra-084
Blocks: tegra-089
Blocks: tegra-093
Blocks: tegra-100
Blocks: tegra-104
Blocks: tegra-141
Blocks: tegra-159
Blocks: tegra-187
All tegra's are pingable.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
tegra-365 returned 1 tegra-343 returned 1 tegra-332 returned 1 tegra-320 returned 1 tegra-319 returned 1 tegra-311 returned 1 tegra-309 returned 1 tegra-307 returned 1 tegra-304 returned 1 tegra-296 returned 1 tegra-295 returned 1 tegra-293 returned 1 tegra-056 returned 1 This was the return code after fresh runs of verify.py for all those devices. I'll get a new bug with next-steps/asks on file soon.
Alias: tegra-recovery
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.