Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of addr-to-ip-port is breaking the build 🚨 #1446

Closed
greenkeeper bot opened this issue Jul 27, 2018 · 3 comments
Closed

An in-range update of addr-to-ip-port is breaking the build 🚨 #1446

greenkeeper bot opened this issue Jul 27, 2018 · 3 comments
Labels

Comments

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jul 27, 2018

Version 1.5.1 of addr-to-ip-port was just published.

Branch Build failing 🚨
Dependency addr-to-ip-port
Current Version 1.5.0
Type dependency

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

addr-to-ip-port 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
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 2 commits.

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 greenkeeper bot added the greenkeeper label Jul 27, 2018
@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Jul 27, 2018

Version 1.5.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by commits ahead by 0, behind by 2.

See the full diff

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

@greenkeeper greenkeeper bot commented Jul 27, 2018

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

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 27, 2018

False positive

@feross feross closed this Jul 27, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.