fix(ngcc): provide a unique exit code for timeouts (#36838)
When ngcc fails due to a timeout waiting for another process to complete, it was not failing with a unique exit code, so that it was not possible to know if the process can be restarted; compared to ngcc failing for some more fatal reason. Now if ngcc exits because of a timeout, the exit code will be 177. PR Close #36838
This commit is contained in:

committed by
Alex Rickabaugh

parent
ee435761fd
commit
d805526659
@ -24,7 +24,7 @@ if (require.main === module) {
|
||||
process.exitCode = 0;
|
||||
} catch (e) {
|
||||
console.error(e.stack || e.message);
|
||||
process.exit(1);
|
||||
process.exit(typeof e.code === 'number' ? e.code : 1);
|
||||
}
|
||||
})();
|
||||
}
|
||||
|
Reference in New Issue
Block a user