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

[greenkeeper[bot]]

Version 2.5.3 of jasmine just got published.

Branch	Build failing 🚨
Dependency	jasmine
Current Version	2.5.2
Type	devDependency

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

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

- ❌ **continuous-integration/codeship** Build in progress [Details](https://app.codeship.com/projects/144819/builds/21636598) - ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/rohan-buchner/MHWDashboard_Alpha/runs/build/5876ce59349cc8010012e962)

Release Notes

2.5.3

Please see the release notes

Commits

The new version differs by 16 commits .

• 0da2582 Bump version to 2.5.3
• f5d1d09 Merge branch 'fix_defaultreporter' of https://github.com/cnishina/jasmine-npm into cnishina-fix_defaultreporter
• 1d51773 Fix setOptions to the ConsoleReporter if it exists on the options param
• e0d502f Merge branch 'fix_configurereporter' of https://github.com/tomv564/jasmine-npm into tomv564-fix_configurereporter
• 3447885 Merge branch 'julka-add_license_file'
• 278c89c adding license file
• 0a9cace don't call configureDefaultReporter in execute if it was already called
• 6f58487 Update specs from PR to match new ConsoleReporter interface
• 1b60f4a Merge pull request #84 from ybian/null_stack
• df43829 Merge pull request #76 from aaalsaleh/master
• d1b5d51 Merge branch 'm7r_helper' of https://github.com/m7r/jasmine-npm into m7r-m7r_helper
• 6de5013 Add a test case for undefined stack
• 9b5df8b Fix #83 - default console reporter hangs sometimes
• dfd9e8f Enable regex filter by omitting automatic escaping
• eed0eed Allow to add files with absolute path

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