Closed scottmries closed 2 weeks ago
When running CI on another PR, Selenium would consistently fail with
Failure/Error: $driver.get fixture "/index.html" Selenium::WebDriver::Error::InvalidSessionIdError: invalid session id
This appears to be due to resourcing issues for new versions of Chrome; pinning the Chrome version in CI consistently fixes the issue.
No QA needed.
When running CI on another PR, Selenium would consistently fail with
This appears to be due to resourcing issues for new versions of Chrome; pinning the Chrome version in CI consistently fixes the issue.
No QA needed.