1045654 - Device b2g-13.1 cannot be found via ADB

Status: RESOLVED FIXED

(Testing Graveyard :: WebQA, defect)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

The device is not able to be found through ADB. I have taken the Jenkins node temporarily offline.

Comment 1

[raymond [:retornam] (inactive)]

Attachment: b2g-13.png

Comment 2

[raymond [:retornam] (inactive)]

The devices is now connected and detected via adb. I'll bring the node back online

Comment 3

[Dave Hunt [:davehunt] [he/him] ⌚BST]

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.

Comment 4

[raymond [:retornam] (inactive)]

(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.

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚BST]

(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.

Comment 6

[Dave Hunt [:davehunt] [he/him] ⌚BST]

I've raised bug 1046104. Thanks for the help Raymond.

Comment 7

[Dave Hunt [:davehunt] [he/him] ⌚BST]

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?

Comment 8

[raymond [:retornam] (inactive)]

(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.