Pin chromedriver version to avoid random test failures

Created on 29 April 2025, 4 days ago

Problem/Motivation

It appears that some of the selenium/chromedriver versions are more prone to random errors.
Core is pinning a specific version of the driver and they update it "manually", like in 📌 Update to selenium/standalone-chrome:128 Active (and related issues).

The templates are using the latest version, as seen in this line.

Steps to reproduce

If you are getting random errors, maybe you are affected by this.

Proposed resolution

Decide whether we should pin the version to match core's.

Core is currently on version 127, but hoping to jump to 134.

📌 Task
Status

Active

Component

gitlab-ci

Created by

🇪🇸Spain fjgarlin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024