[wasm] Bump chrome for testing - linux: 128.0.6613.119, windows: 128.0.6613.120 #107504
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
added
arch-wasm
github-actions
bot
requested review from
akoeplinger,
ilonatommy,
lewing,
maraf and
pavelsavara
|
Tagging subscribers to this area: @directhex, @matouskozak |
|
Failing with #107466, even after dotnet/xharness#1261. |
|
Still failing with timeouts. @pavelsavara had an idea that we could try to add to add more flags to chrome, like |
…in driver-browser communication.
|
It helped, we can see that the last build has no WBT failures on Windows, where the fix was used but Lib tests still fail - we did not add the |
|
/ba-g failures are #108019. |
…0.6613.120 (dotnet#107504) * Automated bump of chrome version * Addning new `BrowserArguments` is possible without changes on xharness side. * Add `--disable-gpu` to lib tests as well. * Set `PageLoadStrategy=NONE` for browser on Windows to avoid timeouts in driver-browser communication. * Remove whitespace. * Set the fixing flag for lib tests on Windows. * Fix: add args to chrome scenario, not node. * Move appended WBT args to one place. --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Ilona Tomkowicz <32700855+ilonatommy@users.noreply.github.com> Co-authored-by: Larry Ewing <lewing@microsoft.com> Co-authored-by: Ilona Tomkowicz <itomkowicz@microsoft.com>
options.setPageLoadStrategy(PageLoadStrategy.NONE);- selenium returns immediately when the page content is downloaded, opposed to waiting for a full load by default (PageLoadStrategy.NORMAL) (or at least PageLoadStrategy.EAGER - Selenium waits for DOM content) forWasmBuildTestson Windows andLibraryTeston Windows.--disable-gputhat could contribute to timeouts.