action #48068
closed
coordination #43769: [functional][y][epic] Use inter-machine dependencies to ease our review
[functional][y][timeboxed:4h] Get to know inter-machine dependencies
Added by okurz about 5 years ago.
Updated almost 5 years ago.
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 25
Description
Motivation¶
With #40415 we can use inter-machine dependencies to prevent the same error to popup on different machines by making machines depend on others. We should get to know this feature better.
- Due date changed from 2019-03-26 to 2019-06-04
- Target version changed from Milestone 23 to Milestone 25
We can do that after 15SP1 release
- Due date changed from 2019-06-04 to 2019-05-21
This is the key feature we could use to split test suites properly on the bare metal.
- Due date changed from 2019-05-21 to 2019-06-04
- Priority changed from Normal to Low
- Status changed from Workable to Resolved
So you mean the example of "trigger default@64bit-ipmi after default@64bit" is not covered, just as well as "default@s390x-kvm" after "default@64bit"? I wonder what would happen for example when you want to trigger "default@64bit-ipmi" after "default@64bit" you could just add (or try to add) START_AFTER_TEST="default:64bit" in the testsuite "default" so that every scenario for "default" would be able to fulfill that restriction except for default@64bit which should start immediately as it can not wait for itself ;) I might try that and see if I can help to add what is missing.
Also available in: Atom
PDF