action #47921
closed[functional][y] Apply new scheduling mechanism for any installation scenario in YaST job group which is also executed on o3
0%
Description
Motivation¶
So we got 3 PoC solutions, which do work already, but none of them solves all the problems (which happens mainly in dreams). It's time to continue and one make step further.
Here are PoCs:
- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6741
- https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6329
- https://github.com/mudler/openqa_testloader_workshop
As a test developer, I would like to easily modify and control schedule of the test suites. I also would like not to affect all existing test suites when enabling additional module.
From https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6329 we should borrow test for yaml format validation. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6741 has couple of points not addressed. We mainly just need to make it extendable, so other features like setting variables in yaml (is available here: https://github.com/mudler/openqa_testloader_workshop) can be developed.
Suggestion:
Use simple scenarios to start with.
Acceptance criteria¶
- New declarative scheduling mechanism is applied for a single test suite which is executed on osd ond o3
- Solution is reusable and available for all test developers
- Solution is documented, describing syntax and usage
Updated by riafarov about 6 years ago
- Copied from action #44420: [functional][y][timeboxed:6h] proof-of-concept of declarative test schedule definition, e.g. in YAML file(s) added
Updated by riafarov almost 6 years ago
- Description updated (diff)
- Estimated time set to 8.00 h
Updated by JERiveraMoya almost 6 years ago
- Status changed from Workable to In Progress
Updated by JERiveraMoya almost 6 years ago
- Status changed from In Progress to Feedback
PR: Scheduling yast2_gui with yaml scheduling -> Merged
Updated by riafarov almost 6 years ago
https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/101 to deploy dependencies to OSD workers.
Updated by riafarov almost 6 years ago
maxlin will support us to deploy on o3 workers, I will check later today. @JERiveraMoya, could you please resurrect your PR, so we don't have to revert reverted PR =)
Updated by JERiveraMoya almost 6 years ago
PR was merged, so I guess there is no other option than revert the reverted due it is 100 commits behind (unless there is some nice git command that I don't know)
Updated by JERiveraMoya almost 6 years ago
Updated by okurz almost 6 years ago
I installed the necessary packages on o3 with for i in aarch64 imagetester openqaworker1 openqaworker4; do echo $i && ssh root@$i "transactional-update -n pkg in perl-YAML-Tiny perl-Test-Assert && reboot"; done
. Crosschecked on openqaworker13 (osd) and the packages also installed there. Should be fine to merge now.
Updated by JERiveraMoya almost 6 years ago
- Status changed from Feedback to Resolved
Thanks both for providing the packages.
Test suites settings adapted. Verification in production provided by @riafarov in PR.
Updated by JERiveraMoya almost 6 years ago
- Status changed from Resolved to In Progress
Still some packages missing for ppc64le. Settings restored again.
Updated by riafarov almost 6 years ago
- Due date changed from 2019-03-12 to 2019-03-26
- Estimated time deleted (
8.00 h)
Updated by riafarov almost 6 years ago
Progress currently is blocked by deployment: https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/103
Updated by riafarov almost 6 years ago
- Estimated time set to 3.00 h
We need to use clone-git-ref script for power and arch64 workers on production to validate this before merging.
Updated by okurz almost 6 years ago
- Blocked by action #49367: [functional][y][fast] yast2_gui does not test yast2_gui anymore added
Updated by riafarov almost 6 years ago
I've merged https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7046
Let's see if we have fixed all issue during the third try =)
Updated by JERiveraMoya almost 6 years ago
- Status changed from In Progress to Resolved