Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Low
Assignee:
riafarov
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 25
Start date:
2019-02-18
Due date:
2019-06-04
% Done:

0%

Estimated time:
Difficulty:

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.

Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • 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

Actions
Copy link
 #2

Updated by riafarov about 5 years ago

  • 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.

Actions
Copy link
 #3

Updated by JERiveraMoya almost 5 years ago

  • Due date changed from 2019-05-21 to 2019-06-04
Actions
Copy link
 #4

Updated by riafarov almost 5 years ago

  • Priority changed from Normal to Low
Actions
Copy link
 #5

Updated by riafarov almost 5 years ago

  • Assignee set to riafarov
Actions
Copy link
 #6

Updated by riafarov almost 5 years ago

  • Status changed from Workable to Resolved

So feature works pretty much as described here: https://github.com/os-autoinst/openQA/blob/master/docs/WritingTests.asciidoc#inter-machine-dependencies
Problem is that it requires different test suites settings, which makes it unusable for main scenario we wanted to apply it to, namely trigger e.g. s390x kvm after 64bit run succeeded. So we should keep this feature in mind and consider extending it.

Actions
Copy link
 #7

Updated by okurz almost 5 years ago

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.

Actions
Copy link

Also available in: Atom PDF