action #164210
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request
Run a basic openQA test in osado is triggeded blindly even if nothing is published
0%
Description
CI is that the script depends on the latest published asset, and does not check if the asset exists and blindly triggers a test
https://openqa.opensuse.org/group_overview/1?limit_builds=1&only_tagged=1
Taking a quick look at: https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/10001594938/job/27650957471 one can notice that there's two consecutive dashes - (aka: CI wants to play Mario Kart
HDD_1=opensuse-Tumbleweed-x86_64--textmode@64bit.qcow2 UEFI_PFLASH_VARS=opensuse-Tumbleweed-x86_64--textmode@64bit-uefi-vars.qcow2
See https://suse.slack.com/archives/C02CANHLANP/p1721356907962369 for more details
The failure rate is a bit higher than it should be, looking randomly at few jobs (like 2) https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/workflows/openqa.yml?page=2&query=is%3Afailure
Updated by okurz 4 months ago
- Tags set to reactive work
- Target version set to Ready
And https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19780 as additional improvement.
Updated by okurz 4 months ago
- Status changed from Feedback to Resolved
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19780 merged. Checks in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19781 which is just the next PR after mine show that all is good again. Others need rebasing or retriggering after the latest Tumbleweed snapshot is also a published one.
Updated by jbaier_cz 3 months ago
- Related to action #165722: Trigger and monitor openQA test inside Github action does not work if the latest TW build is tagged as discarded added