Transient failure in reverting_merge_spec | Unable to find css "[data-qa-selector=\"revert_button\"],.qa-revert-button"

Summary

Failure in reverting_merge_spec Unable to find css "[data-qa-selector=\"revert_button\"],.qa-revert-button"

Seen on Staging https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/5063925

Stack trace

 1) Create Merged merge request can be reverted
     Failure/Error: merge_request.revert_change!
     
     Capybara::ElementNotFound:
       Unable to find css "[data-qa-selector=\"revert_button\"],.qa-revert-button"
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:303:in `block in synced_resolve'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/base.rb:83:in `synchronize'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:292:in `synced_resolve'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/node/finders.rb:53:in `find'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/session.rb:762:in `find'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/dsl.rb:53:in `call'
     # /usr/local/bundle/gems/capybara-3.35.3/lib/capybara/dsl.rb:53:in `find'
     # ./qa/page/base.rb:206:in `click_element'
     # ./qa/support/page/logging.rb:80:in `click_element'
     # ./qa/page/merge_request/show.rb:361:in `revert_change!'
     # ./qa/specs/features/browser_ui/3_create/merge_request/revert/reverting_merge_request_spec.rb:31:in `block (4 levels) in <module:QA>'
     # ./qa/scenario/actable.rb:16:in `perform'
     # ./qa/specs/features/browser_ui/3_create/merge_request/revert/reverting_merge_request_spec.rb:29:in `block (3 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # ./spec/spec_helper.rb:82:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
     # ./qa/specs/runner.rb:74:in `perform'
     # ./qa/scenario/template.rb:10:in `block in perform'
     # ./qa/scenario/template.rb:8:in `tap'
     # ./qa/scenario/template.rb:8:in `perform'
     # ./qa/scenario/template.rb:44:in `perform'
     # ./qa/scenario/template.rb:10:in `block in perform'
     # ./qa/scenario/template.rb:8:in `tap'
     # ./qa/scenario/template.rb:8:in `perform'
     # ./qa/scenario/bootable.rb:28:in `launch!'

Screenshot / HTML page

Possible fixes

changed due date to October 19, 2021

changed milestone to %14.5

added QA Quality devopscreate failureinvestigating found:staging.gitlab.com test labels

cc @tomi

Thanks for the ping

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

@phikai @andr3 This seems like a bug to me, since the button did not appear according to the screenshot. I was not able to reproduce it, though, which indicates that this is a flaky behavior.

@tomi in looking at the screenshot there's quite a bit of inconsistency in that page. It shows the merge request as open, even though it shows the merge request in the widget as merged.

It almost seems like maybe the state of the page didn't actually get updated even though the merge request was merged? I'd suspect if the page isn't showing as merged we wouldn't show the revert button.

added failureflaky-test label and removed failureinvestigating label

@niskhakova When I mentioned flaky behavior, I meant that not the test is flaky, but the bug in the system. Do we still use failureflaky-test for that?

@tomi thanks for the ping! I've misread the message, let's update it back to failureinvestigating and add a note above that it's transient.

Initially marked it as investigating until we figure it out :)

added failureinvestigating label and removed failureflaky-test label

changed title from Failure in reverting_merge_spec | Unable to find css "[data-qa-selector="revert_button"],.qa-revert-button" to Transient failure in reverting_merge_spec | Unable to find css "[data-qa-selector="revert_button"],.qa-revert-button"

added sectiondev label

added [deprecated] Accepting merge requests label

changed milestone to %14.6

added missed:14.5 label

changed milestone to %14.7

added missed:14.6 label

changed milestone to %14.8

added missed:14.7 label

@tomi Are you still working on this? Have we seen it again?

I have not seen it recently, but I also was not able to get to it by now, so I'll have to look into it at some point this quarter

changed milestone to %14.9

added missed:14.8 label

changed milestone to %14.10

added missed:14.9 label

changed milestone to %15.0

added missed:14.10 label

changed milestone to %15.1

added missed:15.0 label

changed milestone to %15.2

added missed:15.1 label

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

changed milestone to %15.3

added missed:15.2 label

added typemaintenance label

added groupcode review label

changed milestone to %15.4

added missed:15.3 label

assigned to @jay_mccure

Occurred a month ago on staging and canary: gitlab-org/quality/testcases#2536 (comment 1015439185)

Will attempt to reproduce on staging.

removed [deprecated] Accepting merge requests label

unassigned @jay_mccure

added [deprecated] Accepting merge requests label

changed milestone to %15.5

added missed:15.4 label

changed milestone to %15.6

added missed:15.5 label

Failed in master: https://gitlab.com/gitlab-org/gitlab/-/jobs/3248433802

Revert button intermittently doesn't register the click.

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

changed milestone to %15.7

added missed:15.6 label

changed milestone to %15.8

added missed:15.7 label

assigned to @jay_mccure

No occurrences for 4 months, there has been reliability improvements to this test so I will close. !107704 (merged)

closed