Selenium grid 4.8.3 hub + node test times out on ubuntu-latest since 12 November

Open
#44,231 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
51/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, java, typescript
Domain
ci-cd, testing

Research direction

Start with tests/installation/connect-to-selenium.spec.ts and the BT-100 test at tests/library/browsertype-launch-selenium.spec.ts:124; inspect how the test starts the Selenium hub and node, and how download-selenium.js selects the server version. Then review the package installation workflow's Java setup and compare runs where the node rejects --grid-url with successful attempts. Done means the intermittent timeout is explained and the test passes consistently on Ubuntu.

Written by the indexing model from the issue text.

Description

The installation test connect to selenium started to need retries on the three package-installations-ubuntu-latest jobs on 12 November. The start time matches the move of ubuntu-latest to the ubuntu-26.04 image (see #44094). The cause is not confirmed.

Failing test

tests/installation/connect-to-selenium.spec.ts runs npm run test -- selenium.spec. In each failed attempt, one inner test fails:

[chromium-library] › tests/library/browsertype-launch-selenium.spec.ts:124:1 › BT-100 selenium grid 4.8.3 hub + node chromium
Test timeout of 90000ms exceeded.

The other Selenium tests pass in the same attempt, also BT-098 selenium grid 3.141.59 hub + node chromium and BT-099 selenium grid 4.8.3 standalone chromium.

Numbers

Runs on main, 12 November 18:22 UTC to 18 November, 57 runs for each job:

Job Runs with a failed first attempt Failed after all retries
package-installations-ubuntu-latest 13 1
package-installations-ubuntu-latest-node24 20 0
package-installations-ubuntu-latest-node26 11 0
  • From 22 October to 12 November the test had one failed attempt in about 200 runs for each job, with a different error.
  • The same failure occurred in 27 pull request runs after 12 November.
  • package-installations-macos-latest and package-installations-windows-latest do not show it.
What the output shows

In each failed attempt, the Selenium node process does not accept --grid-url and prints its usage text:

====== java -Dwebdriver.chrome.driver=.../chromedriver -jar .../selenium/selenium-server-4.8.3.jar node --grid-url http://127.0.0.1:15123 --port 15124
Was passed main parameter '--grid-url' but no main parameter was defined in your arg class
Usage: node [options]

Then node.waitForOutput('Node has been added') in BT-100 never resolves, and the test times out.

The hub output in the same attempts has this warning, which JDK 24 and later print:

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by io.netty.util.internal.PlatformDependent0$4 (.../selenium-server-4.8.3.jar)

The workflow does not set a Java version, so the job uses the default Java of the runner image.

Not known
  • Why the same command passes on a retry.
  • Whether the node process prints the same message in passing attempts. The output of passing attempts is not kept.
Possible fixes
  • Set a fixed Java version for the job with actions/setup-java.
  • Update the Selenium 4 server that download-selenium.js downloads.
Example runs
Dominant language
TypeScript
Stars
100k
Forks
6.9k
Avg merge
16h 8m
Merged PRs (30d)
281

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/playwright

All issues in microsoft/playwright

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.