Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 4 commits into from

Conversation

github-actions[bot]
Copy link
Contributor

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

No description provided.

@ilonatommy
Copy link
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
Copy link
Member

ilonatommy commented Sep 6, 2024

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
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 join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant