| 9 Oct 2025 |
 raitobezarius | can you try to order a revert of the suspected commit and rerun the CI for you? | 19:45:15 |
| raitobezarius | There's unaddressed comments on the CL, hence why it stalled | 19:45:46 |
| raitobezarius | Ah, I understood | 19:46:33 |
| raitobezarius | That's terrifying :( | 19:46:36 |
| raitobezarius | I will try to prioritize looking into that | 19:46:42 |
 Philip Taron (UTC-8) | Yeah, I saw that -- I'm asking if my summary of the feedback, the bullet points, still represents the thinking of the team. | 20:22:28 |
 jade_ | nixpkgs really needs to stop using those environment variables and do it with the arg instead, and that's going to be a compat hazard in the migration period between now and later. it's a shame we didn't get to fixing this in nixpkgs 10 months ago e.g. with feature detection, but alas. | 20:36:50 |
| jade_ | in fact, nixpkgs should just set the NIX_CONFIG debug-on-warn thing assuming it is matched between cppnix and lix, imo | 20:37:30 |
| jade_ | * in fact, nixpkgs should just set the NIX_CONFIG abort-on-warn thing assuming it is matched between cppnix and lix, imo | 20:37:56 |
| jade_ | I would appreciate this being fixed in nixpkgs' test suite before we can release this feature into GA | 20:38:24 |
| jade_ | * I would appreciate this being fixed in nixpkgs' test suite before we can release this feature into GA, because it means that it avoids a period of nixpkgs CI not working properly. | 20:38:47 |
| Philip Taron (UTC-8) | I'm in the channel in part because I was grossed out by the code in Nixpkgs. | 21:02:24 |
| Philip Taron (UTC-8) | The code we're talking about is this function, right? | 21:08:07 |
| Philip Taron (UTC-8) | That codepath is only lit up for Lix, since every supported cppnix has builtins.warn. | 21:08:45 |
|  tavinator joined the room. | 22:24:02 |
| 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 well | 23:26:52 |
| 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 | 23:27:01 |
| jade_ | thus the users of builtins.warn inside nixpkgs test driver code need to start setting NIX_CONFIG so that they don't require us to implement the legacy environment variable | 23:27:31 |
| 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 |
