openQA Project - coordination #39719: [saga][epic] Detect "known failures" and mark jobs as such to make tests more stable, reviewing test results and tracking known issues easier
coordination #77899: [epic] Extend "auto-review" for failed jobs as well
[proof-of-concept] Extend "auto-review" for failed jobs as well, start with o3
#3 Updated by okurz about 2 months ago
Instead of putting a bigger command line within .gitlab-ci.yml which might interfer with YAML parsing I decided to put the one-line-call into it's own script https://github.com/os-autoinst/scripts/pull/47
Also created https://gitlab.suse.de/openqa/auto-review/-/merge_requests/6 to call the new combined script
./openqa-review-failed for o3 Tumbleweed.
#4 Updated by okurz about 2 months ago
- Status changed from Feedback to Resolved
with https://gitlab.suse.de/openqa/auto-review/-/merge_requests/6 merged and a new pipeline triggered there is now
which shows (unfortunately) only comment ids of created openQA comments, e.g. "98634". With
ssh o3 "sudo -u geekotest psql openqa -c 'select job_id from comments where id=98634;'"
one could found out that the corresponding openQA job where the comment was posted and the according comment is
Automatic investigation jobs: * gnome:investigate:retry: https://openqa.opensuse.org/t1486465 * gnome:investigate:last_good_tests:e8223ff26cf73d8dfa4a62358cafd592310d31e9: https://openqa.opensuse.org/t1486466 * gnome:investigate:last_good_build:20201125: https://openqa.opensuse.org/t1486467 * gnome:investigate:last_good_tests_and_build:e8223ff26cf73d8dfa4a62358cafd592310d31e9+20201125: https://openqa.opensuse.org/t1486468
AFAICS no "known issue" was detected which is expected as there are not many (or any?) progress tickets with a proper auto-review regex for failed jobs.
With this I see the proof-of-concept succesfully in place and we can regard this ticket as "Resolved". As next steps in the epic I recommend to extend the approach to a selected product or job group on osd as well as all "non-development" job groups on o3.