d0b635f6f2
Same as 221698c603dcb318c609b4d21cb2a9fada44a14c We had a bunch of instances of https://github.com/NixOS/nix/issues/2176, where nix would exit with a “killed by signal 9” error. According to Eelco in that issue, this is perfectly normal behaviour of course, and appears if the last command in a loop closes `stdout` or `stdin`, then the builder will SIGKILL it immediately. This is of course also a perfectly fine error message for that case. It turns out that mainly GNU coreutils exhibit this behaviour … Let’s see if using a more sane tool suite fixes that. Change-Id: Iaf9e542952ca36c02208a3f067f575ba978272b4 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2663 Reviewed-by: Profpatsch <mail@profpatsch.de> Tested-by: BuildkiteCI |
||
---|---|---|
.. | ||
binify | ||
bufCheck | ||
buildGo | ||
buildLisp | ||
drvSeqL | ||
emptyDerivation | ||
escapeExecline | ||
getBins | ||
mergePatch | ||
readTree | ||
runExecline | ||
runTestsuite | ||
tag | ||
tailscale | ||
utils | ||
writeElispBin | ||
writeExecline | ||
writeScript | ||
writeScriptBin | ||
yants | ||
OWNERS |