Hello,
if the prompt is "# " without more characters then in the lava job definition you have to put "# ". In fact, this won't work well because this string can be seen on other places (like kernel logs).
The only solution here would be to change the prompt of the root filesystem to make it a bit more unique.
Rgds
Le mer. 31 juil. 2019 à 13:53, Hemanth K V kv.hemanth.mys@gmail.com a écrit :
Hello Remi,
First of all Thanks for support.Trying for matching the string "# " If we don't specify any escape or brackets then it is matching one of the kernel message logs and sending the username .Following is reference of auto_login defined in yaml. ***** hwi path: hwi version/minor get_device_info->hwi_get_value: read STRING value: device name Matched prompt #4: #
auto_login: login_prompt: "buildroot login:" username: root password_prompt: "Password:" password: root prompts: - '# 'On including escape it is waiting for auto-login-action: Wait for prompt ['\(# \)', 'Login incorrect', 'Login timed out'] (timeout 00:07:53). Following is reference of auto_login defined in yaml.
auto_login: login_prompt: "buildroot login:" username: root password_prompt: "Password:" password: root prompts: - '\(# \)'Thanks, Hemanth.
On Wed, Jul 31, 2019 at 3:25 PM Remi Duraffort remi.duraffort@linaro.org wrote:
Hello,
which strin are you trying to match? " #", "#", "# "? Just put that (without any escaping or brackets) in the list of prompts.
Rgds
Le mar. 30 juil. 2019 à 14:20, Hemanth K V kv.hemanth.mys@gmail.com a écrit :
Hello Lava Users,
The target on which I am trying to run tests from LAVA has # prompt after login. As specified in Documentation https://lava.collabora.co.uk/static/docs/v2/actions-boot.html?highlight=prom...
- boot: prompts: # escape the brackets to ensure that the prompt does not match # kernel debug lines which may mention initramfs
- '(initramfs)'
in the job definition I am including - boot: ..... failure_retry: 4 prompts: - '(# )'
But in the job execution log getting "*auto-login-action: Wait for prompt ['\(# \)', 'Login incorrect', 'Login timed out'] (timeout 00:07:52)*".
Also if we want to debug while running the job which will be the best possible approach to follow. In the Documentation got information on "Debugging Django issues" which states two settings are required in/etc/lava-server/settings.conf
- "DEBUG": true,
- "USE_DEBUG_TOOLBAR": true,
Thanks, Hemanth.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Team, Linaro