Uh oh!
There was an error while loading. Please reload this page.
[wasm] Bump chrome for testing - linux: 128.0.6613.119, windows: 128.0.6613.120 - #107504
Conversation
Tagging subscribers to this area: @directhex, @matouskozak |
ilonatommy
commented
Sep 10, 2024
Failing with #107466, even after dotnet/xharness#1261. |
ilonatommy
commented
Sep 13, 2024
Still failing with timeouts. @pavelsavara had an idea that we could try to add to add more flags to chrome, like |
Uh oh!
There was an error while loading. Please reload this page.
…in driver-browser communication.
ilonatommy
commented
Sep 18, 2024
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 |
ilonatommy
commented
Sep 19, 2024
/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.