Spec failure on `master` due spec/requests/api/projects_spec.rb
This was perhaps introduced from a combination of these two merge requests:
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11850
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11851
Example build: https://gitlab.com/gitlab-org/gitlab-ce/builds/17948098
Failures:
1) API::Projects POST /projects/:id/fork when authenticated forks if user has sufficient access to project
Failure/Error: expect(json_response['import_status']).to eq('started')
expected: "started"
got: "scheduled"
(compared using ==)
# ./spec/requests/api/projects_spec.rb:1483:in `block (4 levels) in <top (required)>'
2) API::Projects POST /projects/:id/fork when authenticated forks if user is admin
Failure/Error: expect(json_response['import_status']).to eq('started')
expected: "started"
got: "scheduled"
(compared using ==)
# ./spec/requests/api/projects_spec.rb:1496:in `block (4 levels) in <top (required)>'
Finished in 31 minutes 53 seconds (files took 25.15 seconds to load)
1061 examples, 2 failures
Failed examples:
rspec ./spec/requests/api/projects_spec.rb:1474 # API::Projects POST /projects/:id/fork when authenticated forks if user has sufficient access to project
rspec ./spec/requests/api/projects_spec.rb:1487 # API::Projects POST /projects/:id/fork when authenticated forks if user is admin