Dequarantine CS test but leave out of smoke suite
What does this MR do and why?
Dequarantines the Code Suggestions E2E test.
The test was quarantined when it started failing in the smoke suite, but it was passing in the full suite and passes now in full/smoke pipelines.
Smoke failure investigation ongoing in: #431317 (closed)
Test runs
I ran the test in the 4 pipelines it's restricted to and they all passed:
- https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/11867124
- https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/jobs/11867125
- https://ops.gitlab.net/gitlab-org/quality/canary/-/jobs/11867126
- https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/11867128
How to set up and validate locally
It can only be run against Staging or Prod. See instructions in !131604 (merged)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @mlapierre
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@mlapierre - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
changed milestone to %16.6
added QA Quality maintenancepipelines typemaintenance labels
changed milestone to %16.7
mentioned in issue #431317 (closed)
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 @dchevalier2
(UTC-5, 16 hours behind author)
@a_mcdonald
(UTC+13, 2 hours ahead of author)
Please check reviewer's status!
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
DangerAllure report
allure-report-publisher
generated test report!e2e-package-and-test:
test report for 7054dc5bexpand test summary
+---------------------------------------------------------------+ | suites summary | +----------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------+--------+--------+---------+-------+-------+--------+ | ModelOps | 0 | 0 | 4 | 0 | 4 | ➖ | +----------+--------+--------+---------+-------+-------+--------+ | Total | 0 | 0 | 4 | 0 | 4 | ➖ | +----------+--------+--------+---------+-------+-------+--------+
requested review from @at.ramya
enabled an automatic merge when the pipeline for f60a4d9b succeeds
mentioned in commit f50a7564
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added releasedcandidate label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
mentioned in issue gitlab-org/quality/pipeline-triage#227 (closed)