Closed Bug 742630 (tegra-066) Opened 13 years ago Closed 10 years ago

tegra-066 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

()

Details

(Whiteboard: [buildduty][capacity][buildslaves])

It was fine and happy up until this morning, and since then it's been nothing but timeout during cleanup device, timeout during cleanup device, timeout during cleanup device.
I just graceful'ed it from bm20's web UI. tegra-dashboard is indicating it has not rebooted in quite a while. Leaving followup to someone else
You weren't actually successful in stopping it, it's taken another four jobs since.
that tegra has been shutdown
Depends on: 740109
Summary: Please disable tegra-066 and enroll it in tegra recovery and mention the SD card → tegra-066 recovery
Whiteboard: [buildduty] → [buildduty][capacity][buildslaves]
bear - it looks like this got reimaged, but according to slavealloc it's allocated to your test master. can you take a look and reassign to the production pool if appropriate?
Assignee: nobody → bear
forgot to close when this was moved to production
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
For my benefit when next I wonder why it hasn't taken a job for weeks and weeks: It's in staging right now.
(In reply to Phil Ringnalda (:philor) from comment #7) > For my benefit when next I wonder why it hasn't taken a job for weeks and > weeks: > > It's in staging right now. Huh, it is??? From my manual looking its production. It needs a proper reimage, since we can't seem to access to watcher.ini from SUTAgent
Depends on: 788367
My guess is that I would have been talking about the way last-job-per-slave's reflection of slavealloc says "Staging" though it's also possible I was looking at mobile-dashboard, dunno.
No jobs taken on this device for > a week (< 3 weeks)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(mass change: filter on tegraCallek02reboot2013) I just rebooted this device, hoping that many of the ones I'm doing tonight come back automatically. I'll check back in tomorrow to see if it did, if it does not I'll triage next step manually on a per-device basis. --- Command I used (with a manual patch to the fabric script to allow this command) (fabric)[jwood@dev-master01 fabric]$ python manage_foopies.py -j15 -f devices.json `for i in 021 032 036 039 046 048 061 064 066 067 071 074 079 081 082 083 084 088 093 104 106 108 115 116 118 129 152 154 164 168 169 174 179 182 184 187 189 200 207 217 223 228 234 248 255 264 270 277 285 290 294 295 297 298 300 302 304 305 306 307 308 309 310 311 312 314 315 316 319 320 321 322 323 324 325 326 328 329 330 331 332 333 335 336 337 338 339 340 341 342 343 345 346 347 348 349 350 354 355 356 358 359 360 361 362 363 364 365 367 368 369; do echo '-D' tegra-$i; done` reboot_tegra The command does the reboot, one-at-a-time from the foopy the device is connected from. with one ssh connection per foopy
Assignee: bear → nobody
Summary: tegra-066 recovery → tegra-066 problem tracking
Unable to clean sdcard, --> sdcard swap.
Depends on: 838687
now taking jobs
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer blocks: 925447
Depends on: 925447
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Perma-retrying; disabled. 06/24/2014 06:25:35: INFO: copying build/fennec/application.ini to build/talos/remoteapp.ini 06/24/2014 06:25:35: DEBUG: calling [cp build/fennec/application.ini build/talos/remoteapp.ini] 06/24/2014 06:25:35: DEBUG: cp: cannot create regular file `build/talos/remoteapp.ini': No such file or directory 06/24/2014 06:25:35: INFO: connecting to: 10.26.85.47 reconnecting socket 06/24/2014 06:25:35: INFO: devroot /mnt/sdcard/tests 06/24/2014 06:25:35: INFO: 10.26.84.14, 50066 06/24/2014 06:25:35: INFO: Current device time is 2014/06/24 06:25:34 06/24/2014 06:25:35: INFO: Setting device time to 2014/06/24 06:25:35 06/24/2014 06:25:35: INFO: Current device time is 2014/06/24 06:25:35 results: {'process': [['10007', '1206', 'com.android.inputmethod.latin'], ['1001', '1216', 'com.android.phone'], ['1000', '1020', 'system'], ['10029', '1324', 'com.android.deskclock'], ['10032', '1482', 'com.mozilla.SUTAgentAndroid'], ['10017', '1333', 'com.android.bluetooth'], ['1000', '1233', 'com.android.settings'], ['10018', '1227', 'com.android.launcher'], ['10013', '1431', 'com.cooliris.media'], ['10009', '1411', 'com.android.quicksearchbox'], ['10002', '1423', 'com.android.music'], ['10031', '1401', 'com.mozilla.watcher'], ['10004', '1341', 'android.process.media'], ['10006', '1381', 'com.android.mms'], ['10010', '1365', 'com.android.providers.calendar'], ['10014', '1349', 'com.android.email'], ['10015', '1262', 'android.process.acore']]} results: {'memory': ['PA:837627904, FREE: 765939712']} results: {'uptime': ['0 days 0 hours 58 minutes 52 seconds 637 ms']} results: {'screen': ['X:1024 Y:768']} 06/24/2014 06:25:35: INFO: Installing /mnt/sdcard/tests/fennec-33.0a1.en-US.android-arm-armv6.apk in push file with: build/fennec-33.0a1.en-US.android-arm-armv6.apk, and: /mnt/sdcard/tests/fennec-33.0a1.en-US.android-arm-armv6.apk sending: push /mnt/sdcard/tests/fennec-33.0a1.en-US.android-arm-armv6.apk push returned: bed369c8fbf0fec6778e5970dd459931 Push File Validated! 06/24/2014 06:25:52: INFO: /builds/tegra-066/test/../error.flg Remote Device Error: updateApp() call failed - exiting program finished with exit code 1 elapsedTime=47.609789
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1031502
replaced SD card, flashed and reimaged tegra. vle@vle-10516 ~ $ telnet tegra-066.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.47... Connected to tegra-066.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
QA Contact: armenzg → bugspam.Callek
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.