Repository navigation
Test failure: JIT/Directed/tailcall/more_tailcalls/more_tailcalls.cmd #99410
Description
Test timeout
Pipeline: runtime-coreclr gcstress0x3-gcstress0xc
Job: coreclr linux arm Checked gcstress0xc
03:24:36.395 Running test: JIT/Directed/tailcall/more_tailcalls/more_tailcalls.cmd
Invoking: sudo ls -l /home/helixbot/dotnetbuild/dumps/coredump.226.dmp.crashreport.json
stdout: -rw------- 1 helixbot2 adm 24482 Mar 7 03:24 /home/helixbot/dotnetbuild/dumps/coredump.226.dmp.crashreport.json
=========================================
Child process took too long. Timed out... Exiting...
App Exit Code: 110
Expected: 100
Actual: 110
END EXECUTION - FAILED
Failing since 20240302.1
cc @janvorli
Metadata
Metadata
Assignees
Labels
CLR JIT issues involving JIT internal stress modesWork that is important, but not critical for the releaseCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIThe test is disabled in source code against the issueThere is an active PR which will close this issue when it is merged
Activity
BruceForstall commentedon Mar 7, 2024
Three additional failures in gcstress-extra:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=592476&view=ms.vss-test-web.build-test-results-tab
coreclr linux arm Checked gcstress0xc_disabler2r_heapverify1
coreclr linux arm Checked gcstress0xc_disabler2r
coreclr linux arm Checked gcstress0xc_tailcallstress
BruceForstall commentedon Mar 18, 2024
@dotnet/jit-contrib This is a GCStress issue apparently related to tailcall.
SingleAccretion commentedon Apr 3, 2024
I wonder if this could have something to do with the recent conversion of copy helpers to managed code.
Stack args for fast tail calls are set up in a no-gc region. If a copy helper that calls managed code ends up in this region, problems will follow.
Reenable more_tailcalls under GCStress
Reenable more_tailcalls under GCStress (dotnet#106287)
Reenable more_tailcalls under GCStress (dotnet#106287)