-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
Coming out of https://redhat-internal.slack.com/archives/C01CQA76KMX/p1744654665553409
We need a place for tests to go that are disruptive (rebooting, tainting nodes), or excessively slow. (look for slow tests in current suite)
- Is disruptive overloaded, do we have another term that would fit with QE usage as well or live with disruptive?
Resurrect these suites, get tests tagged appropriately, check in with openshift-tests-extensions to make sure we're in sync, and stand up prow jobs to run these new suites.
- Start with small set and add as we go, new annotations?
Do not disable all monitortests, rather only those that make sense and are required.
- Can we profile monitortests to disable / enable in groups vs. each one individually
- * Synthetic events
- * Disruption
- * Standards enforcement
- * Etc
New jobs should run fairly often and be added to payloads.
New jobs should be categorized with a new Suite variant. Discussion around moving away from suite variant.
Team sync discussion regarding this
- is related to
-
OCPBUGS-54951 Multiple pods exiting an excessive amount of times on techpreview serial
-
- Closed
-
- links to