Closed Bug 934493 Opened 11 years ago Closed 11 years ago

tegra recovery

Categories

(Infrastructure & Operations :: DCOps, task)

x86
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

Details

      No description provided.
Blocks: tegra-020
Blocks: tegra-328
colo-trip: --- → mtv1
Blocks: tegra-155
Blocks: tegra-027
Blocks: tegra-345
Blocks: tegra-346
Blocks: tegra-356
The tegras have been successfully re-imaged and are back online.

PING tegra-020.build.mtv1.mozilla.com (10.250.49.7): 56 data bytes
64 bytes from 10.250.49.7: icmp_seq=0 ttl=63 time=5.118 ms
64 bytes from 10.250.49.7: icmp_seq=1 ttl=63 time=4.983 ms
64 bytes from 10.250.49.7: icmp_seq=2 ttl=63 time=5.179 ms

Trying 10.250.49.7...
Connected to tegra-020.build.mtv1.mozilla.com.


PING tegra-221.build.mtv1.mozilla.com (10.250.51.61): 56 data bytes
64 bytes from 10.250.51.61: icmp_seq=0 ttl=63 time=5.106 ms
64 bytes from 10.250.51.61: icmp_seq=1 ttl=63 time=5.052 ms
64 bytes from 10.250.51.61: icmp_seq=2 ttl=63 time=5.121 ms

Trying 10.250.51.61...
Connected to tegra-221.build.mtv1.mozilla.com.


PING tegra-328.build.mtv1.mozilla.com (10.250.51.168): 56 data bytes
64 bytes from 10.250.51.168: icmp_seq=0 ttl=63 time=28.980 ms
64 bytes from 10.250.51.168: icmp_seq=1 ttl=63 time=4.950 ms
64 bytes from 10.250.51.168: icmp_seq=2 ttl=63 time=5.219 ms

Trying 10.250.51.168...
Connected to tegra-328.build.mtv1.mozilla.com.


PING tegra-155.build.mtv1.mozilla.com (10.250.50.65): 56 data bytes
64 bytes from 10.250.50.65: icmp_seq=0 ttl=63 time=5.347 ms
64 bytes from 10.250.50.65: icmp_seq=1 ttl=63 time=4.972 ms
64 bytes from 10.250.50.65: icmp_seq=2 ttl=63 time=7.754 ms

Trying 10.250.50.65...
Connected to tegra-155.build.mtv1.mozilla.com.


PING tegra-027.build.mtv1.mozilla.com (10.250.49.14): 56 data bytes
64 bytes from 10.250.49.14: icmp_seq=0 ttl=63 time=19.098 ms
64 bytes from 10.250.49.14: icmp_seq=1 ttl=63 time=2.503 ms
64 bytes from 10.250.49.14: icmp_seq=2 ttl=63 time=3.853 m

Trying 10.250.49.14...
Connected to tegra-027.build.mtv1.mozilla.com.


PING tegra-346.build.mtv1.mozilla.com (10.250.51.186): 56 data bytes
64 bytes from 10.250.51.186: icmp_seq=0 ttl=63 time=4.941 ms
64 bytes from 10.250.51.186: icmp_seq=1 ttl=63 time=2.358 ms
64 bytes from 10.250.51.186: icmp_seq=2 ttl=63 time=4.889 ms

Trying 10.250.51.186...
Connected to tegra-346.build.mtv1.mozilla.com.


PING tegra-345.build.mtv1.mozilla.com (10.250.51.185): 56 data bytes
64 bytes from 10.250.51.185: icmp_seq=0 ttl=63 time=4.974 ms
64 bytes from 10.250.51.185: icmp_seq=1 ttl=63 time=4.981 ms
64 bytes from 10.250.51.185: icmp_seq=2 ttl=63 time=5.008 ms

Trying 10.250.51.185...
Connected to tegra-345.build.mtv1.mozilla.com.


PING tegra-356.build.mtv1.mozilla.com (10.250.51.196): 56 data bytes
64 bytes from 10.250.51.196: icmp_seq=0 ttl=63 time=5.000 ms
64 bytes from 10.250.51.196: icmp_seq=1 ttl=63 time=5.086 ms
64 bytes from 10.250.51.196: icmp_seq=2 ttl=63 time=5.280 ms

Trying 10.250.51.196...
Connected to tegra-356.build.mtv1.mozilla.com.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Alias: tegra-recovery
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.