| 7 Jul 2023 |
 cole-h | * $ GC_INITIAL_HEAP_SIZE=8g NIX_REMOTE= time nix-env -f ./outpaths.nix -qaP --no-name --out-path --arg checkMeta true >/dev/null
warning: unknown setting 'experimental-features'
805.99user 13.80system 13:39.89elapsed 99%CPU (0avgtext+0avgdata 54731940maxresident)k
0inputs+8outputs (1major+13685712minor)pagefaults 0swaps
13m40s on the same commit using Nix 2.13
| 17:31:51 |
| cole-h | Err Nix 2.3 | 17:33:15 |
| cole-h | lol | 17:33:16 |
| cole-h | * $ GC_INITIAL_HEAP_SIZE=8g NIX_REMOTE= time nix-env -f ./outpaths.nix -qaP --no-name --out-path --arg checkMeta true >/dev/null
warning: unknown setting 'experimental-features'
805.99user 13.80system 13:39.89elapsed 99%CPU (0avgtext+0avgdata 54731940maxresident)k
0inputs+8outputs (1major+13685712minor)pagefaults 0swaps
13m40s on the same commit using Nix 2.3
| 17:33:17 |
| cole-h | (coming back) using 2.15.1:
$ GC_INITIAL_HEAP_SIZE=8g NIX_REMOTE= time nix-env -f ./outpaths.nix -qaP --no-name --out-path --arg checkMeta true >/dev/null
680.15user 11.32system 11:31.55elapsed 99%CPU (0avgtext+0avgdata 43949464maxresident)k
0inputs+0outputs (0major+11026151minor)pagefaults 0swaps
| 20:59:25 |
| 8 Jul 2023 |
 Vladimír Čunát | Hmm, so both CPU and RAM usage would be significantly worse. I thought of doing this for the tarball job instead, but the RAM requirements wouldn't most likely become a problem with the current infra. | 08:05:06 |
| Vladimír Čunát | * Hmm, so both CPU and RAM usage would be significantly worse. I thought of doing this for the tarball job instead, but the RAM requirements would most likely become a problem with the current infra. | 08:05:18 |
| Vladimír Čunát | The corresponding machines have only 64 GiB physical RAM. | 08:07:24 |
 sterni | In reply to @cole-h:matrix.org
Is there a case that would have been caught with 2.3 that wasn't? We already had path interpolation slip into master before: https://github.com/NixOS/ofborg/issues/612 | 08:55:27 |
| 10 Jul 2023 |
|  Simon Menke joined the room. | 08:57:06 |
| 11 Jul 2023 |
 Artturin | https://github.com/NixOS/ofborg/pull/642 | 01:00:41 |
| Artturin | will be a great addition | 01:00:52 |
| 13 Jul 2023 |
| Vladimír Čunát changed their display name from @vcunat to vcunat. | 08:27:38 |
| 14 Jul 2023 |
| cole-h changed their display name from cole-h to cole-h (back 1 Aug). | 23:51:17 |
| 15 Jul 2023 |
 piegames | Hi, I'm currently implementing RFC 127 in https://github.com/NixOS/nixpkgs/pull/177272. There is this comment in check-meta.nix, "!!! reason strings are hardcoded into OfBorg, make sure to keep them in sync". So I'd like to coordinate this change with the OfBorg maintainers | 19:22:09 |
| 16 Jul 2023 |
| piegames | So I did some keyword search through the OfBorg code base, the only relevant thing I found is https://github.com/NixOS/ofborg/blob/released/ofborg/src/outpaths.nix#L28-L34, which does not look like it needs updating | 08:02:16 |
| piegames | On the other hand, the implementation pull request causes OfBorg internal errors (according to the label it added), so clearly there is something weird going on here | 08:02:48 |
| piegames | Where do I find the OfBorg error logs? | 08:04:56 |
 Lily Foster | In reply to @piegames:matrix.org
Where do I find the OfBorg error logs? I'm not sure where the ofborg logs are, but if it did fail in outpath caculation, you could try to run that manually with the instructions at https://github.com/NixOS/ofborg#running-meta-checks-locally (I just hope you have a system with 60+ GiB of RAM though...) | 10:55:04 |
| piegames | Unfortunately that is not an option for me then | 11:00:21 |
| Lily Foster | In reply to @piegames:matrix.org
Unfortunately that is not an option for me then So I'm running some stuff manually for you and it looks like ofborg may be failing in the stdenv check, which runs with a merged stderr+stdout to attempt to get the stdenv output path (but this PR throws a bunch of maintainless warnings to stderr) | 11:18:20 |
| piegames | Thanks. | 11:19:26 |
| Lily Foster | (I feel like ofborg should probably not be merging stderr and stdout when keep_stdout is passed to nix::Nix::run but I do not know much on why that is like that to begin with) | 11:19:59 |
| piegames | I simply forgot to set the maintainerless default to "ignore" again, but actually that's a good thing because there definitely will be warn-by-default things in the log in the future | 11:20:00 |
| Lily Foster | (or at least the stdenv check and possibly others should be run with nix::Nix::run_stderr_stdout which differentiates stderr/stdout) | 11:21:14 |
| Lily Foster | You can replicate this one particular issue with nix-env --query --available --no-name --attr-path --out-path --option extra-experimental-features no-url-literals -f . -A stdenv yourself though (no obscenely large amount of RAM required)
I am admittedly just guessing though since running ofborg one-off is still not currently supported and I'm just manually running the nix commands that it does and inspecting code
| 11:22:36 |
| Lily Foster | (cole just seems to be out for the next few weeks, so I figured I'd help a bit since I'm not sure who else would be able to get ofborg logs) | 11:23:00 |
| piegames | Does ofborg automatically remove the "internal error" label or should I do it manually? | 14:09:53 |
 Mindavi | It does remove it automatically, if it stays then the ofborg maintainer will sometimes have a look at the related logs | 14:12:25 |
| Artturin | In reply to @rick:matrix.ciphernetics.nl
It does remove it automatically, if it stays then the ofborg maintainer will sometimes have a look at the related logs It's not removed automatically | 14:34:01 |
