-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
SpawnBrowserAsync on Windows #107771
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
@ilonatommy please take a look |
It looks that delay increase mitigated the issue. In case of more problems, consider investigating the Windows image details we're using on CI: microsoft/playwright#32897. The last weeks failures are on net9, the fix will be backported there to clean to count |
It hasn't been seen for months, we can consider #108474 was the fix. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=806657
Build error leg or test failing: Workloads-NoWebcil-NoFingerprint-ST-Wasm.Build.Tests.WorkItemExecution
Pull request: #107746
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=806657
Error message validated:
[System.Exception : Failed to launch browser after 3 attempts
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/12/2024 10:35:30 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: