Multiple QA failures due to WaitExceededError
<!---
Before opening a new QA failure issue, make sure to first search for it in the
QA failures board: https://gitlab.com/groups/gitlab-org/-/boards/1385578
The issue should have the following:
- The relative path of the failing spec file in the title, e.g. if the login
test fails, include `qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb` in the title.
This is required so that existing issues can easily be found by searching for the spec file.
- If the issue is about multiple test failures, include the path for each failing spec file in the description.
- A link to the failing job.
- The stack trace from the job's logs in the "Stack trace" section below.
- A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below.
- A link to the corresponding test case(s) in the summary.
--->
### Summary
Multiple specs are failing due to `WaitExceededError`
Example pipelines:
- https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/1831326
- https://ops.gitlab.net/gitlab-org/quality/canary/-/pipelines/1831325
### Stack trace
```ruby
1) Create Reverting a commit creates a merge request
Failure/Error: merge_request.click_diffs_tab
QA::Support::Repeater::WaitExceededError:
Wait failed after 60 seconds
# ./qa/support/repeater.rb:74:in `repeat_until'
# ./qa/support/waiter.rb:20:in `wait_until'
# ./qa/page/base.rb:63:in `wait_until'
# ./qa/page/merge_request/show.rb:207:in `click_diffs_tab'
# ./qa/specs/features/browser_ui/3_create/merge_request/revert/revert_commit_spec.rb:33:in `block (4 levels) in <module:QA>'
# ./qa/scenario/actable.rb:16:in `perform'
# ./qa/specs/features/browser_ui/3_create/merge_request
1) Create Merge request push options removes the source branch
Failure/Error:
Resource::Repository::ProjectPush.fabricate! do |push|
push.project = project
push.branch_name = branch
push.merge_request_push_options = {
create: true,
remove_source_branch: true,
title: title
}
end
QA::Resource::Events::EventNotFoundError:
Timed out waiting for event
# ./qa/resource/events/base.rb:44:in `wait_for_
```
### Screenshot / HTML page
<!--
Attach the screenshot and HTML snapshot of the page from the job's artifacts:
1. Download the job's artifacts and unarchive them.
1. Open the `gitlab-qa-run-2020-*/gitlab-{ce,ee}-qa-*/{,ee}/{api,browser_ui}/<path to failed test>` folder.
1. Select the `.png` and `.html` files that appears in the job logs (look for `HTML screenshot: /path/to/html/page.html` / `Image screenshot: `/path/to/html/page.png`).
1. Drag and drop them here.
Note: You don't need to include a screenshot if the information it contains can be included as text. Include the text instead.
E.g., error 500/404, "Retry later" errors, etc.
If you include multiple screenshots it can be helpful to hide all but the first in a details/summary element, to avoid excessive scrolling:
<details><summary>Expand for screenshot</summary>
drag and drop the screenshot here
</details>
-->
### Possible fixes
<!-- Default due date. -->
<!-- Base labels. -->
<!-- Work classification type label, please apply ignore type label until the investigation is complete and an [issue type](https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification) is determined.-->
<!-- Test failure type label, please use just one.-->
<!--
Choose the stage that appears in the test path, e.g. ~"devops::create" for
`qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb`.
-->
<!--
Select a label for where the failure was found, e.g. if the failure occurred in
a nightly pipeline, select ~"found:nightly".
-->
<!--
https://about.gitlab.com/handbook/engineering/quality/guidelines/#priorities:
- ~"priority::1": Tests that are needed to verify fundamental GitLab functionality.
- ~"priority::2": Tests that deal with external integrations which may take a longer time to debug and fix.
-->
<!-- Select the current milestone if ~"priority::1" or the next milestone if ~"priority::2". -->
issue