Hi,
I launched util-linux ptest using automated/linux/ptest/ptest.yaml from
https://git.linaro.org/qa/test-definitions.git and received the
following results:
https://pastebin.com/nj9PYQzE
As you can see some tests failed. However, case util-linux marked as
passed. It looks like ptest.py only analyze return code of ptest-runner
-d <ptest_dir> <ptest_name> command. And since ptest-runner finishes
correctly exit code is 0. Therefore all tests are always marked as
passed, and users never know when some of the tests fail.
Maybe it worth to analyze each test?
Best regards,
Alex
Hi Linaro Validation,
I have a used case where by during auto_login the Clear OS, we have 1st password prompt and follow by 2nd password prompt to verity the
password creation is set properly. I would like to know if the current dispatcher scripts is able to support this use case, whereby a second
password prompt is expected follow by the a second password re-entry. Let me know your thoughts on where I can start with this if there is
a need to add in an extra key into the boot action methods.
Currently if I used this on my LAVA Job it returns me with this error:
Invalid definition: extra keys not allowed @ data['actions'][1]['boot']['auto_login']['password_prompt_retry']
auto_login: { login_prompt: 'login:', username: root, password_prompt: 'Password:', password: password123, password_prompt_retry: 'New Password:', password_reentry: password123 }
Regards,
Chan, Aaron
SSG Embedded Linux - Yocto Project
Contact : +6042536861
Location: PG12/L1/A318