| 29 Apr 2022 |
@ulrikstrid:matrix.org | In reply to @artturin:matrix.org Could you add the error messages you got and a link to that to https://nixos.wiki/wiki/Hydra#Known_Issues Finally got around to add this 😅 | 07:55:12 |
kayla (she/they) | I was told that people in this channel might appreciate the PR I have adding more output about worker processes termination to hydra-eval-jobs, so that error: unexpected EOF reading a line is not the only information about how it failed. | 16:51:55 |
@ulrikstrid:matrix.org | In reply to @kayla.fire:matrix.org I was told that people in this channel might appreciate the PR I have adding more output about worker processes termination to hydra-eval-jobs, so that error: unexpected EOF reading a line is not the only information about how it failed. Literally the issue I had | 17:38:39 |
@ulrikstrid:matrix.org | What is the easiest way of getting my hydra build into somewhere I can use as a cache? I have multiple builders in my setup for different platforms | 17:39:44 |
ajs124 | You can just serve the store of your hydra machine. If that's what you want to do. | 17:42:55 |
@ulrikstrid:matrix.org | Will my builders upload to the hydra machine? | 17:46:31 |
@ulrikstrid:matrix.org | I feel like I missed something | 17:46:45 |
ajs124 | Hydra copies the build results back from the builders into its own store | 17:56:43 |
@ulrikstrid:matrix.org | Oh, okay, that's easy then. Thank you | 17:57:34 |
@grahamc:nixos.org | hydra itself can present a binary cache | 17:58:06 |
@grahamc:nixos.org | as long as you provide the signing key, I think it does that automatically? not sure | 17:58:16 |
@grahamc:nixos.org | (I've never used it for that) | 17:58:21 |
ajs124 | In reply to @grahamc:nixos.org (I've never used it for that) (nobody ever has) | 17:58:57 |
@grahamc:nixos.org | lol somebody has ... | 17:59:05 |
@grahamc:nixos.org | though maybe we should delete its support for it | 17:59:12 |
@grahamc:nixos.org | it isn't very good at it | 17:59:17 |
@grahamc:nixos.org | what is the shock face for? | 17:59:40 |
@grahamc:nixos.org | it isn't uniquely bad at it afaik | 18:00:02 |
ajs124 | hydra is not very good at multiple things.
it's also very good at a few other things.
as always, the reactions are mostly trolling and should be ignored. | 18:00:57 |
@grahamc:nixos.org | ok :) | 18:01:13 |
@grahamc:nixos.org | that said, you know me, I'm absolutely okay with dropping features that are not well thought out or frequently used | 18:01:41 |
@grahamc:nixos.org | unless there are tests for it | 18:02:30 |
@grahamc:nixos.org | if someone cared enough to add tests, I treat that a bit differently | 18:02:47 |
@ulrikstrid:matrix.org | Might be better to have a good solution to serve a box store that is separate from hydra | 18:02:57 |
@ulrikstrid:matrix.org | * Might be better to have a good solution to serve a nix store that is separate from hydra | 18:03:15 |
@grahamc:nixos.org | hydra.nixos.oorg pushes everything to S3 / S3-like storage, which works quite well | 18:03:39 |
Dandellion | Now that I know it has this feature I'm going to start using it 🙈 | 18:03:56 |
@ulrikstrid:matrix.org | In reply to @dandellion:dodsorf.as Now that I know it has this feature I'm going to start using it 🙈 Add tests or grahamc (he/him): might remove it! 😂 | 18:04:30 |
das_j | In reply to @dandellion:dodsorf.as Now that I know it has this feature I'm going to start using it 🙈 There's harmonia now if you don't want to push the closures through python: https://github.com/helsinki-systems/harmonia (although highly experimental for now) | 18:04:47 |
@grahamc:nixos.org | neat | 18:04:54 |