| 25 Jul 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 01:56:43 |
|  nf changed their profile picture. | 16:43:10 |
|  @yuri:nekover.se joined the room. | 16:56:01 |
|  pbsds changed their display name from pbsds to pbsds (UTC+1). | 19:03:56 |
| 26 Jul 2023 |
|  @janik0:matrix.org changed their display name from Janik (they/them) (es/ihr) to Janik (they/them). | 18:20:27 |
|  @rimuru:gentoo.chat changed their profile picture. | 18:39:07 |
| 27 Jul 2023 |
|  ribosomerocker joined the room. | 02:58:18 |
|  UserSv4 joined the room. | 16:57:25 |
| 28 Jul 2023 |
|  chayleaf joined the room. | 04:26:21 |
| chayleaf | is it normal that hydra takes a stupidly long time to evaluate my flake? I basically do hydraJobs.system-config.x86_64-linux = nixosConfigurations.system, and I've yet to see any jobs being queued after a couple hours of eval | 04:49:44 |
| chayleaf | I do see a lot of hydra-eval-jobs processes being spawned | 04:53:27 |
| chayleaf | * is it normal that hydra takes a stupidly long time to evaluate my flake? I basically did hydraJobs.system-config.x86_64-linux = nixosConfigurations.system, and I've yet to see any jobs being queued after a couple hours of eval | 04:54:21 |
| chayleaf | * is it normal that hydra takes a stupidly long time to evaluate my flake? I basically did `hydraJobs.system-config.x86_64-linux = nixosConfigurations.system`, and I've yet to see any jobs being queued after a couple hours of eval | 04:54:37 |
| chayleaf | I hope I'm doing something wrong because as it is even a bash script is better | 04:58:43 |
| chayleaf | okay I did do something wrong, I should've used nixosConfigurations.system.config.system.build.toplevel instead, hopefully this will fix the issue | 05:18:27 |
| chayleaf | yep it works, though it doesn't show build status (Caught exception in Hydra::Controller::Build->build "[31;1merror:[0m opening a connection to remote store '[35;1mdaemon[0m' previously failed at /nix/store/971v8rm57fb2hpsgzx22df98vm87wqvm-hydra-2023-06-25/libexec/hydra/lib/Hydra/Controller/Build.pm line 83."). Is it because hydra is in allowed-users but not trusted-users? | 05:59:22 |
 cransom | hydra-queue-runner needs to be in trusted-users | 15:14:26 |
| cransom | if you are using the module, it will be there already. | 15:14:46 |
| chayleaf | oh thanks | 15:17:40 |
| chayleaf | and i am using the module but it isnt | 15:17:59 |
 ajs124 | which one? the nixpkgs one or the one from the hydra repo?
I seem to remember them having some differences, but idk if that would be one of them. | 15:19:21 |
| chayleaf | (neither was nix-serve for that matter) | 15:18:31 |
| chayleaf | maybe it's because list settings arent getting merged in whatever freeform type nix.settings is used | 15:20:53 |
| chayleaf | the nixpkgs one | 15:23:58 |
| chayleaf | oh nvm it did get set | 15:24:50 |
| chayleaf | so the issue is something else i guess | 15:24:59 |
| chayleaf | the actual non-cached error is Caught exception in Hydra::Controller::Build->build "[31;1merror:[0m cannot open connection to remote store '[35;1mdaemon[0m': [35;1m[31;1merror:[0m reading from file: [35;1mConnection reset by peer[0m[0m at /nix/store/971v8rm57fb2hpsgzx22df98vm87wqvm-hydra-2023-06-25/libexec/hydra/lib/Hydra/Controller/Build.pm line 83." btw, though I guess that was more or less to be expected | 15:28:11 |
 Rick (Mindavi) | In reply to @andreas.schraegle:helsinki-systems.de
which one? the nixpkgs one or the one from the hydra repo?
I seem to remember them having some differences, but idk if that would be one of them. If you know about any consider making an issue on the nixpkgs tracker | 15:28:48 |
| Rick (Mindavi) | I am running the nixpkgs one | 15:29:16 |
| ajs124 | In reply to @rick:matrix.ciphernetics.nl
If you know about any consider making an issue on the nixpkgs tracker it's probably just outdated information. there used to be a time where certain perl deps also were only part of the hydra flake instead of being in nixpkgs, but I think it's been some years since these issues. | 15:30:33 |
