danger-review
Passed Started
by
@jivanvl
Jose Ivan Vargas
1Running with gitlab-runner 14.3.0-rc1 (ed15bfbf)2 on green-1.private.runners-manager.gitlab.com/gitlab.com/gitlab-org 4bq1s9yM3 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-4bq1s9ym-project-278964-concurrent-0 via runner-4bq1s9ym-private-1633705519-123dc07c...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 20% |****** | 71.0M 0:00:03 ETA18gitlab.tar.gz 96% |****************************** | 334M 0:00:00 ETA19gitlab.tar.gz 100% |********************************| 346M 0:00:00 ETA20'/tmp/gitlab.tar.gz' saved21Extracting tarball into /builds/gitlab-org/gitlab...22Fetching changes with git depth set to 20...23Reinitialized existing Git repository in /builds/gitlab-org/gitlab/.git/24Created fresh repository.25remote: Enumerating objects: 361, done. 26remote: Counting objects: 100% (286/286), done. 27remote: Compressing objects: 100% (119/119), done. 28remote: Total 136 (delta 76), reused 56 (delta 12), pack-reused 0 29Receiving objects: 100% (136/136), 36.70 KiB | 7.34 MiB/s, done.30Resolving deltas: 100% (76/76), completed with 62 local objects.32 * [new ref] 84e6d6823fa5f0041cd8e6c83ebcbe049dd8e933 -> refs/pipelines/38518412733Checking out 84e6d682 as refs/merge-requests/71359/merge...34Skipping Git submodules setup36Checking cache for ruby-gems-v1-4...37Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/ruby-gems-v1-4 38Successfully extracted cache39Checking cache for node-modules-test-v1-4...40Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/node-modules-test-v1-4 41Successfully extracted cache43Using 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 ...44$ source scripts/utils.sh45$ bundle_install_script "--with danger"46Bundler version 2.1.447production:development48Settings are listed in order of priority. The top value will be used.49path50Set for the current user (/root/.bundle/config): "/builds/gitlab-org/gitlab/vendor"51clean52Set for the current user (/root/.bundle/config): "true"53without54Set via BUNDLE_WITHOUT: [:production, :development]55install_flags56Set via BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"57$ bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check58[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 flag59The Gemfile's dependencies are satisfied60==> 'bundle install --jobs=$(nproc) --retry=3 --quiet --with danger && bundle check' succeeded in 3 seconds.61$ bundle pristine pg62Installing pg 1.2.3 with native extensions63==> 'bundle pristine pg' succeeded in 10 seconds.64$ run_timed_command "retry yarn install --frozen-lockfile"65$ retry yarn install --frozen-lockfile66yarn install v1.22.1067[1/5] Validating package.json...68[2/5] Resolving packages...69success Already up-to-date.70$ node ./scripts/frontend/postinstall.js71success Dependency postinstall check passed.72Done in 1.06s.73$ if [ -z "$DANGER_GITLAB_API_TOKEN" ]; then # collapsed multi-line command74==> 'retry yarn install --frozen-lockfile' succeeded in 1 seconds.75$ bundle exec danger --fail-on-errors=true --verbose76danger/ci_templates/Dangerfile:3: warning: already initialized constant Danger::Dangerfile::TEMPLATE_MESSAGE77danger/gitaly/Dangerfile:3: warning: previous definition of TEMPLATE_MESSAGE was here78Results:79Messages:80- [ ] **[CHANGELOG missing](https://docs.gitlab.com/ee/development/changelog.html)**:81If 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.82If 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.83If 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.84Markdown:85## Reviewer roulette86Changes that require review have been detected!87Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:88| Category | Reviewer | Maintainer |89| -------- | -------- | ---------- |90| ~frontend | [Scott Stern](https://gitlab.com/sstern) (`@sstern`) (UTC-7, 18 hours behind `@tigerwnz`) | [Jose Ivan Vargas](https://gitlab.com/jivanvl) (`@jivanvl`) (UTC-5, 16 hours behind `@tigerwnz`) |91To spread load more evenly across eligible reviewers, Danger has picked a candidate for each92review slot, based on their timezone. Feel free to93[override these selections](https://about.gitlab.com/handbook/engineering/projects/#gitlab)94if you think someone else would be better-suited95or use the [GitLab Review Workload Dashboard](https://gitlab-org.gitlab.io/gitlab-roulette/) to find other available reviewers.96To read more on how to use the reviewer roulette, please take a look at the97[Engineering workflow](https://about.gitlab.com/handbook/engineering/workflow/#basics)98and [code review guidelines](https://docs.gitlab.com/ee/development/code_review.html).99Please consider assigning a reviewer or maintainer who is a100[domain expert](https://about.gitlab.com/handbook/engineering/projects/#gitlab) in the area of the merge request.101Once you've decided who will review this merge request, assign them as a reviewer!102Danger does not automatically notify them for you.103**If needed, you can retry the [`danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/1663159970) that generated this comment.**104==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 9 seconds.106Not uploading cache ruby-gems-v1-4 due to policy107Not uploading cache node-modules-test-v1-4 due to policy109Job succeeded