>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3521685. --> Reported by: [fjgarlin](https://www.drupal.org/user/2495842) Related to !350 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>It appears that some of the <code>selenium/chromedriver</code> versions are more prone to random errors.<br> Core is pinning a specific version of the driver and they update it "manually", like in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/drupal/issues/3471113" title="Status: Postponed">#3471113: Update to selenium/standalone-chrome:134</a></span> (and related issues).</p> <p>The templates are using the <code>latest</code> version, as seen in <a href="https://git.drupalcode.org/project/gitlab_templates/-/blob/main/includes/include.drupalci.main.yml?ref_type=heads#L20">this line</a>.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>If you are getting random errors, maybe you are affected by this.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Decide whether we should pin the version to match core's.</p> <p>Core is currently on version 127, but hoping to jump to 134.</p> > Related issue: [Issue #3471113](https://www.drupal.org/node/3471113) > Related issue: [Issue #3514999](https://www.drupal.org/node/3514999)