action #63083
closed
[functional][u] test fails in lshw because of traces from previous test on root console
Added by ggardet_arm over 4 years ago.
Updated about 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
openQA test in scenario opensuse-15.2-DVD-aarch64-extra_tests_in_textmode@aarch64 fails in
lshw
Test fails in lshw because of traces from previous test on root console.
Suggestions¶
- Clear screen?
- Is it using log-console for kernel messages?
Reproducible¶
Fails since (at least) Build 68.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Traces seem to come from ssh.
- Related to action #54287: [functional][u] Weechat test pollute root console and make next test (nano) fail added
- Subject changed from test fails in lshw because of traces from previous test on root console to [functional][u] test fails in lshw because of traces from previous test on root console
- Priority changed from Normal to High
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
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.opensuse.org/tests/1215846
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Status changed from Workable to In Progress
- Assignee set to zluo
check why select_console 'root-console' failed.
- Status changed from In Progress to Rejected
- Status changed from Rejected to Workable
Test died: command 'lshw -sanitize | grep -A5 'description'' failed at /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/lshw.pm line 26.
this is a different issue than the initial issue report in this ticket. I don't see any traces coming from previous test module. Please correct me if this is not true.
- Status changed from Workable to Rejected
That's right, sorry for the noise!
Also available in: Atom
PDF