There was an error fetching the job.
danger-review
Passed Started
by
@grzesiek

Grzegorz Bizon
1Running with gitlab-runner 13.11.0-rc1 (286f7013)2 on docker-auto-scale-com 9538b0ab3 feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.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.2.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:47420e1c99db68fee8e483ec590b37d8aa9ee4ddec03cf46a158fceae71d869c for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.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:33e8ef0294f65409840cf02a5a2699b2eca284f117a2ead068783cfb2f541ff2 ...11Running on runner-9538b0ab-project-278964-concurrent-0 via runner-9538b0ab-gsrm-1619174915-43b7568d...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 33% |********** | 138M 0:00:02 ETA18gitlab.tar.gz 100% |********************************| 417M 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: 6993, done. 25remote: Counting objects: 100% (3128/3128), done. 26remote: Compressing objects: 100% (1448/1448), done. 27remote: Total 1778 (delta 1371), reused 590 (delta 302), pack-reused 0 28Receiving objects: 100% (1778/1778), 665.85 KiB | 11.29 MiB/s, done.29Resolving deltas: 100% (1371/1371), completed with 490 local objects.31 * [new ref] 0bca58045fd39d6ead296b5490cf35b76d783fae -> refs/pipelines/29121265332Checking out 0bca5804 as refs/merge-requests/52203/merge...33Skipping Git submodules setup35Checking cache for danger-review-v1-4...36Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/danger-review-v1-4 37WARNING: vendor/ruby/2.7.0/gems/deprecation_toolkit-1.5.1/gemfiles/test/deprecations: chmod vendor/ruby/2.7.0/gems/deprecation_toolkit-1.5.1/gemfiles/test/deprecations: no such file or directory (suppressing repeats) 38Successfully extracted cache40Using docker image sha256:47420e1c99db68fee8e483ec590b37d8aa9ee4ddec03cf46a158fceae71d869c for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.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:33e8ef0294f65409840cf02a5a2699b2eca284f117a2ead068783cfb2f541ff2 ...41$ source ./scripts/utils.sh42$ run_timed_command "bundle install --jobs=$(nproc) --path=vendor --retry=3 --quiet --with danger"43$ bundle install --jobs=2 --path=vendor --retry=3 --quiet --with danger44[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 flag45==> 'bundle install --jobs=2 --path=vendor --retry=3 --quiet --with danger' succeeded in 1 seconds.46$ run_timed_command "retry yarn install --frozen-lockfile"47$ retry yarn install --frozen-lockfile48yarn install v1.22.549[1/5] Validating package.json...50[2/5] Resolving packages...51success Already up-to-date.52$ node ./scripts/frontend/postinstall.js53success Dependency postinstall check passed.54Done in 1.04s.55==> 'retry yarn install --frozen-lockfile' succeeded in 2 seconds.56$ if [ -z "$DANGER_GITLAB_API_TOKEN" ]; then # collapsed multi-line command57$ bundle exec danger --fail-on-errors=true --verbose58danger/feature_flag/Dangerfile:4: warning: already initialized constant Danger::Dangerfile::SEE_DOC59danger/changelog/Dangerfile:6: warning: previous definition of SEE_DOC was here60danger/feature_flag/Dangerfile:7: warning: already initialized constant Danger::Dangerfile::SUGGEST_MR_COMMENT61danger/changelog/Dangerfile:8: warning: previous definition of SUGGEST_MR_COMMENT was here62danger/roulette/Dangerfile:5: warning: already initialized constant Danger::Dangerfile::MESSAGE63danger/pipeline/Dangerfile:3: warning: previous definition of MESSAGE was here64Results:65Warnings:66- [ ] This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time.67- [ ] This merge request does not refer to an existing milestone.68Messages:69- [ ] We are in the process of rolling out a new workflow for adding changelog entries. This new workflow uses Git commit subjects and Git trailers to generate changelogs. This new approach will soon replace the current YAML based approach.70To ease the transition process, we recommend you start using both the old and new approach in parallel. This is not required at this time, but will make it easier to transition to the new approach in the future. To do so, pick the commit that should go in the changelog and add a `Changelog` trailer to it. For example:71```72This is my commit's subject line73This is the optional commit body.74Changelog: added75```76The value of the `Changelog` trailer should be one of the following: added, fixed, changed, deprecated, removed, security, performance, other.77For more information, take a look at the following resources:80If you'd like to see the new approach in action, take a look at the commits in [the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/-/commits/master).81- [ ] 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.82Markdown:83## Documentation review84The following files require a review from a technical writer:85* `doc/architecture/blueprints/ci_scale/ci_builds_cumulative_forecast.png`86* `doc/architecture/blueprints/ci_scale/ci_builds_daily_forecast.png`87* `doc/architecture/blueprints/ci_scale/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**If needed, you can retry the [`danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/1206553652) that generated this comment.**93==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 8 seconds.95Not uploading cache danger-review-v1-4 due to policy97Job succeeded