about summary refs log tree commit diff
path: root/third_party/README.md
diff options
context:
space:
mode:
authorProfpatsch <mail@profpatsch.de>2021-03-25T21·50+0100
committerProfpatsch <mail@profpatsch.de>2021-03-26T11·01+0000
commit4a33ce1dc141c0e377dbebff8708afd494c24f04 (patch)
tree61b418d81c358dafb8474b56b0c34c7a92e05766 /third_party/README.md
parent45f5eb97a64c6c56c431a805b4facb2935f5a9f0 (diff)
fix(users/Profpatsch/writers): use s6-portable-utils r/2335
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>
Diffstat (limited to 'third_party/README.md')
0 files changed, 0 insertions, 0 deletions