| 7 Jun 2023 |
 raitobezarius | I remember Julien looking into stuff like this for nix-eval-jobs I believe | 00:37:13 |
 Rick (Mindavi) | In reply to @ryantm:matrix.org
Does Hydra filter out attrpaths like "go-1.19"?
I made a hydraJobs output here
and the nix flake show output snippet is:
├───hydraJobs
│ └───x86_64-linux
│ ├───active-modules: derivation 'active-modules-1'
│ ├───"bun-0.5": derivation 'replit-module-bun-0.5'
│ ├───bundle: derivation 'nixmodules-bundle-11e31ab'
│ ├───bundle-image: derivation 'nixmodules-11e31ab'
There is a job for active-modules but not for bun-0.5
https://github.com/NixOS/hydra/pull/1286 I think it was just recently fixed | 05:48:56 |
 Julien | Ah yes | 12:22:49 |
| Julien | I’m not sure this has been deployed though | 12:24:06 |
| raitobezarius | In reply to @julienmalka:matrix.org
I’m not sure this has been deployed though but aren't you in the infra team now… ? :> | 12:37:05 |
| raitobezarius | (iknowiknow hydra is build infra) | 12:37:17 |
 vcunat | Bottom of pages
Hydra 0.1.20221124.0118770 (using nix-2.12.0pre20221116_561440b).
so probably not.
| 12:41:19 |
| raitobezarius | it would be nice to bump to Nix 2.13.3 I guess | 12:41:44 |
 ryantm | Another thing I noticed is the Nix version used for evaluation seems to be not easily configurable. A brief look at the modules indicates it uses nix.package for the builder though. | 12:51:29 |
 das_j | In reply to @ryantm:matrix.org
Another thing I noticed is the Nix version used for evaluation seems to be not easily configurable. A brief look at the modules indicates it uses nix.package for the builder though. That's a topic all by itself. Since Hydra directly links to nix, and the API is sometimes not so stable between nix versions, we usually have exactly 1 supported nix version per Hydra commit | 15:07:55 |
| das_j | I mean we could probably abstract the relevant nix functionality but I don't see me voluntarily touching C++ Code :D | 15:09:01 |
 ma27 | In reply to @raitobezarius:matrix.org
it would be nice to bump to Nix 2.13.3 I guess working fine on my own hydra, you'd have to bump up to https://github.com/NixOS/hydra/commit/f44d3d6ec9b3ca0546a82d0230a9afee4ac179c8 at least I guess | 15:09:08 |
| das_j | * I mean we could probably abstract the relevant nix functionality and add some compat tings but I don't see me voluntarily touching C++ Code :D | 15:09:09 |
|  @rimuru:gentoo.chat changed their profile picture. | 16:21:44 |
| 11 Jun 2023 |
|  @vector:tchncs.de joined the room. | 14:31:24 |
| 13 Jun 2023 |
| Julien changed their display name from Julien to JulienMalka (stop speaking german when). | 14:53:19 |
| Julien changed their display name from JulienMalka (stop speaking german when) to Julien (stop speaking german when). | 14:53:54 |
|  K900 changed their display name from K900 to K900 (Old). | 20:51:42 |
|  @federicodschonborn:matrix.org changed their profile picture. | 20:55:44 |
| Julien changed their display name from Julien (stop speaking german when) to Julien. | 21:05:28 |
 magic_rb |
how do you people deal with having packages, nixos systems, (nixng systems) and others in one flake? since the hydraJobs attribute is flat, its hard to logically group things with good names, unless i do overlay-X overlay-Y nixos-Z nixng-W | 21:20:26 |
|  K900 (deprecated) joined the room. | 21:46:20 |
| 14 Jun 2023 |
 jackdk | hydraJobs can be a nested attrset, you're just not allowed to have '.' in any attr name | 06:39:31 |
| jackdk | How can I chase down why hydra seems to be holding gcroots for basically everything? We've set each jobset to keep only 2 evaluations but I keep finding really old links in various gcroot dirs, which I would not expect | 06:46:20 |
|  raphi changed their display name from raphi (element unread channel fix when) to raphi. | 07:03:13 |
|  hexa left the room. | 16:17:15 |
| 15 Jun 2023 |
| @vector:tchncs.de removed their profile picture. | 15:50:57 |
| @vector:tchncs.de removed their display name vector. | 15:52:33 |
| @vector:tchncs.de left the room. | 15:54:17 |
| 16 Jun 2023 |
| jackdk | In reply to @jackdk:matrix.org
How can I chase down why hydra seems to be holding gcroots for basically everything? We've set each jobset to keep only 2 evaluations but I keep finding really old links in various gcroot dirs, which I would not expect I am the architect of my own suffering: the cronjob which ran hydra-update-gc-roots didn't run in the same environment as all the other hydra stuff, so it dutifully maintained the wrong gc roots dir. | 05:08:19 |
