提交 a240e74b 编写于 作者: S Santiago Fernandez Madero 提交者: Stephen Toub

Set MaxRetryCount to 4 for both Windows and non-Windows jobs (dotnet/corefx#34792)



Commit migrated from https://github.com/dotnet/corefx/commit/fd21fbc661a26eab435a9925fc243616a1798362
上级 cc9be71e
......@@ -28,6 +28,8 @@
<!-- This property is used to show the tests results in Azure Dev Ops. By setting this property the
test run name will be displayed as $(BuildConfiguration)-$(HelixTargetQueue) -->
<TestRunNamePrefix>$(BuildConfiguration)-</TestRunNamePrefix>
<MaxRetryCount Condition="'$(MaxRetryCount)' == ''">4</MaxRetryCount>
</PropertyGroup>
<!-- If mission control reports a test failure then fail the build whenever helix wait runs. -->
......@@ -50,12 +52,6 @@
<HelixType Condition="'$(TargetGroup)' == 'uapaot' AND '$(OfficialBuildId)' != ''">test/functional/ilc/</HelixType>
</PropertyGroup>
<PropertyGroup Condition="'$(MaxRetryCount)' == ''">
<!-- In Windows we need a higher value due to some flakyness in Nano. Can remove when helix provides new containers model -->
<MaxRetryCount Condition="'$(TargetsWindows)' == 'true'">9</MaxRetryCount>
<MaxRetryCount Condition="'$(TargetsWindows)' != 'true'">1</MaxRetryCount>
</PropertyGroup>
<PropertyGroup Condition="'$(HelixCommand)' == ''">
<!-- For windows we need to use call, since the command is going to be called from a bat script created by Helix
and we exit /b at the end of RunTests.cmd, Helix runs some other commands after ours within the bat script,
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册