sandstorm-io/sandstorm

Tests can fail when Actions runner ships an older Chrome than the ChromeDriver installed by Selenium

Open

#3513 opened on Apr 18, 2021

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (6,583 stars) (737 forks)batch import
good first issuesandstorm-dev

Description

So, I noticed tests were broken yesterday, and the only error we got was hilariously because there were no screenshots to upload. I'm guessing this is the error in question though:

 Connection refused! Is selenium server started?
{
  value: {
    message: 'session not created: This version of ChromeDriver only supports Chrome version 90\n' +
      'Current browser version is 89.0.4389.114 with binary path /usr/bin/google-chrome\n' +
      '  (Driver info: chromedriver=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}),platform=Linux 5.4.0-1043-azure x86_64) (WARNING: The server did not provide any stacktrace information)\n' +
      'Command duration or timeout: 5.43 seconds\n' +
      "Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'\n" +
      "System info: host: 'fv-az235-407', ip: '10.1.1.93', os.name: 'Linux', os.arch: 'amd64', os.version: '5.4.0-1043-azure', java.version: '11.0.10'\n" +
      'Driver info: driver.version: unknown',
    error: 'session not created'
  },
  status: 33
}

Contributor guide

Tech stack
javascriptnodejsshell
Domain
testingci cd
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with CI/CD pipelinesbasic knowledge of Selenium
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue stems from a mismatch between the Chrome version installed on GitHub Actions runners and the ChromeDriver version. To fix, locate the CI configuration file (likely .github/workflows/*.yml) and pin the ChromeDriver version to match the Chrome version available on the runner, or update the action to install a compatible version. Alternatively, use a Docker container with fixed versions. Check the logs and comments for any attempted fixes.