action #131279
Updated by livdywan 3 months ago
## Motivation From #121246-15: "We'd need to look for all the tests that are failing for a given incident, using the same TEST_ISSUES for both, Aggregates and Incidents". So what is needed is a [timeboxed:6h][spike solution] a single command line or openQA webUI search view to show all tests blocking an incident by squad. After #117655 and #119746 we should combine both. ## Suggestions * We can get a job for a particular incident (#117655#note-33) * openqa-cli api --o3 /job_settings/jobs key=*_TEST_ISSUES list_value=1234567 * openqa-cli api --osd /job_settings/jobs key=LTSS_TEST_ISSUES list_value=20988 * Note there is an implicit enforced limit of 20000 jobs here (see also the later suggestion) * We have support for group globbing (#134933#note-32) * https://openqa.opensuse.org/tests?group_glob=*Leap*&todo=1 * "squads" could be mapped into openQA for example with special job settings, e.g. QE Core ensures to trigger all their tests with _SQUAD='QE Core' and then be able to filter by that * Explore removing the key/job id limit, or add a way to override it (and/or make followup ticket to finally introduce a trigram gin index for fast text searching without limits on keys) * Maybe add a openqa-cli command **blocked** for this (similar to recently introduced monitor sub-command, make followup ticket) * This doesn't need to be specific to squads/blocking tests (openQA itself should not know about these SUSE specific concepts)