Use project name only for container images in QA tests

added QA label

	3 Warnings
	Please add a merge request subtype to this merge request.
	Please add a merge request type to this merge request.
	This merge request does not refer to an existing milestone.

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	Careem Ahamed (`@cahamed`) (UTC+8, 2 hours behind `@jay_mccure`)	Dan Davison (`@ddavison`) (UTC-4, 14 hours behind `@jay_mccure`)

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

added Quality typemaintenance labels

requested review from @nwestbury

Hi @nwestbury , would you be able to review this? It is for a failure that has started happening recently.

Here is an example of the jobs that fail because of it: https://gitlab.com/gitlab-org/gitlab/-/pipelines/684201878#/

Thanks!

mentioned in issue gitlab-org/quality/pipeline-triage#170 (closed)

Allure report

allure-report-publisher generated test report!

e2e-package-and-test: test report for 2180139a

expand test summary

+--------------------------------------------------------------+
|                        suites summary                        |
+---------+--------+--------+---------+-------+-------+--------+
|         | passed | failed | skipped | flaky | total | result |
+---------+--------+--------+---------+-------+-------+--------+
| Package | 18     | 0      | 0       | 0     | 18    | ✅     |
+---------+--------+--------+---------+-------+-------+--------+
| Total   | 18     | 0      | 0       | 0     | 18    | ✅     |
+---------+--------+--------+---------+-------+-------+--------+

approved this merge request

LGTM!

resolved all threads

merged

@sliaquat, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

Ensure the merge request is not in Draft status.
Start a pipeline (especially important for Community contribution merge requests).
Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.