Closed
Bug 807663
Opened 13 years ago
Closed 13 years ago
tegra-recovery
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
No description provided.
Updated•13 years ago
|
Assignee: server-ops-releng → server-ops-dcops
Component: Server Operations: RelEng → Server Operations: DCOps
Comment 1•13 years ago
|
||
Below are the Tegra's that were reimaged and are now pingable.
--- tegra-349.build.mtv1.mozilla.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.930/6.059/6.875/0.824 ms
--- tegra-218.build.mtv1.mozilla.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.725/6.552/9.815/2.079 ms
--- tegra-133.build.mtv1.mozilla.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.937/5.730/6.978/0.860 ms
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•13 years ago
|
Alias: tegra-recovery
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•