[FIXED] Failing Selenium tests on chrome in concurrency starting from Chrome Browser version 95

Issue

we are using: Selenium: 3 Chrome Version : 95

The problem:

We have a selenium test suit ( written in Watir + Ruby) which runs in concurrency of 25 on a ubuntu amazon EC2 node. Starting from chrome version 95 we experience massive test failures with the following error: timed out after 10 seconds, Element not present in 10 seconds (Watir::Wait::TimeoutError).

while the element is present on the screen as test screenshot shows in our report. The problem does not reproduce when running the tests one after another. (non-parallel). It also did not reproduce locally on our MacOs machines.

We tried: -To increase the timeouts - did not help -Run headless - seems to resolve some of the issues but cause others. -Decreasing screen resolution - which helped to reduce significantly the amount of test failures

We added bug to chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1271067

Solution

Issue resolved: The problem was that on an AWS EC2 instance there is no actual display. The team was using xvfb (Xvfb or X virtual framebuffer). The test execution used to initiate 1 virtual display for the entire test execution and for some reason, when chrome on that EC2 instance was upgraded to v95 caused the problems described when running concurrently.

Solution: A virtual display was initiated for each test by that eliminating the interference caused by concurrent execution on the EC2.

Answered By - Daniel Gold