An in-range update of wdio-junit-reporter is breaking the build 🚨

[greenkeeper[bot]]

Version 0.3.1 of wdio-junit-reporter just got published.

Branch	Build failing 🚨
Dependency	wdio-junit-reporter
Current Version	0.3.0
Type	devDependency

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

As wdio-junit-reporter 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 :muscle:

Status Details

- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/DBCDK/tanterne/09813710a82f382a81227f8a9aac7340e25b6371/dependencies/npm?status=passing) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/DBCDK/tanterne/09813710a82f382a81227f8a9aac7340e25b6371/files?status=passing) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DBCDK/tanterne/builds/265095860?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 40 commits.

• 26b9ac0 0.3.1
• aa023bc chore(package): update sinon to version 3.0.0
• a3423e1 add a test for the crashfix
• 1ef4059 fix a crash when using cucumber hooks
• 5d88774 Only ignore some lines
• 619c552 Fix linting errors
• 9d0cb36 Test Content Output
• 7ae87b6 Handle xit Skipped Tests
• f57975d chore(package): update eslint to version 4.1.0
• 5194349 fix deps
• e668aea chore(package): update eslint-plugin-mocha to version 4.10.1
• 4d6b50c chore(package): update babel-core to version 6.25.0
• fed7188 chore(package): update np to version 2.16.0
• 644b836 chore(package): update eslint-plugin-import to version 2.4.0
• 71410a3 chore(package): update eslint-plugin-node to version 5.0.0

There are 40 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[fvsdbc]

Fixed