summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergey Andreenko <seandree@microsoft.com>2019-06-14 12:49:29 -0700
committerSergey Andreenko <seandree@microsoft.com>2019-06-14 12:53:51 -0700
commit5af3a154e728edc6574dadd4c9400530973990dd (patch)
tree14f287d003fe9a3153049991a879dad558725e69
parentbe341339d1764d7f136a3b4d1c985c5b6108dcb0 (diff)
downloadcoreclr-5af3a154e728edc6574dadd4c9400530973990dd.tar.gz
coreclr-5af3a154e728edc6574dadd4c9400530973990dd.tar.bz2
coreclr-5af3a154e728edc6574dadd4c9400530973990dd.zip
Do not force GCStress at all.
It doesn't work on OSX and Alpine. It shows random failures on Windows as well, that we do not want to see in our PR/CI outerloop testing.
-rw-r--r--tests/src/JIT/Regression/JitBlue/GitHub_23199/GitHub_23199.csproj2
1 files changed, 0 insertions, 2 deletions
diff --git a/tests/src/JIT/Regression/JitBlue/GitHub_23199/GitHub_23199.csproj b/tests/src/JIT/Regression/JitBlue/GitHub_23199/GitHub_23199.csproj
index 3abee21adf..a0ae081a1a 100644
--- a/tests/src/JIT/Regression/JitBlue/GitHub_23199/GitHub_23199.csproj
+++ b/tests/src/JIT/Regression/JitBlue/GitHub_23199/GitHub_23199.csproj
@@ -34,12 +34,10 @@
<CLRTestBatchPreCommands><![CDATA[
$(CLRTestBatchPreCommands)
set COMPlus_GcStressOnDirectCalls=1
-set COMPlus_GCStress=0xc
]]></CLRTestBatchPreCommands>
<BashCLRTestPreCommands><![CDATA[
$(BashCLRTestPreCommands)
export COMPlus_GcStressOnDirectCalls=1
-export COMPlus_GCStress=0xc
]]></BashCLRTestPreCommands>
</PropertyGroup>
<ItemGroup>