action #36802
closed
[functional][u][sporadic] test fails in consoletest_setup
Added by dheidler almost 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-extra_tests_on_gnome@aarch64 fails in
consoletest_setup
Further details¶
Always latest result in this scenario: latest
This is a sporadic issue due to BTRFS kernel messages spamming the tty and breaking the needle matching.
Possible workarounds:
- Subject changed from test fails in consoletest_setup to test fails in consoletest_setup (sporadically)
- Subject changed from test fails in consoletest_setup (sporadically) to test fails in consoletest_setup (not always)
Hi @dheidler please use our common component and team markers for the subject line, e.g. "[functional][u][sporadic] …" as well as provide a proper "expected result". Keep in mind that the ticket reporting template is just a "template". You can fill it with real content and you can also delete parts which you see are not fitting at all. "Last good: (unknown) (or more recent)" only means that the openQA bug reporting template generation code could not find a "last good" but I guess you can be smarter than a script ;)
- Subject changed from test fails in consoletest_setup (not always) to [functional][u][sporadic] test fails in consoletest_setup
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to dheidler
- Is duplicate of action #19398: [functional][y] Handle console messages covering ncurses dialogs (was: Remove "console=tty" boot option for installed system) added
- Status changed from In Progress to Rejected
- Related to action #13304: [sle][functional][u][opensuse][medium] Check plymouth splash screen is not interrupted by ugly console output if 'quiet' added
@okurz: how are we going to login to run cron jobs when the needles won't match?
by either fixing the product or our console options in the bootloader
Also available in: Atom
PDF