danger-review
Passed Started
by
@alexkalderimis
Alex Kalderimis
1Running with gitlab-runner 14.2.0 (58ba2b95)2 on blue-1.private.runners-manager.gitlab.com/gitlab.com/gitlab-org 1zzGUpzq3 feature flags: FF_USE_FASTZIP:true, FF_SCRIPT_SECTIONS:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.14-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.14-git-2.31-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...9Using docker image sha256:2d2d820babccdf44a703e353eee2c88ce089eb1de130ddf7d2c729ef8ee98c4d for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.14-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:9be586657c93d4bb1a61071e6c0649da6a64fba31283ffe36b8e4ec5d042595a ...11Running on runner-1zzgupzq-project-278964-concurrent-0 via runner-1zzgupzq-private-1631644992-df49476e...14Downloading archived master...15Connecting to storage.googleapis.com (172.217.193.128:443)16saving to '/tmp/gitlab.tar.gz'17gitlab.tar.gz 59% |****************** | 201M 0:00:00 ETA18gitlab.tar.gz 100% |********************************| 340M 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: 265, done. 25remote: Counting objects: 100% (191/191), done. 26remote: Compressing objects: 100% (77/77), done. 27remote: Total 93 (delta 68), reused 23 (delta 14), pack-reused 0 29 * [new ref] 7818fd5200fa647737976e6f87724e1b0d1a58fe -> refs/pipelines/37074602830Checking out 7818fd52 as refs/merge-requests/69982/merge...31Skipping Git submodules setup33Checking cache for ruby-gems-v1-4...34cache.zip is up to date 35Successfully extracted cache36Checking cache for node-modules-test-v1-4...37cache.zip is up to date 38Successfully extracted cache40Using docker image sha256:2d2d820babccdf44a703e353eee2c88ce089eb1de130ddf7d2c729ef8ee98c4d for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.patched-golang-1.14-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:9be586657c93d4bb1a61071e6c0649da6a64fba31283ffe36b8e4ec5d042595a ...43Bundler version 2.1.444production:development45Settings are listed in order of priority. The top value will be used.46path47Set for the current user (/root/.bundle/config): "/builds/gitlab-org/gitlab/vendor"48clean49Set for the current user (/root/.bundle/config): "true"50without51Set via BUNDLE_WITHOUT: [:production, :development]52install_flags53Set via BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"54$ bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check55[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 flag56The Gemfile's dependencies are satisfied57==> 'bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check' succeeded in 2 seconds.58$ bundle pristine pg59Installing pg 1.2.3 with native extensions60==> 'bundle pristine pg' succeeded in 12 seconds.62$ retry yarn install --frozen-lockfile63yarn install v1.22.1064[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.03s.70==> 'retry yarn install --frozen-lockfile' succeeded in 3 seconds.72$ 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:76Markdown:77## Reviewer roulette78Changes that require review have been detected!79Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:80| Category | Reviewer | Maintainer |81| -------- | -------- | ---------- |82| ~backend | [Pedro Pombeiro](https://gitlab.com/pedropombeiro) (`@pedropombeiro`) (UTC+2, 1 hour behind `@furkanayhan`) | [Mark Chao](https://gitlab.com/lulalala) (`@lulalala`) (UTC+8, 5 hours ahead of `@furkanayhan`) |83To spread load more evenly across eligible reviewers, Danger has picked a candidate for each84review slot, based on their timezone. Feel free to85[override these selections](https://about.gitlab.com/handbook/engineering/projects/#gitlab)86if you think someone else would be better-suited87or use the [GitLab Review Workload Dashboard](https://gitlab-org.gitlab.io/gitlab-roulette/) to find other available reviewers.88To read more on how to use the reviewer roulette, please take a look at the89[Engineering workflow](https://about.gitlab.com/handbook/engineering/workflow/#basics)90and [code review guidelines](https://docs.gitlab.com/ee/development/code_review.html).91Please consider assigning a reviewer or maintainer who is a92[domain expert](https://about.gitlab.com/handbook/engineering/projects/#gitlab) in the area of the merge request.93Once you've decided who will review this merge request, assign them as a reviewer!94Danger does not automatically notify them for you.95**If needed, you can retry the [`danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/1590281166) that generated this comment.**96==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 6 seconds.98Not uploading cache ruby-gems-v1-4 due to policy99Not uploading cache node-modules-test-v1-4 due to policy101Job succeeded