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

[greenkeeper]

The devDependency karma was updated from 4.0.0 to 4.0.1.

🚨 View failing branch.

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

karma 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).

---

Release Notes for v4.0.1

Bug Fixes

• browser: allow updating total specs count (#3264) (d5df723)
• remove vulnerable dependency combine-lists (#3273) (c43f584), closes #3265
• remove vulnerable dependency expand-braces (#3270) (4ec4f6f), closes #3268 #3269
• filelist: correct logger name. (#3262) (375bb5e)
• launcher: Debug Child Processes exit signal (#3259) (c277a6b)

Commits

The new version differs by 8 commits.

• c7ebf0b chore: release v4.0.1
• c190c4a chore: update contributors
• 375bb5e fix(filelist): correct logger name. (#3262)
• c43f584 fix: remove vulnerable dependency combine-lists (#3273)
• 4ec4f6f fix: remove vulnerable dependency expand-braces (#3270)
• d5df723 fix(browser): allow updating total specs count (#3264)
• c277a6b fix(launcher): Debug Child Processes exit signal (#3259)
• bd95d89 chore: upgrade log4js to v4.0.0 (#3257)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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