From a240e74b7ea6081ac6924e1c0f258de5a0097dad Mon Sep 17 00:00:00 2001
From: Santiago Fernandez Madero <safern@microsoft.com>
Date: Thu, 24 Jan 2019 05:22:52 -0800
Subject: [PATCH] Set MaxRetryCount to 4 for both Windows and non-Windows jobs
 (dotnet/corefx#34792)

Commit migrated from https://github.com/dotnet/corefx/commit/fd21fbc661a26eab435a9925fc243616a1798362
---
 eng/sendtohelix.proj | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/eng/sendtohelix.proj b/eng/sendtohelix.proj
index 885a5c03318..b6821aa098a 100644
--- a/eng/sendtohelix.proj
+++ b/eng/sendtohelix.proj
@@ -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,
-- 
GitLab