[QA] Transient failure in qa/specs/features/project/pipelines_spec.rb:9
As seen in https://gitlab.com/gitlab-org/gitlab-qa/-/jobs/82221168:
1) CI/CD Pipelines user registers a new specific runner
Failure/Error: expect(page).to have_content(executor)
expected to find text "qa-runner-1531814439" in "Runners Collapse Register and see your runners for this project. A 'Runner' is a process which runs a job. You can setup as many Runners as you need. Runners can be placed on separate users, servers, and even on your local machine. Each Runner can be in one of the following states: active - Runner is active and can process any new jobs paused - Runner is paused and will not receive any new jobs To start serving your jobs you can either add specific Runners to your project or use shared Runners Specific Runners Setup a specific Runner automatically You can easily install a Runner on a Kubernetes cluster. Learn more about Kubernetes Click the button below to begin the install process by navigating to the Kubernetes page Select an existing Kubernetes cluster or create a new one From the Kubernetes cluster details view, install Runner from the applications list Install Runner on Kubernetes Setup a specific Runner manually Install a Runner compatible with GitLab CI (checkout the GitLab Runner section for information on how to install it). Specify the following URL during the Runner setup: https://staging.gitlab.com/ Use the following registration token during setup: GHm4sTcb934Y1DXUxesR Start the Runner! Available specific runners 1b477e5c #197745 cluster kubernetes 9855e6fa #197703 cluster kubernetes 1f3aea1c #197696 cluster kubernetes b4bdf480 #197677 cluster kubernetes fa7e4c99 #197676 cluster kubernetes e7d7b950 #197675 cluster kubernetes 7b022d59 #197673 cluster kubernetes 45489f47 #197672 cluster kubernetes 00056eb0 #197671 cluster kubernetes 30fccdb8 #197670 cluster kubernetes 4b8285df #197669 cluster kubernetes Shared Runners Shared Runners on GitLab.com run in autoscale mode and are powered by DigitalOcean. Autoscaling means reduced wait times to spin up builds, and isolated VMs for each project, thus maximizing security. They're free to use for public open source projects and limited to 2000 CI minutes per month per group for private projects. Read about all GitLab.com plans. Disable shared Runners for this project Available shared Runners : 9 fa6cab46 #44028 shared-runners-manager-3.gitlab.com docker east-c gce git-annex linux mongo mysql postgres ruby shared 72989761 #44949 shared-runners-manager-4.gitlab.com docker east-c gce git-annex linux mongo mysql postgres ruby shared 2d99bded #197697 fabio-migration-runner e11ae361 #40786 shared-runners-manager-1.gitlab.com docker git-annex linux mongo mysql postgres ruby shared 1815394d #186460 hc-shared-runners-manager-1.gitlab.com gitlab-org-high-cpu 12afdd1e #186461 hc-shared-runners-manager-2.gitlab.com gitlab-org-high-cpu ab89f037 #37397 gitlab-shared-runners-manager-1.gitlab.com 2gb gitlab-org 9a6801bd #37398 gitlab-shared-runners-manager-2.gitlab.com 2gb gitlab-org 4e4528ca #40788 shared-runners-manager-2.gitlab.com docker git-annex linux mongo mysql postgres ruby shared Group Runners GitLab Group Runners can execute code for all the projects in this group. They can be managed using the Runners API. Disable group Runners for this project This group does not provide any group Runners yet. Group maintainers can register group runners in the Group CI/CD settings"
Unfortunately, due to https://gitlab.com/gitlab-org/gitlab-ce/issues/49318 we cannot see the screenshot taken.