action #99357
openautomatic retrigger when all four investigation jobs pass and the history shows only passed because no one will be able to reproduce such issues
0%
Description
Observation¶
openQA test in scenario sle-15-Server-DVD-HPC-Incidents-x86_64-hpc_rasdaemon@64bit fails in
boot_to_desktop
because the system is seemingly stuck on the plymouth boot splash screen. During the post fail hook it can be seen that the system is actually just ready to be used though with visual artifacts: https://openqa.suse.de/tests/7224406#step/boot_to_desktop/9
https://openqa.suse.de/tests/7224406#comment-387165 shows that all four investigation jobs have passed:
- hpc_rasdaemon:investigate:retry: https://openqa.suse.de/t7230214
- hpc_rasdaemon:investigate:last_good_tests:8b24f41dad2388fee5cb50e6806261405594e917: https://openqa.suse.de/t7230215
- hpc_rasdaemon:investigate:last_good_build::20867:apache2: https://openqa.suse.de/t7230216
- hpc_rasdaemon:investigate:last_good_tests_and_build:8b24f41dad2388fee5cb50e6806261405594e917+:20867:apache2: https://openqa.suse.de/t7230217
Reproducible¶
https://openqa.suse.de/tests/7224406#next_previous shows 255 jobs where none except the one above have ever failed so this is obviously not easy to reproduce.
Idea¶
In cases like these it's unrealistic to be able to fix any bug as there is simply not obvious way to reproduce hence the best approach would likely be to retrigger the individual test and accept the one outlier.
Acceptance criteria¶
- AC1: Tests with 4x passed investigation jobs and a history of all green are automatically retriggered
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 3 years ago
- Project changed from openQA Tests to openQA Project
- Category changed from Bugs in existing tests to Feature requests
- Priority changed from Normal to Low
- Target version set to future
Updated by okurz about 2 years ago
- Related to coordination #89095: [epic] Provide openqa-investigate information on job details added