1089659 - Device b2g-24.2 cannot be found via ADB

Status: RESOLVED DUPLICATE of bug 1121374

(Firefox OS Graveyard :: Infrastructure, defect)

Description

[Robert Chira [:RobertC]]

Please check that this device is powered on, connected via USB, and can be seen by ADB.

Comment 1

[Tony Chung [:tchung]]

device was rebased without adb access.  its now on, please try again.

Comment 2

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

This node wasn't brought back online in Jenkins and is now unavailable again. Please could you take another look Tony?

Comment 3

[Tony Chung [:tchung]]

restarted device, and checked adb is on.

Comment 4

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

Still not found by ADB. Perhaps we should remove this device from the pool if it continues to have problems?

Comment 5

[Tony Chung [:tchung]]

i'm told this is still not detecting adb.  assign to self to fix and bring node back up when completed.

Comment 6

[Tony Chung [:tchung]]

Parul can you take a look please?

Comment 7

[Parul Mathur [:pragmatic] - out of office - please ni? [:bajaj] instead]

Rebooted the device and checked that it has ADB access.

Comment 8

[Robert Chira [:RobertC]]

I checked the device and Jenkins still returns device not found.

Comment 9

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

Can we get confirmation that the device can be seen by using the command adb devices before resolving? It may also be worth flashing v188-1 to the device manually before reconnecting.

Comment 10

[Parul Mathur [:pragmatic] - out of office - please ni? [:bajaj] instead]

Flashed the device with v188-1 base image and then shallow flashed the latest v2.1 build. 

Gaia-Rev        0ec1925fc37b7c71d129ae44e42516a0cfb013c4
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/97487a2d1ee6
Build-ID        20141110001201
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  40
FW-Date         Tue Oct 21 15:59:42 CST 2014
Bootloader      L1TC10011880


Enabled Settings > Developer Menu. Enabled ADB and checked adb access to the device.

$ adb devices
List of devices attached 
e474dac5	device

Comment 11

[Robert Chira [:RobertC]]

Jenkins node seems to be working now.

Comment 12

[Robert Chira [:RobertC]]

Unfortunately there are still some issue with this node.

http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.b2g-inbound.ui.functional.smoke/1080/console
The job gets stuck waiting for the device when it reboots after being flashed.

Comment 13

[Parul Mathur [:pragmatic] - out of office - please ni? [:bajaj] instead]

The device was on the first screen of the FTU. I went through the FTU and enabled Wifi and ADB. 

The automation setup need to be updated to handle this scenario which occurs frequently. See bugs 1095563, 1095576 and 1096822.

Comment 14

[Robert Chira [:RobertC]]

I will leave this bug open until we can figure out if the setUp() needs to be updated.

Comment 15

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

All devices will be on FTU after they've been flashed so this is not an issue. WiFi is enabled as needed by the tests, so that's also not an issue. The only concern I have here is remote debugging not being enabled, which should be the case after a base flash of v188-1 or subsequent shallow flashes or full flashes of engineering builds.

Given the issues we've had with this specific device I would recommend removing it and testing it locally to see if we can replicate it. Perhaps this device, host, or USB cable is faulty.

Comment 16

[Robert Chira [:RobertC]]

We are still seeing the "device not found" on this node

Comment 17

[Geo Mealer [:geo] -- This account is inactive after 2015-07-07]

Duping to the general crash bug, at least for the latest instance.

Let's not re-open these individual node bugs, please. Root causes for future issues are very likely different, and need their own discussions.