Closed Kiskae closed 1 year ago
Thanks for the report!
@colemickens prepared a possible fix with https://github.com/DeterminateSystems/nix-installer-action/pull/47, I'll be cutting that this morning.
I'm not sure how useful it would be, but perhaps the error should be propagated instead of going through the uncaught exception handler?
const exit_code: number = await new Promise((resolve, reject) => {
spawned.on("close", resolve);
spawned.on("error", reject);
});
EDIT: might need to replace close
with exit
, since close
gets emitted after error
or exit
Haven't seen the error since updating the action, will reopen if it shows up again.
Great!
Recently been getting run failures with an
Error: spawn ETXTBSY
error.Tracking down the source appears to show https://github.com/DeterminateSystems/nix-installer-action/blob/721f94f7df2665d750964b01ac153ce9c1151e57/src/main.ts#L268-L270 failing and causing an uncaught exception to propagate through the action.
This specific failure reminds me of the race condition mentioned in the README of https://github.com/buildbarn/bb-remote-execution - requiring separate processes to handle downloading of an executable and executing that executable.
Excerpt from workflow log: