rspec:feature-flags
Passed Started
by
@afontaine
Andrew Fontaine
1Running with gitlab-runner 14.8.0~beta.44.g57df0d52 (57df0d52)2 on green-4.shared-gitlab-org.runners-manager.gitlab.com/default x5QiHUKw3 feature flags: FF_USE_FASTZIP:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images:debian-bullseye-ruby-2.7.patched-golang-1.16-git-2.33-lfs-2.9-chrome-97-node-14.15-yarn-1.22-postgresql-11-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.16-git-2.33-lfs-2.9-chrome-97-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...9Using docker image sha256:456702e6ff9a9321c3b9d1982b92a7f8e24135ed69200af2145f633cc5935ebe for registry.gitlab.com/gitlab-org/gitlab-build-images:debian-bullseye-ruby-2.7.patched-golang-1.16-git-2.33-lfs-2.9-chrome-97-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:3d4194c9cbc4c7a5bfb9057fafffe6229b3542f0994b6adb8864733d65ff1204 ...11Running on runner-x5qihukw-project-278964-concurrent-0 via runner-x5qihukw-shared-gitlab-org-1644861047-abab1ac2...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: 116715, done. 18remote: Counting objects: 100% (116715/116715), done. 19remote: Compressing objects: 100% (78717/78717), done. 20remote: Total 116715 (delta 51197), reused 79175 (delta 33358), pack-reused 0 21Receiving objects: 100% (116715/116715), 112.94 MiB | 29.38 MiB/s, done.22Resolving deltas: 100% (51197/51197), done.24 * [new ref] 7bb0d54a07985215aac62bb9b65d58d080f3b908 -> refs/pipelines/47085653025 * [new branch] master -> origin/master26Checking out 7bb0d54a as master...27Skipping Git submodules setup29Checking cache for ruby-gems-v2-9...30Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/ruby-gems-v2-9 31Successfully extracted cache33Downloading artifacts for feature-flags-usage (2092390354)...34Downloading artifacts from coordinator... ok id=2092390354 responseStatus=200 OK token=3m6fosQs35Downloading artifacts for haml-lint ee (2092390347)...36Downloading artifacts from coordinator... ok id=2092390347 responseStatus=200 OK token=d4MEDmx837Downloading artifacts for haml-lint foss (2092390344)...38Downloading artifacts from coordinator... ok id=2092390344 responseStatus=200 OK token=_My2tmU940Using docker image sha256:456702e6ff9a9321c3b9d1982b92a7f8e24135ed69200af2145f633cc5935ebe for registry.gitlab.com/gitlab-org/gitlab-build-images:debian-bullseye-ruby-2.7.patched-golang-1.16-git-2.33-lfs-2.9-chrome-97-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:3d4194c9cbc4c7a5bfb9057fafffe6229b3542f0994b6adb8864733d65ff1204 ...41$ source scripts/utils.sh42$ export BUNDLE_WITHOUT="${BUNDLE_WITHOUT}:default:test:puma:kerberos:metrics:omnibus:ed25519"43$ bundle_install_script44Successfully installed bundler-2.3.6451 gem installed46Bundler version 2.3.647production:development:default:test:puma:kerberos:metrics:omnibus:ed2551948Settings are listed in order of priority. The top value will be used.49clean50Set for the current user (/root/.bundle/config): true51install_flags52Set via BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"53path54Set for the current user (/root/.bundle/config): "/builds/gitlab-org/gitlab/vendor"55without56Set via BUNDLE_WITHOUT: [:production, :development, :default, :test, :puma, :kerberos, :metrics, :omnibus, :ed25519]57$ bundle install --jobs=$(nproc) --retry=3 --quiet && bundle check58Don't run Bundler as root. Bundler can ask for sudo if it is needed, and59installing your bundle as root will break this application for all non-root60users on this machine.61The Gemfile's dependencies are satisfied62==> 'bundle install --jobs=$(nproc) --retry=3 --quiet && bundle check' succeeded in 5 seconds.63Could not find gem 'pg', because it's in the group 'default', configured to be64ignored.65$ 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"; fi66$ bundle exec scripts/used-feature-flags67config/feature_flags/**/*.yml68Skipping the gitaly_go_user_merge_branch feature flag since it starts with 'gitaly_'.69Skipping the gitaly_pack_objects_hook_with_sidechannel feature flag since it starts with 'gitaly_'.70Skipping the gitaly_mep_mep feature flag since it starts with 'gitaly_'.71Skipping the gitaly_backup feature flag since it starts with 'gitaly_'.72Skipping the gitaly_upload_pack_gitaly_hooks feature flag since it starts with 'gitaly_'.73Skipping the gitaly_enforce_requests_limits feature flag since it starts with 'gitaly_'.74Skipping the gitaly_user_merge_branch_access_error feature flag since it starts with 'gitaly_'.75ee/config/feature_flags/**/*.yml76=========================================77Feature Flags usage summary:78- 441 was found79- 0 appear(s) to be UNUSED80- 2 appear(s) to be unknown81- 439 appear(s) to be used82==================================================83There are feature flags that appears to be unknown84They appear to be used by CI, but we do lack their YAML definition85This is likely expected, so feel free to ignore that list:86- gitaly_backup87- gitaly_enforce_requests_limits88Everything is fine here!89==> 'bundle exec scripts/used-feature-flags' succeeded in 1 seconds.91Not uploading cache ruby-gems-v2-9 due to policy93Job succeeded