coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues
coordination #80828: [epic] Trigger 'auto-review' and 'openqa-investigate' from within openQA when jobs incomplete or fail on o3+osd
Trigger 'openqa-investigate' from within openQA when jobs fail on osd
have not encountered problem but config was reset, likely by salt. Making persistent with https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/420
many unexpected jobs were triggered. Apparently the git update cron job on osd did not work since 2020-12-08 as the directory belongs to root but the cron job runs as geekotest.
delete from jobs where test ~ ':investigate:' and state ~ 'scheduled'; to repair for currently scheduled ones. And for running ones to delete nested ones:
for i in $(openqa-cli api --osd jobs state=running | jq '.jobs | . | select(.test|test(":investigate:.*:investigate:")) | .id'); do openqa-cli api --osd -X delete jobs/$i ; done
- Status changed from In Progress to Resolved
With https://openqa.suse.de/tests?match=:investigate: we can see that investigation jobs are triggered. There was some discussion in https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/425 and we disabled openqa-investigate for "Maintenance", based on feedback as visible in related tickets.