FOSS pipeline failure: spec/features/projects/settings/repository_settings_spec.rb
The following tests failed in FOSS master pipeline today:
Failures:
1) Projects > Settings > Repository settings for maintainer remote mirror settings creates a push mirror that mirrors all branches
Got 1 failure and 1 other error:
1.1) 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 / Help P project2 Project information Issues 0 Merge requests 0 CI/CD Security & Compliance Deployments Packages and registries Infrastructure Monitor Analytics Wiki Snippets Settings General Integrations Webhooks Access Tokens Repository Merge requests CI/CD Packages and registries Monitor Usage Quotas Collapse sidebar Sidney Jones4 project2 Repository Settings An error occurred while loading branch rules. Please try again. Branch defaults Collapse Select the default branch for this project, and configure the template for branch names. A default branch cannot be chosen for an empty project. Auto-close referenced issues on default branch When merge requests and commits in the default branch close, any issues they reference also close. Branch name template Branches created from issues follow this pattern. Leave empty to use default template. Maximum 255 characters. What variables can I use? Save changes Branch rules Collapse Define rules for who can push, merge, and the required approvals for each branch. Protected branches, merge request approvals, and status checks will appear here once configured. 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, please 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 Push Authentication method Password SSH public key Password Keep divergent refs Do not force push over diverged refs. After the mirror is created, this setting can only be modified using the API. Learn more about this option and the API. Mirror only protected branches If enabled, only protected branches will be mirrored. Learn more. Mirror repository Mirrored repositories Direction Last update attempt Last successful update ssh://*****@localhost/project.git Push Never Never Protected branches Collapse Keep stable branches secure and force developers to use merge requests. What are protected branches? By default, protected branches restrict who can modify the branch. Learn more. 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 Allowed to force push: Allowed to force push Allow all users with push access to force push. Protect 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 restrict who can modify the tag. Learn more. Protect a tag Tag: Select tag or create wildcard Wildcards such as v* or *-release are supported. Allowed to create: Maintainers Protected tags (0) No tags are protected. Deploy tokens Collapse Deploy tokens allow access to packages, your repository, and registry images. New deploy token Create a new deploy token for all projects in this group. What are deploy tokens? Name Enter a unique name for your deploy token. Expiration date (optional) Enter an expiration date for your token. Defaults to never expire. Username (optional) Enter a username for your token. Defaults to gitlab+deploy-token-{n}. Scopes (select at least one) read_repository Allows read-only access to the repository. read_package_registry Allows read-only access to the package registry. write_package_registry Allows read and write access to the package registry. Create deploy token 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 Add key 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. Start cleanup"
Timeout (30s) reached while running a waiting Capybara finder.
Consider using a non-waiting finder.
See https://www.cloudbees.com/blog/faster-rails-tests
# ./spec/features/projects/settings/repository_settings_spec.rb:168:in `block (4 levels) in <main>'
# ./spec/spec_helper.rb:411:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:403:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:399:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:59:in `with_raw_context'
# ./spec/spec_helper.rb:399:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
# ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
# ./spec/support/flaky_tests.rb:27:in `block (2 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (3 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:60:in `with_cross_joins_prevented'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (2 levels) in <main>'
1.2) Failure/Error: raise JSConsoleError, message
JSConsoleError:
Unexpected browser console output:
security - Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
https://localhost/com.snowplowanalytics.snowplow/tp2 - Failed to load resource: net::ERR_CONNECTION_REFUSED
security - Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
https://localhost/com.snowplowanalytics.snowplow/tp2 - Failed to load resource: net::ERR_CONNECTION_REFUSED
# ./spec/support/capybara.rb:206:in `block (2 levels) in <main>'
# ./spec/spec_helper.rb:411:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:403:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:399:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:59:in `with_raw_context'
# ./spec/spec_helper.rb:399:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
# ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
# ./spec/support/flaky_tests.rb:27:in `block (2 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (3 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:60:in `with_cross_joins_prevented'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (2 levels) in <main>'
2) Projects > Settings > Repository settings for maintainer remote mirror settings creates a push mirror that only mirrors protected branches
Got 1 failure and 1 other error:
2.1) 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 / Help P project4 Project information Issues 0 Merge requests 0 CI/CD Security & Compliance Deployments Packages and registries Infrastructure Monitor Analytics Wiki Snippets Settings General Integrations Webhooks Access Tokens Repository Merge requests CI/CD Packages and registries Monitor Usage Quotas Collapse sidebar Sidney Jones8 project4 Repository Settings An error occurred while loading branch rules. Please try again. Branch defaults Collapse Select the default branch for this project, and configure the template for branch names. A default branch cannot be chosen for an empty project. Auto-close referenced issues on default branch When merge requests and commits in the default branch close, any issues they reference also close. Branch name template Branches created from issues follow this pattern. Leave empty to use default template. Maximum 255 characters. What variables can I use? Save changes Branch rules Collapse Define rules for who can push, merge, and the required approvals for each branch. Protected branches, merge request approvals, and status checks will appear here once configured. 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, please 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 Push Authentication method Password SSH public key Password Keep divergent refs Do not force push over diverged refs. After the mirror is created, this setting can only be modified using the API. Learn more about this option and the API. Mirror only protected branches If enabled, only protected branches will be mirrored. Learn more. Mirror repository Mirrored repositories Direction Last update attempt Last successful update ssh://*****@localhost/project.git Push Never Never Protected branches Collapse Keep stable branches secure and force developers to use merge requests. What are protected branches? By default, protected branches restrict who can modify the branch. Learn more. 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 Allowed to force push: Allowed to force push Allow all users with push access to force push. Protect 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 restrict who can modify the tag. Learn more. Protect a tag Tag: Select tag or create wildcard Wildcards such as v* or *-release are supported. Allowed to create: Maintainers Protected tags (0) No tags are protected. Deploy tokens Collapse Deploy tokens allow access to packages, your repository, and registry images. New deploy token Create a new deploy token for all projects in this group. What are deploy tokens? Name Enter a unique name for your deploy token. Expiration date (optional) Enter an expiration date for your token. Defaults to never expire. Username (optional) Enter a username for your token. Defaults to gitlab+deploy-token-{n}. Scopes (select at least one) read_repository Allows read-only access to the repository. read_package_registry Allows read-only access to the package registry. write_package_registry Allows read and write access to the package registry. Create deploy token 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 Add key 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. Start cleanup"
Timeout (30s) reached while running a waiting Capybara finder.
Consider using a non-waiting finder.
See https://www.cloudbees.com/blog/faster-rails-tests
# ./spec/features/projects/settings/repository_settings_spec.rb:189:in `block (4 levels) in <main>'
# ./spec/spec_helper.rb:411:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:403:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:399:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:59:in `with_raw_context'
# ./spec/spec_helper.rb:399:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
# ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
# ./spec/support/flaky_tests.rb:27:in `block (2 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (3 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:60:in `with_cross_joins_prevented'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (2 levels) in <main>'
2.2) Failure/Error: raise JSConsoleError, message
JSConsoleError:
Unexpected browser console output:
security - Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
https://localhost/com.snowplowanalytics.snowplow/tp2 - Failed to load resource: net::ERR_CONNECTION_REFUSED
security - Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
https://localhost/com.snowplowanalytics.snowplow/tp2 - Failed to load resource: net::ERR_CONNECTION_REFUSED
# ./spec/support/capybara.rb:206:in `block (2 levels) in <main>'
# ./spec/spec_helper.rb:411:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:403:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:399:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:59:in `with_raw_context'
# ./spec/spec_helper.rb:399:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
# ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
# ./spec/support/flaky_tests.rb:27:in `block (2 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (3 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:60:in `with_cross_joins_prevented'
# ./spec/support/database/prevent_cross_joins.rb:106:in `block (2 levels) in <main>'
Finished in 2 minutes 43.4 seconds (files took 34.18 seconds to load)
...
Failed examples:
rspec ./spec/features/projects/settings/repository_settings_spec.rb:153 # Projects > Settings > Repository settings for maintainer remote mirror settings creates a push mirror that mirrors all branches
rspec ./spec/features/projects/settings/repository_settings_spec.rb:172 # Projects > Settings > Repository settings for maintainer remote mirror settings creates a push mirror that only mirrors protected branches
[TEST PROF INFO] Time spent in factories: 00:02.889 (1.75% of total time)
Edited by Jennifer Li