Quarantine stale mde test
What does this MR do?
Quarantines specs/features/browser_ui/1_manage/login/maintain_login_mixed_env_spec.rb.
This spec is stale due to refactorings in our approach to mixed deployment environment specific tests. Technically, the fix will be ready in less than 24 hours, but it has a dependency on an environment change coming in the next day.
E2E Test Failure issue(s)
Related to: #344213 (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).
-
Merge request reports
Activity
changed milestone to %14.5
added QA Quality devopsmanage typemaintenance labels
assigned to @zeffmorgan
1 Message CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer QA Tiffany Rea ( @treagitlab
) (UTC-8, 3 hours behind@zeffmorgan
)Anastasia McDonald ( @a_mcdonald
) (UTC+13, 18 hours ahead of@zeffmorgan
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Zeff Morgan
mentioned in merge request gitlab-org/quality/staging-canary!1 (merged)
Allure report
allure-report-publisher
generated test report for a61329b1!review-qa-smoke:
test report
review-qa-all: test reportadded 108 commits
-
842c8628...1c5f0fcb - 106 commits from branch
master
- 892721ff - Quarantine stale mde test
- a61329b1 - Restrict to staging
-
842c8628...1c5f0fcb - 106 commits from branch
enabled an automatic merge when the pipeline for 772dbd86 succeeds
@acunskis
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.
For more info, please refer to the following links:
mentioned in issue #341427 (closed)
mentioned in commit 9ab10b34
added workflowstaging-canary label
added workflowstaging label and removed workflowstaging-canary label
mentioned in issue gitlab-com/gl-infra/production#5890 (closed)
mentioned in issue #345209 (closed)
mentioned in issue gitlab-org/quality/pipeline-triage#107 (closed)
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
mentioned in issue #344213 (closed)