An in-range update of jasmine-reporters is breaking the build 🚨

[greenkeeper[bot]]

Version 2.3.1 of jasmine-reporters was just published.

Branch	Build failing 🚨
Dependency	jasmine-reporters
Current Version	2.3.0
Type	devDependency

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

jasmine-reporters 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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/lawrencec/Unroll/builds/369321424?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 3 commits.

• f3e94f5 * JUnit: report total time in seconds, not milliseconds
• 67f762e Merge pull request #188 from alistairjcbrown/total-time-seconds
• e4131a5 Calculate total time in seconds

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 2.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

Version 2.3.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 4487b61 2.3.2
• f9e2b26 (JUnitXMLReporter) add options.suppressDisabled to exclude disabled=".." from XML output (#190)

See the full diff