Quarantines failing import specs
What does this MR do?
Several of the import tests just kept failing the entire week this week and has caused package-and-test
to fail a lot. The cause of the failure is still unknown and pending investigation. They all appear to be failing because the import state doesn't match what is expected. All of them fail with the following error message:
Expected import to finish successfully, but status was: started
E2E Test Failure issue(s)
- #415270 (closed)
- #415247 (closed)
- #415271 (closed)
- #415245 (closed)
- #415272 (closed)
- #415246 (closed)
- #415292 (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).
-
-
To ensure a faster turnaround, ask in the #quality_maintainers
Slack channel for someone to review and merge the merge request, rather than assigning it directly.
Edited by Richard Chong