search

Kronos-Integration / test-step

kronos-step testing support with ava
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

An in-range update of esm is breaking the build 🚨 #408

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency esm was updated from 3.2.13 to 3.2.14.

🚨 View failing branch.

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

esm 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/Kronos-Integration/test-step/builds/503909517?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 17 commits.

  • e8e17d1 Bump to v3.2.14.
  • 3d7fab3 Readme tweaks.
  • 37aee5d Return values of tryPassthru().
  • 5ab620c Use sideloaded compile wrapper if it exists. [closes #739]
  • 3cf1b9c Update tagline in readme.
  • ce55266 Cleanup V8 bug comments.
  • 23a163a Avoid V8 tail call optimization bug with --harmony flag in Node 6.
  • f1a4361 Avoid exposing private realm to inspect().
  • e861807 Use more toExternalFunction() in OwnProxy().
  • e5dc24f Import order nit.
  • fd262ef Use setProperty() in shims.
  • 92de1ab Add comment for natives binding use.
  • bf4fb2b Use safeProcess in src/module/esm/extensions and src/caching-compiler.
  • 2d28cb4 Use safeProcess in src/binding.
  • 8233b80 Add safeProcess methods.

There are 17 commits in total.

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