Deduplicate JIT/Methodical/tailcall tests and make them mergeable #63031
Conversation
This change fixes mergeability of tailcall tests: apart from simple deduplication of the test class names and visibility fixes I have modified the pointer and reference tests to stop using Environment.Exit for exiting the test as that kills the merged wrapper in in-proc execution; I have also fixed them to have main within a class. In two cases (recurse_ep_void and test_virt) I found out that I had previously put the Fact attribute on the wrong method so I fixed that too. I renamed the two C# test projects to better match the test of tests (widen to widen_r to indicate it's a release test and thread-race_il_r to thread-race_r as it's not an IL test). Thanks Tomas
ghost
assigned
|
Tagging subscribers to this area: @hoyosjs Issue DetailsThis change fixes mergeability of tailcall tests: apart from simple Thanks Tomas /cc @dotnet/jit-contrib
|
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
2 participants
This change fixes mergeability of tailcall tests: apart from simple
deduplication of the test class names and visibility fixes
I have modified the pointer and reference tests to stop using
Environment.Exit for exiting the test as that kills the merged
wrapper in in-proc execution; I have also fixed them to have main
within a class. In two cases (recurse_ep_void and test_virt)
I found out that I had previously put the Fact attribute on the
wrong method so I fixed that too. I renamed the two C# test
projects to better match the test of tests (widen to widen_r to
indicate it's a release test and thread-race_il_r to thread-race_r
as it's not an IL test).
Thanks
Tomas
/cc @dotnet/jit-contrib