QA (public) » openQA Project (public)

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". After #117655 we identified that we can use that to filter but there is a key/job id limit so we need to find out how to work with a much larger limit e.g. with a database index. With #182666 we conducted a research. One potential implementation is using advanced indexing and/or trigram gin index on the already existing openQA table job_settings. See #182669 for benchmark results. Assuming that all those previous work shows that we still need a separate openQA table then consider the implementation from #156553-23 about job_tags

Goals¶

• G1: Prototype spike-solution showing how job tags, e.g. SLE maintenance incidents, can be used to efficiently search for related openQA jobs
• G2: Follow-up work as consequence of introducing a new database table has been planned in according tickets covering complete CRUD and automatic cleanup

Suggestions¶

• Implement suggestion from #156553-23 in a spike solution. Try it out using OSD database dumps and putting all *_TEST_ISSUES=$1,$2,… references into according job tags, e.g. OS_TEST_ISSUE:$1, OS_TEST_ISSUE:$2 and try out and benchmark searching of openQA jobs by job tags and complete CRUD operations