Repository navigation
Test failure: profiler\\rejit\\rejit\\rejit.cmd #35472
Description
Activity
- addedJitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modes
on Apr 26, 2020 - addeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Apr 26, 2020 - addedarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIand removeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Apr 26, 2020 This appears to be a problem only for
COMPlus_JITMinOpts=1@dotnet/jit-contrib
This is a relatively new test (added in #34411) and I suspect the failure here is not a regression.
Looks like this test is incompatible with
COMPlus_JITMinOptsas it expects some inlines to happen when jitting, and min opts supresses all inlining. It would likely fail jitstress for the right stress level, for similar reasons.We should be able to mark it as optimization sensitive to exclude it from these kinds of tests.
It is already marked with
<JitOptimizationSensitive>true</JitOptimizationSensitive>but it invokes a subprocess for testing, and that subprocess is the one impacted by minopts.So need to tweak the test code a bit to pass on this notion to the subprocess.
An alternative solution is to set the environment variables that ensure that inlining is not disabled like I did here:
runtime/src/coreclr/tests/src/JIT/opt/ObjectStackAllocation/ObjectStackAllocationTests.csproj
Lines 17 to 19 in ba8fa9e
set COMPlus_JITMinOpts=0 set COMPlus_JitDebuggable=0 set COMPlus_JitStressModeNamesNot=STRESS_RANDOM_INLINE,STRESS_MIN_OPTS Thanks @erozenfeld -- the test case was already setting some COMPlus vars in code, so I just added a few more.
Fixed via #36420.
- ghost locked as resolved and limited conversation to collaborators
on Dec 9, 2020
failed in job: runtime-coreclr jitstress 20200424.3
Error message