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
This commit is contained in:
parent
38f805cd06
commit
f8941a5b6b
@ -33,7 +33,7 @@ export interface NgccProjectConfig<T = NgccPackageConfig> {
|
|||||||
export interface ProcessLockingConfiguration {
|
export interface ProcessLockingConfiguration {
|
||||||
/**
|
/**
|
||||||
* The number of times the AsyncLocker will attempt to lock the process before failing.
|
* The number of times the AsyncLocker will attempt to lock the process before failing.
|
||||||
* Defaults to 50.
|
* Defaults to 500.
|
||||||
*/
|
*/
|
||||||
retryAttempts?: number;
|
retryAttempts?: number;
|
||||||
/**
|
/**
|
||||||
@ -148,7 +148,7 @@ export const DEFAULT_NGCC_CONFIG: NgccProjectConfig = {
|
|||||||
},
|
},
|
||||||
locking: {
|
locking: {
|
||||||
retryDelay: 500,
|
retryDelay: 500,
|
||||||
retryAttempts: 50,
|
retryAttempts: 500,
|
||||||
}
|
}
|
||||||
};
|
};
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user