Staging - Public Room Timeline

	Staging	345 Members
	Staging merges \| Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 \| Review Reports: https://malob.github.io/nix-review-tools-reports/	114 Servers

Load older messages

Sender	Message	Time
11 Feb 2026
K900	Not entirely sure what exactly it does	19:41:53
K900	Have not looked super closely	19:41:59
Grimmauld (any/all)	multilib stdenv when?	21:28:38
12 Feb 2026
Tristan Ross	I tried reviewing a PR targeting staging and got this: error: Cannot build '/nix/store/25szfqz836lmypkvmrwa22zsn4xqf3wq-expand-response-params.drv'. Reason: builder failed with exit code 1. Output paths: /nix/store/hd0k8s0c341wxg041g78jhggsic6s1ws-expand-response-params Last 9 log lines: > Running phase: unpackPhase > Running phase: patchPhase > Running phase: updateAutotoolsGnuConfigScriptsPhase > Running phase: configurePhase > no configure script, doing nothing > Running phase: buildPhase > gcc: error: unrecognized command-line option '-fstrict-flex-arrays=1' > /nix/store/9l34ijwa4q1wp0nnjbmnnrvgm8cgkn8v-bootstrap-stage1-stdenv-linux/setup: line 1824: pop_var_context: head of shell_variables not a function context > /nix/store/shkw4qm9qcw5sc5n1k5jznc83ny02r39-default-builder.sh: line 1: pop_var_context: head of shell_variables not a function context For full logs, run: nix log /nix/store/25szfqz836lmypkvmrwa22zsn4xqf3wq-expand-response-params.drv	04:32:40
Tristan Ross	Seems like https://github.com/NixOS/nixpkgs/pull/473648 is the culprit	04:34:58
dramforever	minimal bootstrap gcc too old for -fsfa=1?	04:37:53
Tristan Ross	Possibly	04:38:42
Tristan Ross	Idk	04:38:45
dramforever	wait what	04:38:52
Tristan Ross	I thought aarch64-linux doesn't have minimal bootstrap	04:39:04
dramforever	it's there since 13	04:39:09
Tristan Ross	Wtf, why is it broken then?	04:39:57
dramforever	oh watit nevermind didn't see aarch64-linux, let me take a look	04:40:38
Tristan Ross	For now, I'm just going to disable that hardening option.	04:40:59
dramforever	yeah pkgs/stdenv/linux/bootstrap-files/aarch64-unknown-linux-gnu.nix is still on 12	04:41:11
dramforever	how hard is it to bump that	04:41:19
Tristan Ross	Idk	04:41:23
Tristan Ross	But it would be good to not have a broken aarch64-linux stdenv	04:41:36
Tristan Ross	I got hello built with just disabling the hardening option. I'll work on bumping it over to GCC 13	04:42:03
Tristan Ross	Ideally, we should update the bootstrap a bit more frequently. It looks like the bootstrap for aarch64-linux is quite old.	04:49:59
Tristan Ross	Last time it was touched was 2023	04:50:30
Tristan Ross	* I got hello built with just disabling the hardening option. I'll work on bumping it over to GCC 13+	04:52:53
Tristan Ross	https://github.com/NixOS/nixpkgs/pull/489675 in case anyone wants to look, currently working on building a stdenv	04:55:08
Tristan Ross	no-mtab-status.sh: skipped test: internal test failure: maybe LD_PRELOAD doesn't work? Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/part-rename.log' Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/part-hardlink.log' make[3]: * [Makefile:24668: check-TESTS] Hangup make[4]: * Deleting file 'tests/mv/part-fail.log' Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/no-target-dir.log' make[4]: * Deleting file 'tests/mv/no-copy.log' Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/mv-special-1.log' Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 make[2]: * [Makefile:24920: check-am] Hangup make[1]: *** [Makefile:24419: check-recursive] Hangup Hangup "$@" >> "$log_file" 2>&1 ./build-aux/test-driver: fork: Cannot allocate memory coreutils didn't build, memory shouldn't be a problem since I have 512GB	05:53:53
Tristan Ross	* no-mtab-status.sh: skipped test: internal test failure: maybe LD_PRELOAD doesn't work? Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/part-rename.log' Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/part-hardlink.log' make[3]: * [Makefile:24668: check-TESTS] Hangup make[4]: * Deleting file 'tests/mv/part-fail.log' Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/no-target-dir.log' make[4]: * Deleting file 'tests/mv/no-copy.log' Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 make[4]: * Deleting file 'tests/mv/mv-special-1.log' Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 Hangup "$@" >> "$log_file" 2>&1 make[2]: * [Makefile:24920: check-am] Hangup make[1]: *** [Makefile:24419: check-recursive] Hangup Hangup "$@" >> "$log_file" 2>&1 ./build-aux/test-driver: fork: Cannot allocate memory coreutils didn't pass a test, memory shouldn't be a problem since I have 512GB	05:54:09
ghpzin	reduce threads, it seems to be a new thing after update	05:54:27
Tristan Ross	Hmm, so basically I have way too many resources available?	05:55:28
ghpzin	Have not looked why it happens exactly, but from experience with default it failed 5 times in a row spamming these `Hangup` messages. With `--cores 1` tests pass.	06:08:46
Tristan Ross	Huh, I dropped it to 8 and it passes	06:12:52
Tristan Ross	Sweet, I got an stdenv now	06:13:23

Show newer messages

Back to Room ListRoom Version: 6