Closed
Bug 877722
Opened 12 years ago
Closed 12 years ago
tegra recovery
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhopkins, Unassigned)
References
Details
No description provided.
The following tergas have been re-imaged: tegra-103.build.mtv1.mozilla.com is alive tegra-082.build.mtv1.mozilla.com is alive tegra-056.build.mtv1.mozilla.com is alive tegra-102.build.mtv1.mozilla.com is alive tegra-085.build.mtv1.mozilla.com is alive tegra-219.build.mtv1.mozilla.com is alive tegra-035.build.mtv1.mozilla.com is alive tegra-200.build.mtv1.mozilla.com is unreachable tegra-307.build.mtv1.mozilla.com is alive tegra-328.build.mtv1.mozilla.com is alive tegra-348.build.mtv1.mozilla.com is alive tegra-309.build.mtv1.mozilla.com is alive tegra-282.build.mtv1.mozilla.com is alive tegra-322.build.mtv1.mozilla.com is alive tegra-276.build.mtv1.mozilla.com is alive tegra-313.build.mtv1.mozilla.com is alive tegra-114.build.mtv1.mozilla.com is alive We were unable to locate tegra 200.
Tegra-200 has been re-imaged. PING tegra-200.build.mtv1.mozilla.com (10.250.50.110): 56 data bytes 64 bytes from 10.250.50.110: icmp_seq=0 ttl=63 time=5.352 ms 64 bytes from 10.250.50.110: icmp_seq=1 ttl=63 time=5.275 ms
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•