search

FullScreenShenanigans / TimeHandlr

A flexible, pausable alternative to setTimeout and setInterval for GameStartr Things.
MIT License
1 stars 0 forks source link

An in-range update of lolex is breaking the build 🚨 #60

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency lolex was updated from 2.7.4 to 2.7.5.

🚨 View failing branch.

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

lolex 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 could not complete due to an error ([Details](https://travis-ci.org/FullScreenShenanigans/TimeHandlr/builds/430455050?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 9 commits.

  • 927609c 2.7.5
  • 76c212d Updated release files for 2.7.5
  • c4ee56d fix: handle floating point in hrtime (#210)
  • cbaa8ba Merge pull request #208 from SimenB/run-to-last-loop
  • f1f80da fix: reset high resolution timer on clock.reset (#209)
  • a6c0308 clarify test
  • ee3862e simplify test
  • 4983ee8 fix: runToLast should respect current time
  • 1278eaa Add an error when creating a clock with no Date object (#205)

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] commented 5 years ago

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