From f64ee1216ae3f2b5d7b377bebdef4e13e9daaa40 Mon Sep 17 00:00:00 2001
From: Jeff Genovy <29107334+jefgen@users.noreply.github.com>
Date: Thu, 17 Sep 2020 11:56:13 -0700
Subject: [PATCH] ICU-21291 Increase the timeout for the Exhaustive Test CI
 builds

---
 .ci-builds/.azure-exhaustive-tests.yml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/.ci-builds/.azure-exhaustive-tests.yml b/.ci-builds/.azure-exhaustive-tests.yml
index c7309157b30..8390fdd21e1 100644
--- a/.ci-builds/.azure-exhaustive-tests.yml
+++ b/.ci-builds/.azure-exhaustive-tests.yml
@@ -16,6 +16,9 @@ trigger:
     include:
     - '*'
     exclude:
+    - .github/*
+    - .ci-builds/.azure-pipelines.yml
+    - .ci-builds/.azure-valgrind.yml
     - docs/*
     - tools/*
     - vendor/*
@@ -27,11 +30,10 @@ trigger:
 
 jobs:
 #-------------------------------------------------------------------------
-# Note: The exhaustive tests for J take longer than the C tests. They 
-# take roughly 85 min to complete on the Azure VMs.
+# Note: The exhaustive tests can take more than 1 hour to complete.
 - job: ICU4J_OpenJDK_Ubuntu_1604
   displayName: 'J: Linux OpenJDK (Ubuntu 16.04)'
-  timeoutInMinutes: 100
+  timeoutInMinutes: 120
   pool:
     vmImage: 'Ubuntu 16.04'
     demands: ant
@@ -50,11 +52,10 @@ jobs:
       displayName: 'List failures (if any)'
       timeoutInMinutes: 2
 #-------------------------------------------------------------------------
-# Note: The exhaustive tests take roughly 65 mins to complete on the
-# Azure VMs.
+# Note: The exhaustive tests can take more than 1 hour to complete.
 - job: ICU4C_Clang_Exhaustive_Ubuntu_1604
   displayName: 'C: Linux Clang Exhaustive Tests (Ubuntu 16.04)'
-  timeoutInMinutes: 80
+  timeoutInMinutes: 120
   pool:
     vmImage: 'Ubuntu 16.04'
   steps: