Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Upgrading Capybara to latest version makes Gitlab CI fail #1080

Open
8vius opened this issue May 2, 2019 · 0 comments
Open

Upgrading Capybara to latest version makes Gitlab CI fail #1080

8vius opened this issue May 2, 2019 · 0 comments

Comments

@8vius
Copy link

8vius commented May 2, 2019

I'm upgrading my Capybara to the latest version (up from 2.18.0) This causes the normalized_whitespace deprecation running to show up a lot when running my tests. I read that pulling the master branch of the gem fixes the issue, effectively it does but now my CI on Gitlab fails with:

Errno::ENOENT: No such file or directory - /builds/products/micheticket/vendor/ruby/2.5.0/bundler/gems/capybara-webkit-77fdac424cd6/bin/webkit_server

Does anyone have any Idea on how to fix this?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@8vius