action #25576
closed[tw]test fails in kdump_and_crash (reboot not happening)
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_in_textmode@64bit fails in
kdump_and_crash
Reproducible¶
Fails since (at least) Build 20170905
Expected result¶
Last good: 20170904 (or more recent)
Further details¶
Always latest result in this scenario: latest
I'm not sure I understand the test per se, so can't judge right away if this is a prod bug or not; has been failing at least since 0913, but with all the other mess, got 'lost' in the noise
Updated by okurz over 6 years ago
I see https://openqa.opensuse.org/tests/492687#step/kdump_and_crash/37 full of errors. How do you see this as a "bug in existing tests"?
Updated by okurz over 6 years ago
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/508147
Updated by okurz over 6 years ago
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/520628
Updated by okurz over 2 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".
Updated by dimstar over 1 year ago
- Status changed from New to Rejected
kdump_and_crash went through so many iterattions and is broken so badly, that it can;t even understand the dwarf format being used anymore:
https://bugzilla.opensuse.org/show_bug.cgi?id=1190434
No need to have this tracked by QA in any way