action #152853
Updated by tinita 5 months ago
## Motivation With #109920 openqa-investigate can identify clear *PRODUCT REGRESSIONS* and with #132272 we identify *TEST REGRESSIONS* and with #151399 we can already identify infrastructure issues. Sometimes openqa-investigate can come or lead to wrong conclusions when different workers on which tests have been executed have an impact. So we should see that openqa-investigate by default is not impacted by that, e.g. by executing investigation jobs only on the very same openQA worker. ## Acceptance criteria * **AC1:** openqa-investigate last_good_test+last_good_build jobs run on the same worker as the original failure if uniquely identifyable by WORKER_CLASS * **AC2:** openqa-investigate provides a caution notice if no worker could be uniquely identified ## Suggestions * Learn what had been done in #109920 for product regressions and #132272 for test regressions and #151399 for infrastructure regressions * Identify "worker" by WORKER_CLASS or other means and schedule openqa-investigate last_good_test+last_good_build jobs so that they run on the same worker if uniquely identifyable by WORKER_CLASS * If no such worker can be uniquely identified then make openqa-investigate provide a caution notice if no worker could be uniquely identified, e.g. either an extension of the openQA comment that is written or extend https://github.com/os-autoinst/scripts/blob/master/README.md#openqa-investigate---automatic-investigation-jobs-with-failure-analysis-in-openqa as we point to that in the comment already