action #101494
closedcoordination #103323: [epic] BCI testing
BCI: create openQA CI pipeline for bci-tests repo
0%
Description
bci-tests have a CI already but sometimes there are errors found in openQA that are not in that gitlab CI.
The idea is to trigger the same tests in openQA that will be triggered in productiong, but testing the branch whenever there is a new MR.
When creating the isos post, it's possible to insert the variable BCI_TESTS_BRANCH pointing to the branch-under-test. The openQA tests are already prepared to clone that branch if the variable is given.
Updated by jlausuch about 3 years ago
- Status changed from New to In Progress
- Assignee set to jlausuch
Updated by jlausuch about 3 years ago
First MR for bci-tests pipeline for new MR.
https://gitlab.suse.de/dancermak/bci-tests/-/merge_requests/43
For now, only x86_64 tests will be triggered in fromm.arch.suse.de.
There is one caveat if we want to run them in OSD, there could be long waiting times due to jobs scheduled and taking time to run if queues are long...
Updated by jlausuch about 3 years ago
I tried again to run the tests from the CI but some tests keep failing:
https://gitlab.suse.de/dancermak/bci-tests/-/jobs/697533
Need to talk to Dan to see how to fix the issue we have currently with no space left on device
e.g. http://fromm.arch.suse.de/tests/4338#external
Updated by jlausuch almost 3 years ago
- Status changed from In Progress to Resolved
This got solved after creating the Container OS HDDs with higher root partition size.
Related: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13720
I haven't seen these type of issues in BCI tests any more, so this is resolved.