danger-review
Passed Started
by
@shinya.maeda

Shinya Maeda
1Running with gitlab-runner 14.3.0-rc1 (ed15bfbf)2 on green-2.private.runners-manager.gitlab.com/gitlab.com/gitlab-org GaSD-S1F3 feature flags: FF_USE_FASTZIP:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.16-git-2.31-lfs-2.9-chrome-89-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:ruby-2.7.patched-golang-1.16-git-2.31-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...9Using docker image sha256:5ba30b2efcbe583314cc76f63951dc9434780296f6f0c0927d24b4ce4fb73622 for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.16-git-2.31-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:c4091382b5a12b75ca112f017f8cecffed2cf1a087968e3a03143d55ec67d3bf ...11Running on runner-gasd-s1f-project-278964-concurrent-0 via runner-gasd-s1f-private-1633001800-612fa7ed...13$ eval "$CI_PRE_CLONE_SCRIPT"14Downloading archived master...15Connecting to storage.googleapis.com (172.217.193.128:443)16saving to '/tmp/gitlab.tar.gz'17gitlab.tar.gz 56% |****************** | 193M 0:00:00 ETA18gitlab.tar.gz 100% |********************************| 344M 0:00:00 ETA19'/tmp/gitlab.tar.gz' saved20Extracting tarball into /builds/gitlab-org/gitlab...21Fetching changes with git depth set to 20...22Reinitialized existing Git repository in /builds/gitlab-org/gitlab/.git/23Created fresh repository.24remote: Enumerating objects: 2066, done. 25remote: Counting objects: 100% (834/834), done. 26remote: Compressing objects: 100% (390/390), done. 27remote: Total 486 (delta 348), reused 198 (delta 90), pack-reused 0 28Receiving objects: 100% (486/486), 105.32 KiB | 4.58 MiB/s, done.29Resolving deltas: 100% (348/348), completed with 192 local objects.31 * [new ref] 25ac40e5012c94be8bac8b0ada9e7297b41fcf22 -> refs/pipelines/38016509832Checking out 25ac40e5 as refs/merge-requests/70889/merge...33Skipping Git submodules setup35Checking cache for ruby-gems-v1-4...36Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/ruby-gems-v1-4 37Successfully extracted cache38Checking cache for node-modules-test-v1-4...39Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/node-modules-test-v1-4 40Successfully extracted cache42Using docker image sha256:5ba30b2efcbe583314cc76f63951dc9434780296f6f0c0927d24b4ce4fb73622 for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.16-git-2.31-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:c4091382b5a12b75ca112f017f8cecffed2cf1a087968e3a03143d55ec67d3bf ...43$ source scripts/utils.sh44$ bundle_install_script "--with danger"45Bundler version 2.1.446production:development47Settings are listed in order of priority. The top value will be used.48path49Set for the current user (/root/.bundle/config): "/builds/gitlab-org/gitlab/vendor"50clean51Set for the current user (/root/.bundle/config): "true"52without53Set via BUNDLE_WITHOUT: [:production, :development]54install_flags55Set via BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"56$ bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check57[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 with 'danger'`, and stop using this flag58The Gemfile's dependencies are satisfied59==> 'bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check' succeeded in 2 seconds.60$ bundle pristine pg61Installing pg 1.2.3 with native extensions62==> 'bundle pristine pg' succeeded in 11 seconds.63$ run_timed_command "retry yarn install --frozen-lockfile"64$ retry yarn install --frozen-lockfile65yarn install v1.22.1066[1/5] Validating package.json...67[2/5] Resolving packages...68success Already up-to-date.69$ node ./scripts/frontend/postinstall.js70success Dependency postinstall check passed.71Done in 1.04s.72==> 'retry yarn install --frozen-lockfile' succeeded in 3 seconds.73$ if [ -z "$DANGER_GITLAB_API_TOKEN" ]; then # collapsed multi-line command74$ bundle exec danger --fail-on-errors=true --verbose75danger/ci_templates/Dangerfile:3: warning: already initialized constant Danger::Dangerfile::TEMPLATE_MESSAGE76danger/gitaly/Dangerfile:3: warning: previous definition of TEMPLATE_MESSAGE was here77Results:78Messages:79- [ ] **[CHANGELOG missing](https://docs.gitlab.com/ee/development/changelog.html)**:80If 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.81If 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.82If 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.83- [ ] This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is **recommended**. Reviews can happen after you merge.84Markdown:85## Documentation review86The following files require a review from a technical writer:87* `doc/ci/yaml/index.md`88The review does not need to block merging this merge request. See the:89- [Metadata for the `*.md` files](https://docs.gitlab.com/ee/development/documentation/#metadata) that you've changed. The first few lines of each `*.md` file identify the stage and group most closely associated with your docs change.90- The [Technical Writer assigned](https://about.gitlab.com/handbook/engineering/technical-writing/#designated-technical-writers) for that stage and group.91- [Documentation workflows](https://docs.gitlab.com/ee/development/documentation/workflow.html) for information on when to assign a merge request for review.92## Reviewer roulette93Changes that require review have been detected!94Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:95| Category | Reviewer | Maintainer |96| -------- | -------- | ---------- |97| ~backend | [Alexandru Croitor](https://gitlab.com/acroitor) (`@acroitor`) (UTC+3, 4 hours behind `@shinya.maeda`) | [Alex Kalderimis](https://gitlab.com/alexkalderimis) (`@alexkalderimis`) (UTC+1, 6 hours behind `@shinya.maeda`) |98| ~frontend | [Sheldon Led](https://gitlab.com/sheldonled) (`@sheldonled`) (UTC+1, 6 hours behind `@shinya.maeda`) | [Simon Knox](https://gitlab.com/psimyn) (`@psimyn`) (UTC+10, 3 hours ahead of `@shinya.maeda`) |99To spread load more evenly across eligible reviewers, Danger has picked a candidate for each100review slot, based on their timezone. Feel free to101[override these selections](https://about.gitlab.com/handbook/engineering/projects/#gitlab)102if you think someone else would be better-suited103or use the [GitLab Review Workload Dashboard](https://gitlab-org.gitlab.io/gitlab-roulette/) to find other available reviewers.104To read more on how to use the reviewer roulette, please take a look at the105[Engineering workflow](https://about.gitlab.com/handbook/engineering/workflow/#basics)106and [code review guidelines](https://docs.gitlab.com/ee/development/code_review.html).107Please consider assigning a reviewer or maintainer who is a108[domain expert](https://about.gitlab.com/handbook/engineering/projects/#gitlab) in the area of the merge request.109Once you've decided who will review this merge request, assign them as a reviewer!110Danger does not automatically notify them for you.111**If needed, you can retry the [`danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/1637694922) that generated this comment.**112==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 5 seconds.114Not uploading cache ruby-gems-v1-4 due to policy115Not uploading cache node-modules-test-v1-4 due to policy117Job succeeded