An in-range update of chromedriver is breaking the build π¨
greenkeeper opened this issue Β· 10 comments
The devDependency chromedriver was updated from 2.42.0
to 2.42.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
chromedriver 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).
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 π΄
After pinning to 2.42.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
chromedriver was updated from2.42.1
to2.43.0
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.43.0
to2.43.1
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.43.1
to2.43.2
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.43.2
to2.43.3
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.43.3
to2.43.4
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.43.4
to2.44.0
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.44.0
to2.44.1
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.44.1
to2.45.0
.
Your tests are still failing with this version. Compare changes
- The
devDependency
chromedriver was updated from2.45.0
to2.46.0
.
Your tests are still failing with this version. Compare changes