Repository navigation
WasmTestOnChrome timeouts in CI #105363
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Infrastructure-mono
Milestone
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=752591
Build error leg or test failing: WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution
Pull request: #105350
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": ["WasmTestOnChrome", "max 3600 seconds"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=752591
Error message validated: [WasmTestOnChrome max 3600 seconds]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2024 11:22:08 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 29 | 141 | 174 |
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Infrastructure-mono
Activity
dotnet-policy-service commentedon Jul 23, 2024
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Jul 24, 2024
Tagging subscribers to this area: @directhex, @matouskozak
See info in area-owners.md if you want to be subscribed.
ilonatommy commentedon Oct 24, 2024
This is catching all the logs with
WasmTestOnChromescenario that fail from different reasons, we are always logging in the first lines:regardless of the timeout. Currently all the recent failures are duplicates of #109024. I will close and in case real timeouts will occur, we will open a new issue - I am not able to find any real timeout log to correct the regex.