QA » openQA Project » openQA Tests

I don't think that this is a bug in the test, but a bug in openQA. The serial console is not working again, so the wait_serial function is failing.

@apappas I think it simply never worked. It's unfortunate that it seems there is so little care for failing tests hence this was never detected because on s390x there is no (easy) way to revert to snapshots so the job failed for very long in #56969 and never reached gdb. I do not know how this is supposed to ever work, to just start gdb and assume that string would show up on the serial port as it's never forwarded there.

I think it's best that I rewrite the test as a python script to be interpreted by gdb.
It will not then be interactive and I will be able to just use assert_script_run.

What do you think @okurz?

Makes sense. As an alternative you might want to log all output of gdb to /dev/$serialdev which allows to still use wait_serial. Both approaches sound easy to me.

As it's Urgent now: if you can't get this done today, please take the test out of QAM (and keep the ticket open)

Passing on x86_64, and s390x already disabled currently:

https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191010-2&groupid=232

vs where this was linked from https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20190911-1&groupid=232

Your link is misleading as it 10-2 wasn't tested for s390x (for whatever reason): https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191013-1&groupid=232 fails

I worked around it now by setting EXCLUDE_MODULES=gdb. So please fix and validate with care :)

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3575790

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3575790

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed