| 26 Jun 2021 |
dadada (they/them) | See https://nixos.wiki/wiki/Flakes There is an overview of the most common keys in outputs and what they are used for. | 12:15:18 |
wucke13 | dadada: What a surprise to see you here 😀 | 14:17:40 |
wucke13 | In reply to @tim:stratum0.org wucke13 hydraJobs."<attr>"."<system>" = derivation; should work. To come back to my question, where in nixosConfigurations.my-machine do I find the relevant derivation which builds most of the configuration (without generating an ISO or such stuff, I just want the store to be populated with everything needed to actually build said config). | 14:21:50 |
wucke13 | Answering my own question: I think .#nixosConfigurations.my-machine.config.system.build.toplevel will do :) | 14:29:26 |
dadada (they/them) | In reply to @wucke13:matrix.org Answering my own question: I think .#nixosConfigurations.my-machine.config.system.build.toplevel will do :) Thanks for posting the solution. I've also been looking for this derivation. | 15:33:49 |
wucke13 | Well, in that case I have a nother convenience snippet:
hydraJobs = builtins.listToAttrs (lib.mapAttrsToList (machine: config:
lib.nameValuePair machine {
"x86_64-linux" = config.config.system.build.toplevel;
}) nixosConfigurations);
Any feedback on how the system can be read from an existing nixosConfiguration would be welcome, to fix the remaining ugly code
| 16:39:36 |
wucke13 | And again I think I have an answer to my own question:
hydraJobs = builtins.listToAttrs (lib.mapAttrsToList (machine: config:
lib.nameValuePair machine {
"${config.config.nixpkgs.system}" = config.config.system.build.toplevel;
}) nixosConfigurations);
The system can be read from .#nixosConfigurations.my-machine.config.nixpkgs.system
| 18:31:54 |
wucke13 | Even more noise: where can the timeout be configured for hydra jobs? Couldn't find the term timeout in the manual nor the nixos options | 18:54:02 |
| 28 Jun 2021 |
@grahamc:nixos.org | wucke13: I https://github.com/NixOS/hydra/pull/979/files | 14:01:06 |
@grahamc:nixos.org | RFR^ | 14:31:05 |
@grahamc:nixos.org | wucke13: don't just 😏, what do you think? :) | 15:01:50 |
wucke13 | I will leave a review later tonight. First impression was 😏 though 😄 | 16:03:55 |
| 29 Jun 2021 |
@grahamc:nixos.org | Just deployed #887 adding how long an evaluation took to https://hydra.nixos.org/jobset/nixos/staging | 15:10:45 |
das_j | this is starting to look more and more like my hydra ;) | 15:11:37 |
@grahamc:nixos.org | thanks das_j ! | 15:11:38 |
@grahamc:nixos.org | hehe | 15:11:41 |
sterni | 25min without ifd 😳 | 15:19:56 |
@grahamc:nixos.org | 2 things at play:
- evaluating staging often means creating a lot of files, and the IO itself can be costly
- evaluating NixOS means evaluating tests which are computationally costly
| 15:23:27 |
sterni | oh yeah didn't see the nixos part | 15:24:40 |
| 30 Jun 2021 |
| putchar joined the room. | 12:36:16 |
| cw (just got delta) changed their display name from cw (28 cycles) to cw (Vi/Vim). | 16:27:54 |
samueldr | hmmm | 21:37:43 |
| 2 Jul 2021 |
Taneb | Any idea what could cause Hydra to not perform a build when it's able to, there's no other builds running, and it does straight away when I click the bump this build button? The machine it builds and runs on did run out of disk space but it had been restored by the time Hydra performed the relevant eval | 08:28:40 |
| 30 Jun 2021 |
samueldr | Collecting from unknown thread
[...]
error: unexpected EOF reading a line
| 21:37:56 |
samueldr | hydra ate the evaluation error here
https://hydra.nixos.org/jobset/mobile-nixos/unstable#tabs-errors | 21:38:08 |
| 2 Jul 2021 |
das_j | You need to restart the queue runner from time to time because it sometimes decides it doesn't have to run the queue | 08:33:22 |
das_j | I have a pr somewhere in the hydra project that adds dedicated buttons for this because it happens so often for us | 08:33:44 |
Taneb | That's... not a particularly satisfying answer | 08:39:59 |
ajs124 | https://github.com/NixOS/hydra/pull/836 | 08:40:52 |
ajs124 | In reply to @janne.hess:helsinki-systems.de You need to restart the queue runner from time to time because it sometimes decides it doesn't have to run the queue The queue runner works in mysterious ways, doesn't it? | 08:41:21 |