Failure in qa/specs/features/ee/browser_ui/3_create/repository/file_locking_spec.rb:63
https://gitlab.com/gitlab-org/quality/nightly/-/jobs/308393359
5) Create File Locking creates a merge request and fails to merge
Failure/Error: expect(page).to have_text("locked by Administrator")
expected to find text "locked by Administrator" in "Skip to content Projects Groups More F file_locking-daa66fbbbcfad0f9 Project Repository Issues 0 Merge Requests 1 CI / CD Security & Compliance Operations Packages Wiki Snippets Members Collapse sidebar gitlab-qa-sandbox-group qa-test-2019-10-01-04-34-42-1fb7edb222c6e722 file_locking-daa66fbbbcfad0f9 Merge Requests !1 Open Opened just now by Administrator Edit Close merge request QA test - merge request This is a test merge request Request to merge test into master Open in Web IDE Check out branch Pipeline #9 pending for c318c739 on test Approve No approval required; you can still approve Merge in progress Delete source branch 1 commit and 1 merge commit will be added to master. Modify merge commit You can merge this merge request manually using the command line 0 0 Discussion 0 Commits 1 Pipelines 1 Changes 1 Show all activity Write Preview Markdown and quick actions are supported Attach a file Comment Close merge request To Do Add a To Do 0 Assignees Edit None - assign yourself Milestone Edit None Time tracking No estimate or time spent Labels Edit None Lock merge request Edit Unlocked 1 participant Notifications Reference: gitlab-qa-sandbox-group/qa-test-2019-10-01-04-34-42-1fb7edb222c6e722/file_locking-daa66fbbbcfad0f9!1". (However, . it was found 1 time including non-visible text.)
# ./qa/specs/features/ee/browser_ui/3_create/repository/file_locking_spec.rb:77:in `block (3 levels) in <module:QA>'
Screenshot from 1st retry:
Screenshot from 2nd retry:
Looks like there is a timing issue here. In the first retry screenshot, the merge is still in progress where as in the second one, we see the expected text "locked by Administrator" on the screen but the test still failed. That the text showed up right after a failure was registered.