Some GC tests timing out in CI on wasm on 9.0

[svick]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1435334
Build error leg or test failing: GC/API/GC/GetAllocatedBytesForCurrentThread/GetAllocatedBytesForCurrentThread.sh
Pull request: #125816

Error Message

DO NOT USE JSON BELOW IF THIS IS A BUILD BREAK otherwise build analysis will allow pull requests to merge that break the build worse. For a build break, do not use this issue form. Make a regular new issue.

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

{
  "ErrorMessage": "Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

cmdLine:/root/helix/work/workitem/e/GC/API/GC/GetAllocatedBytesForCurrentThread/GetAllocatedBytesForCurrentThread.sh Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 5/26/2026 1:24:07 PM, end: 5/26/2026 1:34:07 PM)
Return code:      -100

cmdLine:/root/helix/work/workitem/e/GC/API/GCHandleCollector/Count/Count.sh Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 5/26/2026 1:24:12 PM, end: 5/26/2026 1:34:12 PM)
Return code:      -100

cmdLine:/root/helix/work/workitem/e/GC/Scenarios/muldimjagary/muldimjagary/muldimjagary.sh Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 5/26/2026 1:34:32 PM, end: 5/26/2026 1:44:32 PM)
Return code:      -100

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1435334
Error message validated: [Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 5/26/2026 4:35:47 PM UTC

Report

Build	Repository	Test	Pull Request
1482369	dotnet/runtime	baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd
1479819	dotnet/runtime	Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.cmd	#129543
1479810	dotnet/runtime	baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd
1478372	dotnet/runtime	Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.cmd	#129777
1463377	dotnet/runtime	JIT/superpmi/superpmicollect/superpmicollect.cmd	#129373
1463068	dotnet/runtime	JIT/superpmi/superpmicollect/superpmicollect.cmd	#129373
1457995	dotnet/runtime	tracing/eventpipe/pauseonstart/pauseonstart/pauseonstart.cmd	#128384
1456424	dotnet/runtime	tracing/eventpipe/applystartuphook/applystartuphook/applystartuphook.cmd	#129179
1446501	dotnet/runtime	baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd
1443946	dotnet/runtime	profiler/handles/handles/handles.sh

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	3	10

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @dotnet/gc
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @BrzVlad
See info in area-owners.md if you want to be subscribed.

[BrzVlad]

Closing this issue as it matches on any runtime test timeout. The timeouts are not GC related and the filter is too broad