Uh oh!
There was an error while loading. Please reload this page.
[browser] Increase timeout and clean up after failed attempts of launching browser when testing - #107865
[browser] Increase timeout and clean up after failed attempts of launching browser when testing#107865ilonatommy wants to merge 34 commits into
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ilonatommy
commented
Sep 16, 2024
It does not help: |
lewing
commented
Sep 16, 2024
Can we check if there are other running chrome instances or something to help diagnose the issue? |
ilonatommy
commented
Sep 17, 2024
If we keep the last commit about killing all other chromes, running WBT locally can be a nuisance. If it works, we should check for running on CI and only then call |
ilonatommy
commented
Sep 17, 2024
It's not about chrome instances, |
ilonatommy
commented
Sep 18, 2024
The chrome bump will be ready soon: #107504, maybe that might help? |
ilonatommy
commented
Sep 20, 2024
Failures are on Windows with |
ilonatommy
commented
Oct 1, 2024
The issue is still existing after the Playwright bump, see: https://helix.dot.net/api/2019-06-17/jobs/8d53b01d-113d-4e65-a893-6a5d825a52b6/workitems/Workloads-NoWebcil-ST-Wasm.Build.Tests.TestAppScenarios.LibraryInitializerTests/console. |
ilonatommy
commented
Oct 2, 2024
Using default chromium from Playwright is broken on Linux: |
1st and 2nd run with default chrome + higher timeout: success. |
This is a playground for fixing #107771.
The issue is hit only on Windows, where we are running WBT sequentially.
Changes:
linux-x64dir, not inlinux. Node requires elevated execution rights, sochmod +xpath was changed accordingly.Browserand disposing ofPlaywright.