Skip to content

[wasm] Bump chrome for testing - linux: 128.0.6613.113 - #107259

Closed
github-actions[bot] wants to merge 4 commits into
mainfrom
update-chrome-version-10669217505
Closed

github-actions[bot] wants to merge 4 commits into
mainfrom
update-chrome-version-10669217505

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 2, 2024

Copy link
Copy Markdown
Contributor

No description provided.

@ilonatommy

Copy link
Copy Markdown
Member

Might have timeout failures that we observed in #107131.

@ilonatommy ilonatommy changed the title [wasm] Bump chrome for testing - linux: 128.0.6613.113, windows: 128.0.6613.86 [wasm] Bump chrome for testing - linux: 128.0.6613.113 Sep 6, 2024
@ilonatommy

ilonatommy commented Sep 6, 2024 •

Copy link
Copy Markdown
Member

Windows timeouts on chrome can be reproduced locally on WBT and are being investigated. Chrome version used: 128.0.6613.120.

The exception that I can reproduce locally is caused by line:
https://github.com/dotnet/xharness/blob/ab056567a15664fe3430a18cd0d97077831f2bb8/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmTestBrowserCommand.cs#L123
that containing no elements, throws fail: Error while closing browser: System.InvalidOperationException: Sequence contains no elements

I logged a new issue to track it: #107466

@ilonatommy

Copy link
Copy Markdown
Member

Linux also has interesting timeouts in lib tests. Let's wait for propagation of dotnet/xharness#1261 to see if it changed anything. I am closing this one in favor of automatic bumps.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant