From f8941a5b6b8e673ead98d998ffed948393469e58 Mon Sep 17 00:00:00 2001 From: Pete Bacon Darwin Date: Tue, 28 Apr 2020 16:42:31 +0100 Subject: [PATCH] refactor(ngcc): change async locker timeout to 250 secs (#36838) 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 default is now 500x500ms, which is 250secs. If this is too high for some projects then it can be changed via the `ngcc.config.js` project file. PR Close #36838 --- packages/compiler-cli/ngcc/src/packages/configuration.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/compiler-cli/ngcc/src/packages/configuration.ts b/packages/compiler-cli/ngcc/src/packages/configuration.ts index 092ac5db69..e79b5fd6d4 100644 --- a/packages/compiler-cli/ngcc/src/packages/configuration.ts +++ b/packages/compiler-cli/ngcc/src/packages/configuration.ts @@ -33,7 +33,7 @@ export interface NgccProjectConfig { export interface ProcessLockingConfiguration { /** * The number of times the AsyncLocker will attempt to lock the process before failing. - * Defaults to 50. + * Defaults to 500. */ retryAttempts?: number; /** @@ -148,7 +148,7 @@ export const DEFAULT_NGCC_CONFIG: NgccProjectConfig = { }, locking: { retryDelay: 500, - retryAttempts: 50, + retryAttempts: 500, } };