Transient failure in `qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb[1:1:1:1:1]` / `expected QA::Git::Repository::RepositoryCommandError with message [...] \(pre-receive hook declined\)/ but nothing was raised`
As seen in https://gitlab.com/gitlab-org/gitlab-qa/-/jobs/400497662:
5116 1) Create Restricted protected branch push and merge when only one user is allowed to merge and push to a protected branch behaves like only user with access pushes and merges unselected maintainer user fails to push
5117 Failure/Error:
5118 expect { push_new_file(branch_name, as_user: user_maintainer) }.to raise_error(
5119 QA::Git::Repository::RepositoryCommandError,
5120 /remote: GitLab: You are not allowed to push code to protected branches on this project\.([\s\S]+)\[remote rejected\] #{branch_name} -> #{branch_name} \(pre-receive hook declined\)/)
5121
5122 expected QA::Git::Repository::RepositoryCommandError with message matching /remote: GitLab: You are not allowed to push code to protected branches on this project\.([\s\S]+)\[remote rejected\] protected-branch -> protected-branch \(pre-receive hook declined\)/ but nothing was raised
5123 Shared Example Group: "only user with access pushes and merges" called from ./qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:62
5124 # ./qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:13:in `block (4 levels) in <module:QA>'
5125 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
5126 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
5127 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
5128 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
5129 # ./spec/spec_helper.rb:68:in `block (2 levels) in <top (required)>'
5130 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
5131 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `loop'
5132 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:110:in `run'
5133 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
5134 # /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
5135 # ./qa/specs/runner.rb:69:in `perform'
5136 # ./qa/scenario/template.rb:10:in `block in perform'
5137 # ./qa/scenario/template.rb:8:in `tap'
5138 # ./qa/scenario/template.rb:8:in `perform'
5139 # ./qa/scenario/template.rb:33:in `perform'
5140 # ./qa/scenario/template.rb:10:in `block in perform'
5141 # ./qa/scenario/template.rb:8:in `tap'
5142 # ./qa/scenario/template.rb:8:in `perform'
5143 # ./qa/scenario/bootable.rb:28:in `launch!'
5144 Top 10 slowest examples (652.18 seconds, 59.6% of total time):
5145 Release Pipelines for merged results and merge trains merges via a merge train
5146 88.73 seconds ./qa/specs/features/ee/browser_ui/6_release/pipelines_for_merged_results_and_merge_trains_spec.rb:87
5147 Secure Security Reports in a Merge Request can create an auto-remediation MR
5148 83.48 seconds ./qa/specs/features/ee/browser_ui/secure/create_merge_request_with_secure_spec.rb:101
5149 Secure Security Reports in a Merge Request can create an issue from a vulnerability
5150 80.84 seconds ./qa/specs/features/ee/browser_ui/secure/create_merge_request_with_secure_spec.rb:90
5151 Create Approval rules allows multiple approval rules with users and groups
5152 66.42 seconds ./qa/specs/features/ee/browser_ui/3_create/merge_request/approval_rules_spec.rb:26
5153 Secure Security Reports in a Merge Request displays the Security reports in the merge request
5154 63.72 seconds ./qa/specs/features/ee/browser_ui/secure/create_merge_request_with_secure_spec.rb:64
5155 Secure Security Reports in a Merge Request can dismiss a vulnerability with a reason
5156 61.54 seconds ./qa/specs/features/ee/browser_ui/secure/create_merge_request_with_secure_spec.rb:78
5157 Create Restricted protected branch push and merge when only one user is allowed to merge and push to a protected branch behaves like only user with access pushes and merges unselected maintainer user fails to push
5158 55.71 seconds ./qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:12
5159 Create Restricted protected branch push and merge when only one group is allowed to merge and push to a protected branch behaves like only user with access pushes and merges selected developer user pushes and merges
5160 54.74 seconds ./qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:18
5161 Create Protected branch support when developers and maintainers are not allowed to push to a protected branch user without push rights fails to push to the protected branch
5162 49.94 seconds ./qa/specs/features/browser_ui/3_create/repository/push_protected_branch_spec.rb:33
5163 Manage Group audit logs Enable and disable allow user request access behaves like group audit event logs logs audit events
5164 47.06 seconds ./qa/specs/features/ee/browser_ui/1_manage/group/group_audit_logs_2_spec.rb:7
5165 Top 10 slowest example groups:
5166 Secure
5167 72.4 seconds average (289.59 seconds / 4 examples) ./qa/specs/features/ee/browser_ui/secure/create_merge_request_with_secure_spec.rb:6
5168 Release
5169 67.64 seconds average (135.28 seconds / 2 examples) ./qa/specs/features/ee/browser_ui/6_release/pipelines_for_merged_results_and_merge_trains_spec.rb:6
5170 Create
5171 66.43 seconds average (66.43 seconds / 1 example) ./qa/specs/features/ee/browser_ui/3_create/merge_request/approval_rules_spec.rb:4
5172 Create
5173 48.46 seconds average (193.84 seconds / 4 examples) ./qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb:4
5174 Create
5175 35.68 seconds average (71.36 seconds / 2 examples) ./qa/specs/features/browser_ui/3_create/repository/push_protected_branch_spec.rb:4
5176 Create
5177 31.73 seconds average (63.45 seconds / 2 examples) ./qa/specs/features/browser_ui/3_create/merge_request/create_merge_request_spec.rb:4
5178 Create
5179 26.84 seconds average (26.84 seconds / 1 example) ./qa/specs/features/browser_ui/3_create/repository/use_ssh_key_spec.rb:4
5180 Verify
5181 24.29 seconds average (24.29 seconds / 1 example) ./qa/specs/features/browser_ui/4_verify/runner/register_runner_spec.rb:4
5182 Plan
5183 20.11 seconds average (40.23 seconds / 2 examples) ./qa/specs/features/ee/browser_ui/2_plan/multiple_assignees_for_issues/more_than_four_assignees_spec.rb:4
5184 Manage
5185 17.29 seconds average (34.59 seconds / 2 examples) ./qa/specs/features/ee/browser_ui/1_manage/insights/default_insights_spec.rb:4
5186 Finished in 18 minutes 14 seconds (files took 41.47 seconds to load)
5187 36 examples, 1 failure, 5 pending
5188 Failed examples:
5189 rspec './qa/specs/features/ee/browser_ui/3_create/repository/restrict_push_protected_branch_spec.rb[1:1:1:1:1]' # Create Restricted protected branch push and merge when only one user is allowed to merge and push to a protected branch behaves like only user with access pushes and merges unselected maintainer user fails to push
It looks like the protected branch isn't created (the form is filled but the "Protect" button is disabled and the branch isn't listed in the protected branches list along with master
):
restrict_push_protected_branch_spec.rb_2020-01-12-19-52-16.933.html
Edited by Rémy Coutable