Quarantine flaky integration tests

What does this MR do and why?

Quarantine flaky integration tests

• the request for searchProjectMembers is causing issues in the tests, so we are going to disable them

EE: true

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #10898

changed milestone to %17.10

assigned to @aturinske

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#10898 (closed)

added pipelinetier-1 label

added frontend label

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	@cindy-halim (UTC+9, 16 hours ahead of author)	@pslaughter (UTC-5, 2 hours ahead of author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

mentioned in issue #523910

added Category:Security Policy Management GitLab Ultimate devopssecurity risk management groupsecurity policies sectionsec labels

added typebug workflowin review labels

added 1 commit

• 5996229b - Quarantine flaky integration tests

Compare with previous version

@psimyn can you review this? Thanks

requested review from @psimyn

/cc @arfedoro

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

enabled automatic add to merge train when checks pass

mentioned in incident gitlab-org/quality/engineering-productivity/approved-mr-pipeline-incidents#1949

mentioned in incident gitlab-org/quality/engineering-productivity/approved-mr-pipeline-incidents#1971