rspec:feature-flags
Passed Started
by
@DylanGriffith
Dylan Griffith
1Running with gitlab-runner 15.6.0~beta.186.ga889181a (a889181a)2 on blue-3.private.runners-manager.gitlab.com/gitlab.com/gitlab-org 6io2xoDD3 feature flags: 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-2.7.patched-golang-1.18-node-16.14-postgresql-12:rubygems-3.2-git-2.36-lfs-2.9-chrome-103-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-2.7.patched-golang-1.18-node-16.14-postgresql-12:rubygems-3.2-git-2.36-lfs-2.9-chrome-103-yarn-1.22-graphicsmagick-1.3.36 ...9Using docker image sha256:5c5404ecc69273636c3ef49645be715ef30ea99e51ad146a2efbeac2a1875f9c for registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-2.7.patched-golang-1.18-node-16.14-postgresql-12:rubygems-3.2-git-2.36-lfs-2.9-chrome-103-yarn-1.22-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-2.7.patched-golang-1.18-node-16.14-postgresql-12@sha256:b032fe79dc0bf3ebfaeb610c82eacc500fbd0ec6e01889444011cf5a72b4135d ...11Running on runner-6io2xodd-project-278964-concurrent-0 via runner-6io2xodd-private-1667783180-6abd32a6...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: 119894, done. 18remote: Counting objects: 100% (119894/119894), done. 19remote: Compressing objects: 100% (78952/78952), done. 20remote: Total 119894 (delta 50153), reused 83076 (delta 36611), pack-reused 0 21Receiving objects: 100% (119894/119894), 110.17 MiB | 30.71 MiB/s, done.22Resolving deltas: 100% (50153/50153), done.24 * [new ref] refs/pipelines/687019226 -> refs/pipelines/68701922625 * [new branch] master -> origin/master26Checking out a134b2ce as master...27Skipping Git submodules setup28$ git remote set-url origin "${CI_REPOSITORY_URL}"30Checking cache for ruby-gems-debian-bullseye-ruby-2.7-16...31Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/ruby-gems-debian-bullseye-ruby-2.7-16 32Successfully extracted cache34Downloading artifacts for feature-flags-usage (3281613285)...35Downloading artifacts from coordinator... ok id=3281613285 responseStatus=200 OK token=xtHS6MrC36Downloading artifacts for haml-lint (3281613269)...37Downloading artifacts from coordinator... ok id=3281613269 responseStatus=200 OK token=xtHS6MrC38Downloading artifacts for haml-lint ee (3281613272)...39Downloading artifacts from coordinator... ok id=3281613272 responseStatus=200 OK token=xtHS6MrC41Using docker image sha256:5c5404ecc69273636c3ef49645be715ef30ea99e51ad146a2efbeac2a1875f9c for registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-2.7.patched-golang-1.18-node-16.14-postgresql-12:rubygems-3.2-git-2.36-lfs-2.9-chrome-103-yarn-1.22-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-2.7.patched-golang-1.18-node-16.14-postgresql-12@sha256:b032fe79dc0bf3ebfaeb610c82eacc500fbd0ec6e01889444011cf5a72b4135d ...42$ source scripts/utils.sh43$ export BUNDLE_WITHOUT="${BUNDLE_WITHOUT}:default:test:puma:kerberos:metrics:omnibus:ed25519"44$ bundle_install_script643$ 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"; fi644$ bundle exec scripts/used-feature-flags645config/feature_flags/**/*.yml646Skipping the gitaly_go_user_merge_branch feature flag since it starts with 'gitaly_'.647Skipping the gitaly_pack_objects_hook_with_sidechannel feature flag since it starts with 'gitaly_'.648Skipping the gitaly_mep_mep feature flag since it starts with 'gitaly_'.649Skipping the gitaly_revlist_for_repo_size feature flag since it starts with 'gitaly_'.650Skipping the gitaly_upload_pack_gitaly_hooks feature flag since it starts with 'gitaly_'.651Skipping the gitaly_enforce_requests_limits feature flag since it starts with 'gitaly_'.652Skipping the gitaly_user_merge_branch_access_error feature flag since it starts with 'gitaly_'.653ee/config/feature_flags/**/*.yml654=========================================655Feature Flags usage summary:656- 511 was found657- 0 appear(s) to be UNUSED658- 2 appear(s) to be unknown659- 509 appear(s) to be used660==================================================661There are feature flags that appears to be unknown662They appear to be used by CI, but we do lack their YAML definition663This is likely expected, so feel free to ignore that list:664- geo_pipeline_replication665- gitaly_enforce_requests_limits666Everything is fine here!667==> 'bundle exec scripts/used-feature-flags' succeeded in 1 seconds.669Not uploading cache ruby-gems-debian-bullseye-ruby-2.7-16 due to policy671Job succeeded