If you could give the full job log that would certainly help. From what I can see the login_prompt in your definition doesn't match the output from the board. LAVA expects "xxxxx login:" and the board outputs "mgu22 login:". You can probably remove all "xxxxx" and that should fix the issue.
milosz
On Wed, 9 Oct 2019 at 08:36, George Nistor george.n@l4b-software.com wrote:
Hello Lava users,
I have a Lava job, with the following section:
boot:
namespace: target
prompts:
- 'root@xxxxx:~#'
auto_login:
login_prompt: 'xxxxx login:' username: roottimeout:
minutes: 5method: fastboot
and Lava does not complete with ‘root’ to do autologin. After 5 mins it give me timeout autologin.
Even if I run the job and waited till the login prompt comes as output in Lava and do a echo 'root' > /dev/ttyUSB2 still Lava detects timeout autologin. (even if the devices successfully logs in – I have sent the string ‘root’ 2 times from the terminal).
[ 25.440854] audit: type=1325 audit(1564586870.989:25): table=filter family=2 entries=8
BMW xxxxx 19w32.5-1-2 mgu22 ttyMSM0
mgu22 login: root
7[r[999;999H[6nroot@xxxxx:~# root
-sh: root: not found
root@mgu22:~# [ 79.848385] firmware cdsp.mdt: _request_firmware_load: firmware state wait timeout: rc = -110
[ 79.857777] subsys-pil-tz 8300000.qcom,turing: cdsp: Failed to locate cdsp.mdt(rc:-11)
auto-login-action timed out after 231 seconds
The complete lava job is here.
Where is the mistake I do?
george