Quarantine jenkins_build_status_spec due to failures in nightly
What does this MR do?
I've missed something during !83268 (merged) which is causing failures in nightly builds. Adding test back to quarantine until I can investigate it to avoid failures.
E2E Test Failure issue(s)
#356488 (closed) #195179 (closed)
Check-list
-
General code guidelines check-list -
Quarantine test check-list -
Follow the Quarantining Tests guide. -
Confirm the test has a quarantine:
tag with the specified quarantine type. -
Note if the test should be quarantined for a specific environment. -
(Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
-
-
Dequarantine test check-list -
Follow the Dequarantining Tests guide. -
Confirm the test consistently passes on the target GitLab environment(s). -
(Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE
variable from thepackage-and-qa
job of the current merge request.
-
-
-
To ensure a faster turnaround, ask in the #quality
Slack channel for someone to review and merge the merge request, rather than assigning it directly.
Edited by John McDonnell