Skip to content

Test failure './spec/features/projects/settings/forked_project_settings_spec.rb[1:2:1:1]'

Job #1180972568 failed for 435239f1:

Failures:
  1) Projects > Settings > For a forked project when the original project is deleted behaves like project settings for a forked projects allows deleting the link to the forked project
     Got 1 failure and 1 other error:
     Shared Example Group: "project settings for a forked projects" called from ./spec/features/projects/settings/forked_project_settings_spec.rb:40
     1.1) Failure/Error: expect(page).to have_content('The fork relationship has been removed.')
            expected to find text "The fork relationship has been removed." in "Skip to content GitLab Projects Help P project122 Project overview Issues 0 CI/CD Security & Compliance Operations Packages & Registries Analytics Wiki Snippets Members Settings General Integrations Webhooks Access Tokens Repository CI/CD Operations Collapse sidebar group29 project122 General Settings An error occurred fetching the approval rules. Naming, topics, avatar Collapse Update your project name, topics, description, and avatar. Project name Project ID Topics (optional) Separate topics with commas. Compliance framework No compliance frameworks are in use. Project description (optional) P Project avatar Choose file… No file chosen. Max file size is 200 KB. Visibility, project features, permissions Collapse Choose visibility level, enable/disable project features and their permissions, disable email notifications, and show default award emoji. Project visibility Private Internal Public The project is accessible only by members of the project. Access must be granted explicitly to each user. Issues Lightweight issue tracking system. Only Project Members Repository View and edit files in this project. Only Project Members Merge requests Submit changes to be merged upstream. Only Project Members Forks Users can copy the repository to a new project. Only Project Members Packages Every project can have its own space to store its packages. CI/CD Build, test, and deploy your changes. Only Project Members Analytics View project analytics. Only Project Members Security & Compliance Security & Compliance for this project Only Project Members Wiki Pages for project documentation. Only Project Members Snippets Share code with others outside the project. Only Project Members Operations Configure your project resources and monitor their health. Only Project Members Metrics Dashboard Visualize the project's performance metrics. Only Project Members Disable email notifications Override user notification preferences for all project members. Show default award emojis Always show thumbs-up and thumbs-down award emoji buttons on issues, merge requests, and snippets. Allow editing commit messages Commit authors can edit commit messages on unprotected branches. Merge requests Collapse Choose your merge method, merge options, merge checks, merge suggestions, and set up a default description template for merge requests. Merge method Determine what happens to the commit history when you merge a merge request. Merge commit Every merge creates a merge commit. Merge commit with semi-linear history Every merge creates a merge commit. Fast-forward merges only. When there is a merge conflict, the user is given the option to rebase. Fast-forward merge No merge commits are created. Fast-forward merges only. When there is a merge conflict, the user is given the option to rebase. Merge options Additional settings that influence how and when merges are done. Automatically resolve merge request diff discussions when they become outdated Show link to create or view a merge request when pushing from the command line Enable \"Delete source branch\" option by default Existing merge requests and protected branches are not affected. Squash commits when merging Set the default behavior of this option in merge requests. Changes to this are also applied to existing merge requests. What is squashing? Do not allow Squashing is never performed and the checkbox is hidden. Allow Checkbox is visible and unselected by default. Encourage Checkbox is visible and selected by default. Require Squashing is always performed. Checkbox is visible and selected, and users cannot change it. Merge checks These checks must pass before merge requests can be merged. Pipelines must succeed To enable this feature, configure pipelines. How to configure pipelines for merge requests? Skipped pipelines are considered successful Introduces the risk of merging changes that do not pass the pipeline. All discussions must be resolved Merge suggestions The commit message used when applying merge request suggestions. Learn more about suggestions. Supported variables: %{branch_name} %{files_count} %{file_paths} %{project_name} %{project_path} %{user_full_name} %{username} %{suggestions_count} Default description template for merge requests Used for every new merge request. What are description templates? Description parsed with GitLab Flavored Markdown Merge request (MR) approvals Collapse Define approval settings. Learn more. Approval rules Approval settings Prevent users from modifying MR approval rules in merge requests. Require new approvals when new commits are added to an MR. Prevent MR approvals by the author. Prevent MR approvals from users who make commits to the MR. Require user password for approvals. Badges Collapse Customize this project's badges. What are badges? Name Link Supported variables: %{project_path}, %{project_id}, %{default_branch}, %{commit_sha} Example: https://example.gitlab.com/%{project_path} Badge image URL Supported variables: %{project_path}, %{project_id}, %{default_branch}, %{commit_sha} Example: https://example.gitlab.com/%{project_path}/badges/%{default_branch}/pipeline.svg Badge image preview No image to preview Add badge Your badges 0 This project has no badges Default description template for issues Collapse Set a default description template to be used for new issues. What are description templates? Description parsed with GitLab Flavored Markdown. Service Desk Collapse Enable and disable Service Desk. Some additional configuration might be required. Learn more. Improve customer support with Service Desk Service Desk allows people to create issues in your GitLab instance without their own user account. It provides a unique email address for end users to create issues in a project. Replies can be sent either through the GitLab interface or by email. End users only see threads through email. Advanced Collapse Housekeeping, export, path, transfer, remove, archive. Housekeeping Runs a number of housekeeping tasks within the current repository, such as compressing file revisions and removing unreachable objects. Learn more. Run housekeeping Export project Export this project with all its related data in order to move it to a new GitLab instance. When the exported file is ready, you can download it from this page or from the download link in the email notification you will receive. You can then import it when creating a new project. Learn more. The following items will be exported: Project and wiki repositories Project uploads Project configuration, excluding integrations Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities LFS objects Issue Boards Design Management files and data The following items will NOT be exported: Job logs and artifacts Container registry images CI variables Webhooks Any encrypted tokens Export project Archive project Archiving the project will make it entirely read only. It is hidden from the dashboard and doesn't show up in searches. The repository cannot be committed to, and no issues, comments, or other entities can be created. Learn more. Archive project Change path A project’s repository name defines its URL (the one you use to access the project via a browser) and its place on the file disk where GitLab is installed. Learn more. Be careful. Renaming a project's repository can have unintended side effects. You will need to update your local repositories to point to the new location. Path http://127.0.0.1:36361/group29/ Transfer project Transfer your project into another namespace. Learn more. Be careful. Changing the project's namespace can have unintended side effects. You can only transfer the project to namespaces you manage. You will need to update your local repositories to point to the new location. Project visibility level will be changed to match namespace rules when transferring to a group. Select a new namespace Select a new namespace Delete project Delayed Project Deletion (Disabled) Projects will be permanently deleted immediately. Customizable by an administrator. This action will permanently delete project122 immediately, including its repositories and all related resources, including issues, merge requests, etc. Are you ABSOLUTELY SURE you wish to delete this project? Delete project"
          # ./spec/features/projects/settings/forked_project_settings_spec.rb:28:in `block (3 levels) in <top (required)>'
          # ./spec/spec_helper.rb:361:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:352:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:348:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:31:in `with_raw_context'
          # ./spec/spec_helper.rb:348:in `block (2 levels) in <top (required)>'
     1.2) Failure/Error: raise JSConsoleError, message
          JSConsoleError:
            Unexpected browser console output:
            webpack-internal:///GTtl 57:25 Uncaught TypeError: Cannot read property 'addEventListener' of null
            http://127.0.0.1:36361/api/v4/projects/126/external_approval_rules - Failed to load resource: the server responded with a status of 401 (Unauthorized)
            webpack-internal:///GTtl 53:32 Uncaught TypeError: Cannot read property 'checked' of null
            webpack-internal:///GTtl 57:25 Uncaught TypeError: Cannot read property 'addEventListener' of null
            webpack-internal:///GTtl 53:32 Uncaught TypeError: Cannot read property 'checked' of null
            http://127.0.0.1:36361/api/v4/projects/126/external_approval_rules - Failed to load resource: the server responded with a status of 401 (Unauthorized)
          # ./spec/support/capybara.rb:194:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:361:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:352:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:348:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:31:in `with_raw_context'
          # ./spec/spec_helper.rb:348:in `block (2 levels) in <top (required)>'
Finished in 15 minutes 7 seconds (files took 43.82 seconds to load)
169 examples, 1 failure, 5 pending
Failed examples:
rspec './spec/features/projects/settings/forked_project_settings_spec.rb[1:2:1:1]' # Projects > Settings > For a forked project when the original project is deleted behaves like project settings for a forked projects allows deleting the link to the forked project