Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of mocha-junit-reporter is breaking the build 🚨 #12

Open
greenkeeper bot opened this issue Jan 11, 2020 · 2 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jan 11, 2020

The devDependency mocha-junit-reporter was updated from 1.23.1 to 1.23.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha-junit-reporter is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: dependencies: Your tests passed on CircleCI! (Details).
  • ci/circleci: dev_dependencies: Your tests passed on CircleCI! (Details).
  • ci/circleci: build: CircleCI is running your tests (Details).
  • ci/circleci: audit_dependencies: Your tests failed on CircleCI (Details).
  • ci/circleci: code_review: CircleCI is running your tests (Details).

Commits

The new version differs by 9 commits.

  • 9787677 1.23.2
  • c612b17 Bump js-yaml from 3.13.0 to 3.13.1
  • b30afd0 add default values in option table
  • bcfc7a4 Ensure that test time attribute is capped at 4 digits after the decimal
  • 19eee3e Update options parsing for mocha 6+
  • 3b310cc Bump lodash from 4.17.11 to 4.17.15
  • 1993678 Un-IDE the path
  • ed7a698 Do workflows work?
  • 9168d01 Fixed unhandled promise rejection

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 11, 2020

After pinning to 1.23.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 16, 2020

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants