danger-review
Passed Started
by
@pshutsin

Pavel Shutsin
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-16.14-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-16.14-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...9Using docker image sha256:05ef9d4530defd286a1afb1c11aa54387d674a2b01197ea21cb1e90be04384bf 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-16.14-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:6a51c0d95cda96bf7eb8b8fcc2390ee8267ad187f6728fbc74a650836638ac1e ...11Running on runner-x5qihukw-project-278964-concurrent-0 via runner-x5qihukw-shared-gitlab-org-1647352684-cc70ed58...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: 136708, done. 18remote: Counting objects: 100% (136708/136708), done. 19remote: Compressing objects: 100% (91832/91832), done. 20remote: Total 136708 (delta 63539), reused 92463 (delta 39537), pack-reused 0 21Receiving objects: 100% (136708/136708), 123.93 MiB | 28.25 MiB/s, done.22Resolving deltas: 100% (63539/63539), done.24 * [new ref] refs/pipelines/492890772 -> refs/pipelines/49289077225Checking out c0d44bf7 as refs/merge-requests/82739/merge...26Skipping Git submodules setup28Checking cache for ruby-gems-bullseye-9...29cache.zip is up to date 30Successfully extracted cache31Checking cache for node-modules-bullseye-test-9...32cache.zip is up to date 33Successfully extracted cache35Using docker image sha256:05ef9d4530defd286a1afb1c11aa54387d674a2b01197ea21cb1e90be04384bf 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-16.14-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:6a51c0d95cda96bf7eb8b8fcc2390ee8267ad187f6728fbc74a650836638ac1e ...36$ source scripts/utils.sh37$ bundle_install_script "--with danger"38Successfully installed bundler-2.3.6391 gem installed40Bundler version 2.3.641production:development42Settings are listed in order of priority. The top value will be used.43clean44Set for the current user (/root/.bundle/config): true45install_flags46Set via BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"47path48Set for the current user (/root/.bundle/config): "/builds/gitlab-org/gitlab/vendor"49without50Set via BUNDLE_WITHOUT: [:production, :development]51$ bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check52[DEPRECATED] The `--with` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local with 'danger'`, and stop using this flag53Don't run Bundler as root. Bundler can ask for sudo if it is needed, and54installing your bundle as root will break this application for all non-root55users on this machine.56The Gemfile's dependencies are satisfied57==> 'bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check' succeeded in 35 seconds.58$ bundle pristine pg59Installing pg 1.2.3 with native extensions60==> 'bundle pristine pg' succeeded in 14 seconds.61$ run_timed_command "retry yarn install --frozen-lockfile"62$ retry yarn install --frozen-lockfile63yarn install v1.22.1764[1/5] Validating package.json...65[2/5] Resolving packages...66success Already up-to-date.67$ node ./scripts/frontend/postinstall.js68success Dependency postinstall check passed.69Done in 1.13s.70==> 'retry yarn install --frozen-lockfile' succeeded in 2 seconds.71$ if [ -z "$DANGER_GITLAB_API_TOKEN" ]; then # collapsed multi-line command72$ bundle exec danger --fail-on-errors=true --verbose73danger/ci_templates/Dangerfile:3: warning: already initialized constant Danger::Dangerfile::TEMPLATE_MESSAGE74danger/gitaly/Dangerfile:3: warning: previous definition of TEMPLATE_MESSAGE was here75Results:76Messages:77- [ ] **[CHANGELOG missing](https://docs.gitlab.com/ee/development/changelog.html)**:78If you want to create a changelog entry for GitLab FOSS, add the `Changelog` trailer to the commit message you want to add to the changelog.79If you want to create a changelog entry for GitLab EE, also [add the `EE: true` trailer](https://docs.gitlab.com/ee/development/changelog.html#gitlab-enterprise-changes) to your commit message.80If this merge request [doesn't need a CHANGELOG entry](https://docs.gitlab.com/ee/development/changelog.html#what-warrants-a-changelog-entry), feel free to ignore this message.81Markdown:82**If needed, you can retry the [🔁 `danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/2206707801) that generated this comment.**83## Reviewer roulette84Changes that require review have been detected!85Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:86| Category | Reviewer | Maintainer |87| -------- | -------- | ---------- |88| ~backend | [Diogo Frazão](https://gitlab.com/dfrazao-gitlab) (`@dfrazao-gitlab`) (UTC+0, 5 hours ahead of `@digitalmoksha`) | [Pavel Shutsin](https://gitlab.com/pshutsin) (`@pshutsin`) (UTC+1, 6 hours ahead of `@digitalmoksha`) |89To spread load more evenly across eligible reviewers, Danger has picked a candidate for each90review slot, based on their timezone. Feel free to91[override these selections](https://about.gitlab.com/handbook/engineering/projects/#gitlab)92if you think someone else would be better-suited93or use the [GitLab Review Workload Dashboard](https://gitlab-org.gitlab.io/gitlab-roulette/) to find other available reviewers.94To read more on how to use the reviewer roulette, please take a look at the95[Engineering workflow](https://about.gitlab.com/handbook/engineering/workflow/#basics)96and [code review guidelines](https://docs.gitlab.com/ee/development/code_review.html).97Please consider assigning a reviewer or maintainer who is a98[domain expert](https://about.gitlab.com/handbook/engineering/projects/#gitlab) in the area of the merge request.99Once you've decided who will review this merge request, assign them as a reviewer!100Danger does not automatically notify them for you.101==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 8 seconds.103Not uploading cache ruby-gems-bullseye-9 due to policy104Not uploading cache node-modules-bullseye-test-9 due to policy106Job succeeded