Flaky test ee/spec/features/projects/mirror_spec.rb:110 # Project mirror configuration password authentication can be set up
Job #1218633774 failed for b8ea06e5:
1) Project mirror configuration password authentication can be set up
Failure/Error: expect(page).to have_content('Mirroring settings were successfully updated')
expected to find text "Mirroring settings were successfully updated" in "Skip to content GitLab Projects Help P project74 Project overview Repository Issues 0 Merge requests 0 CI/CD Security & Compliance Operations Packages & Registries Analytics Wiki Snippets Members Settings General Integrations Webhooks Access Tokens Repository CI/CD Operations Collapse sidebar John Doe218 project74 Repository Settings Import url can't be blank Default branch Collapse Set the default branch for this project. All merge requests and commits are made against this branch unless you specify a different one. Default branch master Default branch Auto-close referenced issues on default branch When merge requests and commits in the default branch close, any issues they reference also close. Push rules Collapse Restrict push operations for this project. Learn more. Select push rules Do not allow users to remove Git tags with git push Users can still delete tags through the GitLab UI. Check whether the commit author is a GitLab user Restrict commits to existing GitLab users. Prevent pushing secret files Reject any files likely to contain secrets. What secret files are rejected? Require expression in commit messages All commit messages must match this regular expression. If empty, commit messages are not required to match any expression. Reject expression in commit messages Commit messages cannot match this regular expression. If empty, commit messages are not rejected based on any expression. Branch name All branch names must match this regular expression. If empty, any branch name is allowed. Commit author's email All commit author's email must match this regular expression. If empty, any email is allowed. Prohibited file names All committed filenames cannot match this regular expression. If empty, any filename is allowed. Maximum file size (MB) Reject file sizes equal to or greater than this size. If set to 0, files of any size are allowed. This rule does not apply to files tracked by Git LFS. Mirroring repositories Collapse Set up your project to automatically push and/or pull changes to/from another repository. Branches, tags, and commits will be synced automatically. How do I mirror repositories? Git repository URL The repository must be accessible over http://, https://, ssh:// or git://. When using the http:// or https:// protocols, provide the exact URL to the repository. HTTP redirects will not be followed. Include the username in the URL if required: https://username@gitlab.company.com/group/project.git. The update action will time out after 180 minutes. For big repositories, use a clone/push combination. Git LFS objects will be synced if LFS is enabled for the project. Push mirrors will not sync LFS objects over SSH. In case of pull mirroring, your user will be the author of all events in the activity feed that are the result of an update, like new branches being created or new commits being pushed to existing branches. Mirror direction Pull Push Authentication method Password SSH public key Password Mirror user John Doe217 You will be the author of all events in the activity feed that are the result of an update, like new branches being created or new commits being pushed to existing branches. Overwrite diverged branches If disabled, a diverged local branch will not be automatically updated with commits from its remote counterpart, to prevent local data loss. If the default branch (master) has diverged and cannot be updated, mirroring will fail. Other diverged branches are silently ignored. Learn more. Trigger pipelines for mirror updates Trigger pipelines when branches or tags are updated in the upstream repository. Depending on the activity of the upstream repository, this may greatly increase the load on your CI runners. Only enable this if you know they can handle the load. CI will run using the credentials assigned above. Learn more. Mirror only protected branches If enabled, only protected branches will be mirrored. Learn more. Mirrored repositories (0) Direction Last update attempt Last successful update Protected branches Collapse Keep stable branches secure, and force developers to use merge requests. What are protected branches? By default, protected branches protect your code and: Allow only users with Maintainer permissions to create new protected branches. Allow only users with Maintainer permissions to push code. Prevent anyone from force-pushing to the branch. Prevent anyone from deleting the branch. Protect a branch Branch: Select branch or create wildcard Wildcards such as *-stable or production/* are supported. Allowed to merge: Select Allowed to push: Select You can add only groups that have this project shared. Learn more. Allow force push: Allow force push for all users with push access. Protected branch (0) There are currently no protected branches, protect a branch with the form above. Protected tags Collapse Limit access to creating and updating tags. What are protected tags? By default, protected tags protect your code and: Allow only users with Maintainer permissions to create tags. Prevent anyone from updating tags. Prevent anyone from deleting tags. Protect a tag Tag: Select tag or create wildcard Wildcards such as v* or *-release are supported. Allowed to create: Select You can add only groups that have this project shared. Learn more. Protected tags (0) No tags are protected. Deploy tokens Collapse Deploy tokens allow access to packages, your repository, and registry images. Add a deploy token Pick a name for your unique deploy token. Name Expires at (optional) Unless you enter a date, the token does not expire. Username (optional) Unless you specify a username, it is set to \"gitlab+deploy-token-{n}\". Scopes [Select 1 or more] read_repository Allows read-only access to the repository. read_package_registry Allows read access to the package registry. write_package_registry Allows write access to the package registry. Active Deploy Tokens (0) This project has no active Deploy Tokens. Deploy keys Collapse Add deploy keys to grant read/write access to this repository. What are deploy keys? Title Key Paste a public key here. How do I generate it? Grant write permissions to this key Allow this key to push to this repository Enabled deploy keys 0 Privately accessible deploy keys 0 Publicly accessible deploy keys 0 No deploy keys found. Create one with the form above. Repository cleanup Collapse Clean up after running git filter-repo on the repository. Upload object map Choose a file No file selected The maximum file size is 10 MB."
# ./ee/spec/features/projects/mirror_spec.rb:120:in `block (4 levels) in <top (required)>'
# ./spec/spec_helper.rb:355:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:346:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:342:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:31:in `with_raw_context'
# ./spec/spec_helper.rb:342:in `block (2 levels) in <top (required)>'
Finished in 17 minutes 20 seconds (files took 40.11 seconds to load)
328 examples, 1 failure, 1 pending
Failed examples:
rspec ./ee/spec/features/projects/mirror_spec.rb:110 # Project mirror configuration password authentication can be set up
project_mirror_configuration_password_authentication_can_be_set_up.html
Edited by Rémy Coutable