action #94714
closed
action #94696: [qe-yast][qe-core][epic] optimize maintenance tests (was: test fails in welcome as a rogue RMT server popped up, blocking maintenance tests on the SCC/RMT selection dialog)
[tools] Prevent rogue SCC servers to break maintenance tests auto_review:"2021-06-25.*no candidate needle.*scc-invalid-url":retry
Added by okurz almost 3 years ago.
Updated almost 3 years ago.
Category:
Enhancement to existing tests
- Subject changed from Prevent rogue SCC servers to break maintenance tests to [tools] Prevent rogue SCC servers to break maintenance tests
- Subject changed from [tools] Prevent rogue SCC servers to break maintenance tests to [tools] Prevent rogue SCC servers to break maintenance tests auto_review:"2021-06-25.*no candidate needle.*scc-invalid-url":retry
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
All jobs seem to be good now.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: btrfs
https://openqa.suse.de/tests/6329597
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: btrfs
https://openqa.suse.de/tests/6329597
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Also available in: Atom
PDF