Project

General

Profile

Actions
Copy link

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 over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Enhancement to existing tests
Target version:
openQA Project (public) - Ready
Start date:
2021-06-25
Due date:
% Done:

0%

Estimated time:
Difficulty:
Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Subject changed from Prevent rogue SCC servers to break maintenance tests to [tools] Prevent rogue SCC servers to break maintenance tests
Actions
Copy link
 #2

Updated by okurz over 3 years ago

  • 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

Adding "auto_review" keyword with automatic retry after we have the PR with fix https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12789 in the test code merged

Actions
Copy link
 #3

Updated by okurz over 3 years ago

I guess only the tests that use the interactive GUI installer are affected so maybe not all. And complete product builds can be retriggered over the UI. I am trying out a solution based on a customized version of https://github.com/os-autoinst/openQA/blob/master/script/openqa-label-all applying to all builds but this solution might take minutes-hours due to the big load of affected tests.

EDIT: Retriggering in process …
EDIT: Retriggering done. Around 3.5k jobs were scheduled, see https://monitor.qa.suse.de/d/nRDab3Jiz/openqa-jobs-test?viewPanel=9&orgId=1&from=1624614664624&to=1624620353910

Actions
Copy link
 #4

Updated by okurz over 3 years ago

Created improvement to "openqa-label-all" with https://github.com/os-autoinst/openQA/pull/3978

Actions
Copy link
 #5

Updated by okurz over 3 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #6

Updated by okurz over 3 years ago

  • Status changed from Feedback to Resolved

All jobs seem to be good now.

Actions
Copy link
 #7

Updated by openqa_review over 3 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed
Actions
Copy link
 #8

Updated by okurz over 3 years ago

Reported #95338 about the unexpected reminder message and moved the affected job group of https://openqa.suse.de/tests/6329597 to "EOL"

Actions
Copy link
 #9

Updated by openqa_review over 3 years ago

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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed
Actions
Copy link

Also available in: Atom PDF