Fix CI test failures caused by ChromeDriver (PT-185924955) #1209
Conversation
There was a problem hiding this comment.
Did you try the more forward compatible solution described here:
titusfortner/webdrivers#247 (comment)
Basically remove webdrivers and upgrade selenium-webdriver. It sounds like it has to be version 4.11.0 for this approach to work.
|
@scytacki Dropping |
|
@dougmartin can you help @433eros with this. It looks like the error is that an additional library (probably capybara) has to be updated. The first spec test failure is on this line: https://github.com/concord-consortium/rigse/blob/master/rails/spec/support/feature_helper.rb#L3 The cucumber tests with javascript started running, but didn't get far enough to tell if they would have the same problem. Maybe the update is too big to tackle now, but I hopeful (since we brought things up to date recently) that updating won't be too bad. |
433eros
force-pushed
the
failing-ci-workflow
branch
from
df8aa5e
to
fdf2a6e
Compare
|
@scytacki & @dougmartin reverted to original PR state |
Fixes deprecation warning message: "/home/runner/work/rigse/rigse/rails/spec/support/solr_spec_helper.rb:23: warning: calling URI.open via Kernel#open is deprecated, call URI.open directly or use URI#open" See: https://github.com/concord-consortium/rigse/actions/runs/5728882369/job/15530837575#step:17:9
Try to fix CI warning: "Please set `Webdrivers::Chromedriver.required_version = <desired driver version>` to a known chromedriver version" See: https://github.com/concord-consortium/rigse/actions/runs/5728882369/job/15530837575#step:17:12
wget is more suitable for downloading files than curl because it handles interruptions by default
433eros
force-pushed
the
failing-ci-workflow
branch
from
fdf2a6e
to
3a74d85
Compare
See story card PT-185924955 for more information