Closed
Bug 753082
(tegra-020)
Opened 14 years ago
Closed 12 years ago
[staging] tegra-020 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslave][capacity][mobile])
bash-3.2$ telnet tegra-020 20701
Trying 10.250.49.7...
telnet: connect to address 10.250.49.7: Connection refused
telnet: Unable to connect to remote host
This one had a bad sut agent installed unto it.
Comment 1•14 years ago
|
||
I can ping/telnet now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Summary: tegra-020 problem tracking → [staging] tegra-020 problem tracking
Whiteboard: [buildduty][buildslave][capacity][mobile]
Comment 2•12 years ago
|
||
Sending this slave to recovery
-->Automated reopening of bug
Comment 3•12 years ago
|
||
reflashed and reimaged.
Updated•12 years ago
|
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 4•12 years ago
|
||
09/18/2013 18:27:44: INFO: INFO: attempting to create file /mnt/sdcard/writetest
09/18/2013 18:27:45: INFO: INFO: updateSUT.py: We're running SUTAgentAndroid Version 1.00
09/18/2013 18:27:45: INFO: updateSUT.py: We're going to try to install SUTAgentAndroid Version 1.19
09/18/2013 18:27:45: INFO: INFO: updateSUT.py: We're downloading the apk: http://talos-bundles.pvt.b
uild.mozilla.org/mobile/sutAgentAndroid.1.19.apk
09/18/2013 18:27:45: INFO: We're going to sleep for 90 seconds
09/18/2013 18:29:15: INFO: Connecting to: tegra-020
09/18/2013 18:29:45: INFO: INFO: updateSUT.py: We're running SUTAgentAndroid Version 1.19
09/18/2013 18:29:45: INFO: updateSUT.py: We're now running SUTAgentAndroid Version 1.19
:sal, are you *sure* you and the interns used the steps I setup on the two new imaging netbooks in Bug 913321 and that this one reimaged fine?
I note that the SUTAgent we install should have been 1.19, but the code showed 1.00 here, after a few forced powercycles....
If you did there is a pretty good chance that the staging run releng did after Bug 913321 is invalid, and the work I did to prep for that bug was also bad.... please advise.
Depends on: 918162
Flags: needinfo?(sespinoza)
Comment 5•12 years ago
|
||
:callek, Sorry I missed this bug.
I'm sure they did, but if we missed it we can have this one re-imaged in the next tegra recovery bug with the staging image.
Flags: needinfo?(sespinoza)
Comment 6•12 years ago
|
||
I think this one is working again...
Status: REOPENED → RESOLVED
Closed: 14 years ago → 12 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•