From ad3fbe1ea0816581db572e33edd281842fb50936 Mon Sep 17 00:00:00 2001
From: Gabriel Schuster <56930714+vokeit-gschuster@users.noreply.github.com>
Date: Thu, 7 May 2020 14:15:13 +0200
Subject: [PATCH] refactor(ngcc): change async locker timeout to 250 secs
 (#36979)

Previously the `AsyncLocker` was configured to only wait
50x500ms before timing out. This is 25secs, which is often
less than a normal run of ngcc, so the chance of a timeout
flake was quite high.

The timeout is now 500x500ms, which is 250secs.

PR Close #36979
---
 packages/compiler-cli/ngcc/src/main.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/compiler-cli/ngcc/src/main.ts b/packages/compiler-cli/ngcc/src/main.ts
index 8811654e37..114e136a90 100644
--- a/packages/compiler-cli/ngcc/src/main.ts
+++ b/packages/compiler-cli/ngcc/src/main.ts
@@ -155,7 +155,7 @@ function getExecutor(
   const lockFile = new LockFileWithChildProcess(fileSystem, logger);
   if (async) {
     // Execute asynchronously (either serially or in parallel)
-    const locker = new AsyncLocker(lockFile, logger, 500, 50);
+    const locker = new AsyncLocker(lockFile, logger, 500, 500);
     if (inParallel) {
       // Execute in parallel. Use up to 8 CPU cores for workers, always reserving one for master.
       const workerCount = Math.min(8, os.cpus().length - 1);