Device b2g-13.1 cannot be found via ADB

RESOLVED FIXED

Status

Testing Graveyard
WebQA
--
critical
RESOLVED FIXED
4 years ago
3 months ago

People

(Reporter: davehunt, Unassigned)

Tracking

Trunk
ARM
Gonk (Firefox OS)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
The device is not able to be found through ADB. I have taken the Jenkins node temporarily offline.
Flags: needinfo?(mozbugs.retornam)
Flags: needinfo?(dwong)
Created attachment 8464058 [details]
b2g-13.png
Flags: needinfo?(mozbugs.retornam)
The devices is now connected and detected via adb. I'll bring the node back online
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Flags: needinfo?(dwong)
(Reporter)

Comment 3

4 years ago
Do you know what was wrong? This is happening fairly frequently, and I'd like to see if we can prevent it rather than just react to it, especially as it can be several hours before detection.
Flags: needinfo?(mozbugs.retornam)
(In reply to Dave Hunt (:davehunt) from comment #3)
> Do you know what was wrong? This is happening fairly frequently, and I'd
> like to see if we can prevent it rather than just react to it, especially as
> it can be several hours before detection.

All the phones were powered on and had full battery power when I checked on them. I dont have much information as to what really caused them not to be detected via adb. My guess is that the phones run out of battery power early this morning due to the long test run times for the perf-tests.
Flags: needinfo?(mozbugs.retornam)
(Reporter)

Comment 5

4 years ago
(In reply to raymond [:retornam] [PTO 7/18, 7/21, 7/24, 7/25 2014](needinfo? me) from comment #4)
> (In reply to Dave Hunt (:davehunt) from comment #3)
> > Do you know what was wrong? This is happening fairly frequently, and I'd
> > like to see if we can prevent it rather than just react to it, especially as
> > it can be several hours before detection.
> 
> All the phones were powered on and had full battery power when I checked on
> them. I dont have much information as to what really caused them not to be
> detected via adb. My guess is that the phones run out of battery power early
> this morning due to the long test run times for the perf-tests.

That sounds possible. Not just the long run times, but the fact we're running lost of tests back-to-back. We should look into giving the devices time to recharge.
(Reporter)

Comment 6

4 years ago
I've raised bug 1046104. Thanks for the help Raymond.
(Reporter)

Comment 7

4 years ago
This has happened again. It would appear the last successful build to run started with 100% battery capacity, so I think it's unlikely the device was drained. Do you want me to reopen bugs like this or file new ones?
Status: RESOLVED → REOPENED
Flags: needinfo?(mozbugs.retornam)
Resolution: FIXED → ---
(In reply to Dave Hunt (:davehunt) from comment #7)
> This has happened again. It would appear the last successful build to run
> started with 100% battery capacity, so I think it's unlikely the device was
> drained. Do you want me to reopen bugs like this or file new ones?


The device has 100% power but cannot be detected at all via adb. Dave are you fine with replacing this device with a new one?


It will be great to file new bugs as it will help with metrics.
Flags: needinfo?(mozbugs.retornam)
See Also: → bug 1052117
(Reporter)

Updated

4 years ago
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED

Updated

3 months ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.