Failure in browser_ui/3_create/repository/add_new_branch_rule_spec.rb | Create Branch Rules Overview adds a new branch rule

Full description

Create Branch Rules Overview adds a new branch rule

File path

./qa/specs/features/browser_ui/3_create/repository/add_new_branch_rule_spec.rb

Stack trace

Failure/Error: Page::Project::Settings::Repository.perform(&:expand_branch_rules)

Capybara::ElementNotFound:
  Unable to find css "[data-qa-selector=\"branch_rules_content\"],.qa-branch-rules-content"

First happened in https://gitlab.com/gitlab-org/gitlab/-/jobs/4036491046.

Related test case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/397587.

added QA Quality failurenew found:main priority2 test labels

Failed most recently in main pipeline: https://gitlab.com/gitlab-org/gitlab/-/jobs/4038084368

changed due date to April 30, 2023

assigned to @jay_mccure

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

Hi @a_mcdonald , could this be feature flag related? The second time this failed in the screenshot there is no Branch Rules. Unless it is EE only?

No, the feature is not a EE one, looks like a feature flag flakiness. Possibly because it failed on the first run, ff got disabled in after part and it took longer for switch on toggle to come into effect again We can try adding a waiting time with refresh? Unfortunately, we get this with ff toggling from time to time

added found:nightly label

This issue was automatically tagged with the label groupsource code by TanukiStan, a machine learning classification model, with a probability of 0.93.

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.

added automation:ml groupsource code labels

added devopscreate sectiondev labels

mentioned in issue gitlab-org/quality/testcase-sessions#68001 (closed)

added failureflaky-test label and removed failurenew label

I'm going to quarantine the spec as it's failing intermittently

mentioned in merge request !116396 (merged)

Setting label(s) Category:Source Code Management based on groupsource code.

added Category:Source Code Management label

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

mentioned in issue #397587

added typeignore label

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

mentioned in merge request !123368 (merged)

Once !123368 (merged) is merged, which removed the FF altogether I will de-quarantine this test

changed due date to June 15, 2023

changed milestone to %16.2

marked this issue as blocked by #404595 (closed)

created branch 403583-failure-in-browser_ui-3_create-repository-add_new_branch_rule_spec-rb-create-branch-rules to address this issue

mentioned in merge request !123753 (merged)

Test is enabled again

removed the relation with #404595 (closed)

closed