4a33ce1dc1
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: If34ab692120e5e299575bf8044aa5802145ab494 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2658 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de> |
||
---|---|---|
.. | ||
advent-of-code/2020 | ||
arglib | ||
emacs-tree-sitter-move | ||
execline | ||
netencode | ||
netstring | ||
nixpkgs-rewriter | ||
writers | ||
imap-idle.nix | ||
imap-idle.rs | ||
lib.nix | ||
OWNERS | ||
read-http.nix | ||
read-http.rs | ||
rust-crates.nix | ||
tree-sitter.nix |