Ubuntu 24.04 (20260525) Image Update causes WebdriverIO tests in updated Chrome to hang

[torokati44]

Description

Related issue: webdriverio/webdriverio#15257
(Not confirmed to be the same as we have, but sounds really similar.)

I know, this could be an issue with either WebdriverIO or Chrome too, but this image update is what made it surface for us.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• Ubuntu Slim
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• macOS 26
• macOS 26 Arm64
• Windows Server 2022
• Windows Server 2025
• Windows Server 2025 with Visual Studio 2026

Image version and build link

https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20260525.161

Is it regression?

yes - worked on 20260518.149.1

Expected behavior

https://github.com/ruffle-rs/ruffle/actions/runs/26538912491/job/78175433913?pr=23775

Actual behavior

https://github.com/ruffle-rs/ruffle/actions/runs/26538954371/job/78175727180?pr=23789

Repro steps

sorry, can't help much here

[v-GeorgyPuzakov]

Hi @torokati44, thanks for the report.

The only browser change between 20260518.149.1 and 20260525.161.1 is Google Chrome 148.0.7778.167 → 148.0.7778.178. We install Chrome from the official stable channel and don’t pin versions.

So this is an upstream Chrome 148.0.7778.178 regression that has to be fixed on Google’s side. We’ll ship an image update as soon as a fixed Chrome build is released.

Workaround: install Chrome at job start with pinned to version.

[torokati44]

Will the rollout of this image update be held back until an upstream fix can be applied?

[torokati44]

That's an option that would work, but I don't think it's the right one.

[v-GeorgyPuzakov]

@torokati44 Unfortunately, we won't be doing a rollback of the entire image due to this known issue with Google Chrome. We will wait fix from google chrome. Before that you will have to use workaround. Sorry for the inconvenience.

[MaxwellMaragia]

I experience the same issue

[pierreluc16]

I experience the same issue

The solution is Workaround: install Chrome at job start with pinned to version.