| 9 Oct 2025 |
jade_ | * right, but the stuff that uses it is relying on NIX_ABORT_ON_WARN=true doing something at all, which it will not do if we implement the lix side the way we want. cppnix reads NIX_ABORT_ON_WARN like the nixpkgs polyfill | 23:27:55 |
jade_ | https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/pkgs/top-level/nixpkgs-basic-release-checks.nix#L49
https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/nixos/modules/misc/documentation.nix#L136
https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/lib/tests/modules.sh#L478
these three need to stop doing this | 23:29:39 |
jade_ | * https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/pkgs/top-level/nixpkgs-basic-release-checks.nix#L49 https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/nixos/modules/misc/documentation.nix#L136 https://github.com/NixOS/nixpkgs/blob/086b8fb31f8cbab212aa093fd4aa672970ff3212/lib/tests/modules.sh#L478
these three need start doing NIX_CONFIG in addition to the legacy var
| 23:29:55 |
| 10 Oct 2025 |
| @aloisw:kde.org left the room. | 07:36:24 |
raitobezarius | Rutile (Commentator2.0) feel free to ping: FYI, horrors might be bisecting the whole F2 situation | 10:43:35 |
raitobezarius | The timeouts are clearly due to F2 hanging and not exiting | 10:45:43 |
raitobezarius | Why is not clear yet to me | 10:45:47 |
raitobezarius | (Additional macOS capacity is being connected today as well) | 10:45:58 |
Rutile (Commentator2.0) feel free to ping | In reply to @raitobezarius:matrix.org Why is not clear yet to me Me neither | 10:46:01 |
raitobezarius | We will see what we can do, please be careful with the spurious +1 caused by timeouts of macOS builds | 10:46:19 |
raitobezarius | Fortunately, F1 → F2 migration doesn't touch any "user level code" | 10:46:32 |
raitobezarius | But any other change is suffering from this | 10:46:39 |