-----Original Message----- From: Stephen Lawrence Sent: 05 August 2020 20:22 To: Antonio Terceiro antonio.terceiro@linaro.org Cc: lava-users@lists.lavasoftware.org Subject: RE: [Lava-users] fastboot in docker support
[snip]
I simplified the test case to a simple boot and 'test with docker' job that is just sending some fastboot commands to check comms. It reboots into the bootloader and then sends a set-active command so it will wait if the device is not available: https://lava.genivi.org/scheduler/job/1154/definition
Submitting the job the fastboot device is successfully found and passed into the test docker as dev /001/074/: https://lava.genivi.org/scheduler/job/1154#L190
We have DUT comms and can reboot the board: https://lava.genivi.org/scheduler/job/1154#L232
However when we then do the fastboot set-active it waits: https://lava.genivi.org/scheduler/job/1154#L238
On the worker I can see that lsusb reports a Google device at /001/075. So the DUT appears to have successfully rebooted into fastboot. All be it with a different device number. If I connect to the device I can break into u-boot.
So it appears LAVA has not re-hooked the device on reboot. In your description you mention dev numbers changing so I assume that is in the design.
Do you have any suggestions as to what might be wrong or how I could debug this further?
Worker is running LAVA at the point of your 1268 PR on Debian stretch. lava-dispatcher-host is installed.
Just to simplify further and eliminate the possibility that the recent PR didn't have all the code I retested using the latest code. LAVA master branch HEAD~3 (sha a2bd1a87). I got the same results, with fastboot on the host not finding the device after reboot: https://lava.genivi.org/scheduler/job/1166
Best Wishes,
Steve