rspec:feature-flags
Passed Started
by
@rkadam3

Rajendra Kadam
1Running with gitlab-runner 15.9.0~beta.115.g598a7c91 (598a7c91)2 on green-4.shared-gitlab-org.runners-manager.gitlab.com/default x5QiHUKw, system ID: s_b9637080a79e3 feature flags: FF_NETWORK_PER_BUILD:true, FF_USE_FASTZIP:true, FF_USE_IMPROVED_URL_MASKING:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13:rubygems-3.4-git-2.36-lfs-2.9-chrome-109-yarn-1.22-graphicsmagick-1.3.36 ...7Authenticating with credentials from job payload (GitLab Registry)8Pulling docker image registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13:rubygems-3.4-git-2.36-lfs-2.9-chrome-109-yarn-1.22-graphicsmagick-1.3.36 ...9Using docker image sha256:552b81110cdd830e05d17c8e7365f72e1dd96842217d7225636cb55a75777ea7 for registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13:rubygems-3.4-git-2.36-lfs-2.9-chrome-109-yarn-1.22-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13@sha256:a386dd1acb1341f710f3c3c320984f70512694bcfec8cb1c771365058ac7c475 ...11Running on runner-x5qihukw-project-278964-concurrent-0 via runner-x5qihukw-shared-gitlab-org-1681892985-3e71a302...13$ eval "$CI_PRE_CLONE_SCRIPT"14Fetching changes with git depth set to 20...15Initialized empty Git repository in /builds/gitlab-org/gitlab/.git/16Created fresh repository.17remote: Enumerating objects: 127066, done. 18remote: Counting objects: 100% (127066/127066), done. 19remote: Compressing objects: 100% (84263/84263), done. 20remote: Total 127066 (delta 52059), reused 86943 (delta 37888), pack-reused 0 21Receiving objects: 100% (127066/127066), 122.40 MiB | 26.44 MiB/s, done.22Resolving deltas: 100% (52059/52059), done.24 * [new ref] refs/pipelines/841847819 -> refs/pipelines/84184781925 * [new branch] master -> origin/master26Checking out e2ff33c5 as detached HEAD (ref is master)...27Skipping Git submodules setup28$ git remote set-url origin "${CI_REPOSITORY_URL}"30Checking cache for ruby-gems-debian-bullseye-ruby-3.0-16...31cache.zip is up to date 32Successfully extracted cache34Downloading artifacts for feature-flags-usage (4139146331)...35Downloading artifacts from coordinator... ok host=storage.googleapis.com id=4139146331 responseStatus=200 OK token=64_Kgq2a36Downloading artifacts for haml-lint (4139146327)...37Downloading artifacts from coordinator... ok host=storage.googleapis.com id=4139146327 responseStatus=200 OK token=64_Kgq2a38Downloading artifacts for haml-lint ee (4139146328)...39Downloading artifacts from coordinator... ok host=storage.googleapis.com id=4139146328 responseStatus=200 OK token=64_Kgq2a41Using docker image sha256:552b81110cdd830e05d17c8e7365f72e1dd96842217d7225636cb55a75777ea7 for registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13:rubygems-3.4-git-2.36-lfs-2.9-chrome-109-yarn-1.22-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-3.0.patched-golang-1.19-rust-1.65-node-16.14-postgresql-13@sha256:a386dd1acb1341f710f3c3c320984f70512694bcfec8cb1c771365058ac7c475 ...42$ source scripts/utils.sh43$ export BUNDLE_WITHOUT="${BUNDLE_WITHOUT}:default:test:puma:kerberos:metrics:omnibus:ed25519"44$ bundle_install_script679$ if [ "$CI_COMMIT_BRANCH" == "$CI_DEFAULT_BRANCH" ]; then run_timed_command "bundle exec scripts/used-feature-flags" || (scripts/slack master-broken "☠️ \`${CI_JOB_NAME}\` failed! ☠️ See ${CI_JOB_URL}" ci_failing "GitLab Bot" && exit 1); else run_timed_command "bundle exec scripts/used-feature-flags"; fi680$ bundle exec scripts/used-feature-flags681config/feature_flags/**/*.yml682Skipping the gitaly_enforce_requests_limits feature flag since it starts with 'gitaly_'.683Skipping the gitaly_go_user_merge_branch feature flag since it starts with 'gitaly_'.684Skipping the gitaly_mep_mep feature flag since it starts with 'gitaly_'.685Skipping the gitaly_pack_objects_hook_with_sidechannel feature flag since it starts with 'gitaly_'.686Skipping the gitaly_revlist_for_repo_size feature flag since it starts with 'gitaly_'.687Skipping the gitaly_upload_pack_gitaly_hooks feature flag since it starts with 'gitaly_'.688Skipping the gitaly_user_merge_branch_access_error feature flag since it starts with 'gitaly_'.689ee/config/feature_flags/**/*.yml690=========================================691Feature Flags usage summary:692- 513 was found693- 0 appear(s) to be UNUSED694- 1 appear(s) to be unknown695- 512 appear(s) to be used696==================================================697There are feature flags that appear to be unknown698They appear to be used by CI, but we do lack their YAML definition699This is likely expected, so feel free to ignore that list:700- geo_pipeline_replication701Everything is fine here!702==> 'bundle exec scripts/used-feature-flags' succeeded in 0 seconds.704Not uploading cache ruby-gems-debian-bullseye-ruby-3.0-16 due to policy706Job succeeded