[Reason: Bug in Code] Failure in "./qa/specs/features/ee/browser_ui/3_create/repository/file_locking_spec.rb:62"
Bug issue: #40125 (closed)
Failing job example: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/785425
1) Create File Locking creates a merge request and fails to merge
Failure/Error: expect(page).to have_text("locked by #{admin_username}")
expected to find text "locked by QA User (Quality Team's Test Account)" in "Skip to content Projects Groups More 17 2 26 F file_locking-43dfe0ed31cbf08d Project overview Repository Issues 0 Merge Requests 1 CI / CD Security & Compliance Operations Packages Wiki Snippets Members Collapse sidebar gitlab-qa-sandbox-group qa-test-2019-12-11-15-55-23-61d47c0cc38b9116 file_locking-43dfe0ed31cbf08d Merge Requests !1 Open Opened just now by QA User (Quality Team's Test Account) Edit Close merge request QA test - merge request Overview 0 Commits 1 Pipelines 1 Changes 1 This is a test merge request Request to merge test into master Open in Web IDE Check out branch Pipeline #12692877 running for 3d06379e on test Will deploy to review/test Approve No approval required; you can still approve View eligible approvers Merge when pipeline succeeds Delete source branch 1 commit and 1 merge commit will be added to master. Modify merge commit Merge failed: Something went wrong during merge pre-receive hook. The path 'file' is locked by QA User (Quality Team's Test Account). Please try again. You can merge this merge request manually using the command line 0 0 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-12-11-15-55-23-61d47c0cc38b9116/file_locking-43dfe0ed31cbf08d!1 Now you can access the merge request navigation tabs at the top, where they’re easier to find. More information and share feedback Got it"
# ./qa/specs/features/ee/browser_ui/3_create/repository/file_locking_spec.rb:76:in `block (3 levels) in <module:QA>'
The error message is not properly decoding text, causing our text validation to fail on Staging when the user's full name has an apostrophe. See the bug issue for more details.
Edited by Aleksandr Soborov