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

[greenkeeper]

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

The dependency bull was updated from 3.13.0 to 3.14.0.

🚨 View failing branch.

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

bull is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ✅ ci/circleci: checkout_code: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: integration_tests: CircleCI is running your tests (Details).
• ✅ ci/circleci: unit_tests: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: audit: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 19 commits.

• a4aa27c 3.14.0
• 7f9056a docs: update changelog
• 1898b5a feat(queue): add removeJobs function
• 635210f fix(job): guard moveToComplet/Failed with isReady
• 10a9eae fix: clamp negative job delay values to 0 to prevent thrashing
• c06af98 docs: improve documentation for getJobs() (#1468)
• c61cd84 docs: add a hyperlink to #488 in README
• 031b231 fix: use DEFAULT_JOB_NAME (#1585)
• 3a6a519 docs: Update REFERENCE.md (#1595)
• 626f21f fix: remove the lazy client error handler on close (#1605)
• 5ecc30b docs: Update REFERENCE.md (#1633)
• 4a6268b docs: Update CHANGELOG.md (#1652)
• 4b6031d fix: prevent exceeding the maximum stack call size when emptying large queues (#1660)
• dbe2549 Update REFERENCE.md (#1668)
• b06f4b2 docs(REFERENCE.md): add missing curly bracket (#1677)

There are 19 commits in total.

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