[functional][u] test fails in yast2_lan: console loglevel changed too late
The minimum level of kernel messages is set in force_scheduled_tasks, but that is too late here.
The console got created in consoletest_setup, so any messages in between that and the call to dmesg
in force_scheduled_tasks still spam the console and cause needles to not match.
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-42.2-gnome@64bit fails in
Fails since (at least) Build 20180926
Last good: 20180925 (or more recent)
Always latest result in this scenario: latest
#1 Updated by okurz almost 3 years ago
- Subject changed from test fails in yast2_lan: console loglevel changed too late to [functional][u] test fails in yast2_lan: console loglevel changed too late
- Target version set to future
putting to "future". Based on the current velocity of the team and the already planned backlog this could take some team for QSF-u to complete. I guess you could be way faster to do it properly yourself. Feel free to remove the "[functional][u]" tag and make it happen :)
#2 Updated by okurz over 2 years ago
- Status changed from New to Rejected
- Assignee set to okurz