Failure in browser_ui/4_verify/ci_job_artifacts/unlocking_job_artifacts_across_pipelines_spec.rb | Verify Unlocking job artifacts across pipelines when latest pipeline failed keeps job artifacts from latest failed pipelines and from latest successful p...
Full description
Verify Unlocking job artifacts across pipelines when latest pipeline failed keeps job artifacts from latest failed pipelines and from latest successful pipeline
The test has failed consistently in 10 jobs in the last two master pipelines.
File path
./qa/specs/features/browser_ui/4_verify/ci_job_artifacts/unlocking_job_artifacts_across_pipelines_spec.rb
Stack trace
Failure/Error: expect(job).to have_unlocked_artifact
expected `QA::Page::Project::Job::Show.has_unlocked_artifact?` to be truthy, got falseScreenshot
Expand
The screenshot shows the wrong message. It expects The artifacts will be removed but the screenshot shows These artifacts are the latest. They will not be deleted (even if expired) until newer artifacts are available
First happened in https://gitlab.com/gitlab-org/gitlab/-/jobs/4027799593.
Related test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/394808.
Designs
Activity
added QA Quality failurenew found:main priority2 test labels
Failed most recently in production pipeline: https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/10040288
Edited by GitLab QA Botassigned to @treagitlab
mentioned in issue gitlab-org/quality/testcase-sessions#67887 (closed)
marked #403181 (closed) as a duplicate of this issue
marked this issue as related to #403181 (closed)
mentioned in issue gitlab-org/quality/pipeline-triage#191 (closed)
The test was updated a week ago, so that shouldn't be the reason it's failing. !115301 (merged)
-
This related MR was just merged yesterday: !114426 (merged)
Edited by Mark Lapierre -
OIC !116207 (merged)
-
I didn't realize that the was same MR that was reverted in !116144 (merged)
I merged the quarantine MR so the pipelines should be clear again soon.
mentioned in merge request !116207 (merged)
added found:canary.gitlab.com label
mentioned in issue gitlab-org/quality/testcase-sessions#67898 (closed)
mentioned in issue gitlab-org/quality/testcase-sessions#67899 (closed)
This issue was automatically tagged with the label grouppipeline execution by TanukiStan, a machine learning classification model, with a probability of 0.85.
If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.
If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.
Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan
This message was generated automatically. You're welcome to improve it.
- A deleted user
added automation:ml grouppipeline execution labels
added devopsverify sectionops labels
mentioned in issue gitlab-org/quality/testcase-sessions#67904 (closed)
mentioned in issue gitlab-org/quality/testcase-sessions#67907 (closed)
added found:staging.gitlab.com label
mentioned in issue gitlab-org/quality/testcase-sessions#67915 (closed)
added found:gitlab.com label
mentioned in issue gitlab-org/quality/testcase-sessions#67917 (closed)
mentioned in issue gitlab-org/quality/testcase-sessions#67918 (closed)
mentioned in issue gitlab-org/quality/testcase-sessions#67932 (closed)
added found:pre.gitlab.com ~17053143 quarantinebug labels
assigned to @alberts-gitlab and unassigned @treagitlab
added grouppipeline security label and removed grouppipeline execution label
added found:canary.staging.gitlab.com label
added found:nightly label
added Category:Build Artifacts label
changed milestone to %Backlog
mentioned in issue gitlab-org/quality/pipeline-triage#194 (closed)
mentioned in issue gitlab-org/quality/pipeline-triage#195 (closed)
added auto closed label
