An in-range update of mocha is breaking the build 🚨

[greenkeeper[bot]]

The devDependency mocha was updated from 6.0.1 to 6.0.2.

🚨 View failing branch.

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

mocha 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: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/roderickhsiao/idle-tracker/55?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Release Notes for v6.0.2

6.0.2 / 2019-02-25

🐛 Fixes

Two more regressions fixed:

• #3768: Test file paths no longer dropped from mocha.opts (@boneskull)
• #3767: --require does not break on module names that look like certain node flags (@boneskull)

Commits

The new version differs by 6 commits.

• 00a895f Release v6.0.2
• 1edce76 update CHANGELOG for v6.0.2 [ci skip]
• 347e9db fix broken positional arguments in config; ensure positional args are unique; closes #3763
• 9e31e9d fix handling of bareword args matching node flags; closes #3761
• 6535965 Update "karma-browserify" to eliminate Karma middleware warning (#3762)
• 37febb6 improve issue template. (#3411)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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