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

[greenkeeper]

Version 2.1.4 of testit just got published.

Branch	Build failing 🚨
Dependency	testit
Current Version	2.1.3
Type	devDependency

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

As testit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ✅ dependency-ci Dependencies checked Details
• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 11 commits.

• 60e9f16 Update wtfnode ^0.4.0 → ^0.5.4 (#21)
• 61d71ca fix(package): update ms to version 1.0.0 (#19)
• 990dba6 fix(package): update wtfnode to version 0.5.0 (#18)
• 3ffdc22 Merge pull request #12 from ForbesLindesay/greenkeeper-ms-0.7.2
• 026b361 chore(package): update coveralls to version 2.11.13 (#11)
• 3c043ab chore(package): update wtfnode to version 0.4.0 (#10)
• c32c8e6 Merge pull request #14 from ForbesLindesay/greenkeeper-sauce-test-1.1.0
• aeb2588 Release 2.1.3
• 9238965 Stop testing on unsupported versions of node.js
• b4ca44c chore(package): update sauce-test to version 1.1.0
• c6f4a72 chore(package): update ms to version 0.7.2

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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