Wasm test timeout: Process ... didn't exit within 00:30:00 and will be killed

[jkotas]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=632728
Build error leg or test failing: Methodical_r2.WorkItemExecution
Pull request: #100682

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": ["RuntimeIdentifier=browser-wasm", "Process .* didn't exit within .* and will be killed"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=632728
Error message validated: [RuntimeIdentifier=browser-wasm Process .* didn't exit within .* and will be killed]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/10/2024 8:18:06 AM UTC

Report

Build	Definition	Test	Pull Request
636092	dotnet/runtime	JIT_opt.WorkItemExecution	#100810
636134	dotnet/runtime	JIT_opt.WorkItemExecution
632728	dotnet/runtime	Methodical_r2.WorkItemExecution	#100682
632340	dotnet/runtime	JIT_opt.WorkItemExecution
631328	dotnet/runtime	baseservices_varargs.WorkItemExecution
630865	dotnet/runtime	tracing_eventpipe.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	6

[pavelsavara]

tracing_eventpipe.WorkItemExecution case is on iOS, not WASM

[maraf]

tracing_eventpipe.WorkItemExecution case is on iOS, not WASM

The original error (Methodical_r2.WorkItemExecution) was on wasm. The regex is too broad and catches other things as well

[pavelsavara]

See also #100757

[jkotas]

The regex is too broad and catches other things as well

I have updated the regex to be wasm specific.

[pavelsavara]

Nice, I didn't know ErrorPattern can have 2 expressions. They could be on different lines with logical 'AND` ?

Now it will probably report similar set as #99888. I'm happy to own it now.

[jkotas]

Nice, I didn't know ErrorPattern can have 2 expressions. They could be on different lines with logical 'AND` ?

Right. It is mentioned in the build analysis docs, but it is impossible to find it. I am working on a build analysis doc update to make it more discoverable.

[pavelsavara]

I think this was resolved with #100907