Closed sbomer closed 2 months ago
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries See info in area-owners.md if you want to be subscribed.
@jkotas this is clearly not wasm specific
The pattern match is too generic. It matches all timeouts on all platforms. Closing since this issue accumulated a lot of noise. We should open new issues with more specific pattern match as needed.
Looks similar to https://github.com/dotnet/runtime/issues/102239
Plus I'm seeing similar timeouts in Mono_DebuggerTests_chrome, WasmBuildTests, and AllSubsets_Mono_RuntimeTests monointerpreter, which have a timeout of 180 minutes. I'm setting an error message below that covers all of these cases since they both look like infrastructure problems, but I can open a separate issue if we prefer more granular tracking.
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=711952 Build error leg or test failing: Build / browser-wasm linux Release LibraryTests Pull request: https://github.com/dotnet/runtime/pull/103665
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=711952 Error message validated:
[ran longer than the maximum time
] Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 6/18/2024 11:32:59 PM UTCReport
Summary