| 19 Oct 2024 |
 ma27 | ohh the nixpkgs module, yeah I see. | 13:13:49 |
| 20 Oct 2024 |
 hexa | https://github.com/NixOS/hydra/commit/031aaa065bf001099deea946a3ff6bb87766fb7a | 00:09:52 |
| hexa | discovered by puck 🙏 | 00:10:04 |
| 23 Oct 2024 |
|  @luna-null:matrix.org changed their display name from Autumn to luna-null. | 09:49:20 |
 Rick (Mindavi) | I find this story a bit sad: https://github.com/NixOS/infra/commit/bc53abb25ad5b7a658b5961cf4aa4e79dca04fe9 | 11:55:49 |
| Rick (Mindavi) | Was also looking for monitoring as there is for h.n.o and apparently that's how it works | 11:56:34 |
| ma27 | fwiw there's also https://github.com/helsinki-systems/hydra_exporter, but I never got to trying it out so far. | 11:57:17 |
| Rick (Mindavi) | Already started hacking something together with the json Prometheus exporter but that script seems a lot more done than my hacks. Still unfortunate that the decision was made to build it outside of hydra 😅 | 11:57:48 |
| Rick (Mindavi) | I'll probably try that out instead of copying the infra python script that has a hardcoded url | 13:16:48 |
| hexa | oh yeah, the hydra exporter … totally forgot abotu that | 13:16:48 |
| hexa | * oh yeah, the hydra exporter … totally forgot about that | 13:16:50 |
|  quentin joined the room. | 22:43:02 |
| 24 Oct 2024 |
|  @swendel:curious.bio left the room. | 00:03:42 |
|  @rewina:matrix.org left the room. | 05:38:12 |
| 25 Oct 2024 |
| Rick (Mindavi) | In reply to @ma27:nicht-so.sexy
fwiw there's also https://github.com/helsinki-systems/hydra_exporter, but I never got to trying it out so far. It was actually really easy to get this running, so next step is threading it through my config | 07:10:58 |
| 27 Oct 2024 |
|  Austin Horstman joined the room. | 02:47:06 |
| 29 Oct 2024 |
 Christian Theune | Hmmm | 20:45:54 |
| Christian Theune | Looks like the namedConstituents feature isn't quite doing anything ... | 20:46:09 |
| Christian Theune | I just noticed that the jobs using that don't actually block on the constituents they advertise ... | 20:46:32 |
| * Christian Theune stares at the cpp code ... | 20:46:38 |
| Christian Theune | and apparently it isn't in use by nixpkgs anyway (maybe because it's broken?) | 20:47:19 |
| Christian Theune | aaaaah | 20:52:47 |
| Christian Theune | namedConstituents isn't what goes into the derivation. one needs to pass in the constituents as strings and then hydra internally turns that into the namedConstituents list ... | 20:53:15 |
|  Toma joined the room. | 20:53:19 |
| Christian Theune | thanks ma27 | 20:55:02 |
| Toma | Is there a way to make hydra not cache a package?
I've seen this discussion: https://discourse.nixos.org/t/how-to-exclude-derivation-in-a-package-closure-from-the-binary-cache/50144
This would be useful for https://github.com/NixOS/nixpkgs/pull/349360, where the vendor directory is not itself a FOD, but constucted from a FOD. This would mean AFAICT that the vendor directory would always be rebuilt when its inputs change, since it's not a FOD. (The creation of the vendor directory is pretty cheap after you have the FOD)
| 21:00:07 |
| Toma | * Is there a way to make hydra not cache a package?
I've seen this discussion: https://discourse.nixos.org/t/how-to-exclude-derivation-in-a-package-closure-from-the-binary-cache/50144
This would be useful for https://github.com/NixOS/nixpkgs/pull/349360, where the vendor directory is not itself a FOD, but constucted from a FOD. This would mean AFAICT that the vendor directory would always be rebuilt when its inputs change, since it's not a FOD, polluting the cache unnecessarily. (The creation of the vendor directory is pretty cheap after you have the FOD)
| 21:00:50 |
| Christian Theune | Eelco: I'm wondering whether the namedConstituents feature should be working correctly when used recursively ... I'm seeing weird results where a job (release) that has another job (tested) as a constituent that in turn has constituents (the tests) only lists the tested job as a build dependency but not as a constituents and becomes green in hydra before tested actually has all its constituents fulfilled ... | 21:41:31 |
| 31 Oct 2024 |
 vcunat | In reply to @tomasajt:matrix.org
Is there a way to make hydra not cache a package?
I've seen this discussion: https://discourse.nixos.org/t/how-to-exclude-derivation-in-a-package-closure-from-the-binary-cache/50144
This would be useful for https://github.com/NixOS/nixpkgs/pull/349360, where the vendor directory is not itself a FOD, but constucted from a FOD. This would mean AFAICT that the vendor directory would always be rebuilt when its inputs change, since it's not a FOD, polluting the cache unnecessarily. (The creation of the vendor directory is pretty cheap after you have the FOD)
I think that discourse thread answers it all. | 12:24:37 |
| vcunat | In reply to @tomasajt:matrix.org
Is there a way to make hydra not cache a package?
I've seen this discussion: https://discourse.nixos.org/t/how-to-exclude-derivation-in-a-package-closure-from-the-binary-cache/50144
This would be useful for https://github.com/NixOS/nixpkgs/pull/349360, where the vendor directory is not itself a FOD, but constucted from a FOD. This would mean AFAICT that the vendor directory would always be rebuilt when its inputs change, since it's not a FOD, polluting the cache unnecessarily. (The creation of the vendor directory is pretty cheap after you have the FOD)
* I think the discourse thread answers it all. | 12:24:47 |
