Hydra | 381 Members | |
| 109 Servers |
| Sender | Message | Time |
|---|---|---|
| 19 Aug 2023 | ||
| https://github.com/NixOS/nixpkgs/pull/250248 | 20:41:06 | |
In reply to @hacker1024:matrix.org* ^ ~if you have more than 48 cores~ nvm you only have 4 | 20:42:38 | |
* ~maybe making this https://github.com/NixOS/nixpkgs/blob/bbfcab42fd6f93f1f45fdd50544735edf79ffe90/nixos/lib/make-squashfs.nix#L25-L29 dependant on stdenv.buildPlatform.is32bit would help?~ | 20:42:53 | |
| 20 Aug 2023 | ||
| 17:45:48 | ||
| 18:26:45 | ||
| 24 Aug 2023 | ||
| 18:37:25 | ||
| 25 Aug 2023 | ||
| 03:57:56 | ||
| 22:06:40 | ||
| 22:26:46 | ||
| 30 Aug 2023 | ||
| 13:19:00 | ||
| 13:19:32 | ||
| it seems unlikely to me that this is a regression caused by a change in Hydra, but maybe someone has an (other) idea: https://github.com/NixOS/nixos-org-configurations/issues/270 | 13:57:18 | |
| 31 Aug 2023 | ||
| 16:13:17 | ||
| 21:46:16 | ||
| 2 Sep 2023 | ||
| We have a main repository that contains Nix expressions for Hydra and core packages. We also have several auxiliary repositories with their own `default.nix` files. We generate jobsets for PRs to any repository. Some PRs, however, are from branches that are out of date and either lack a `default.nix` or are broken due to changes in the core repository. It seems that the generated jobsets with evaluation errors will keep getting evaluated periodically, even if the inputs do not change. This is a significant drain on resources. Is there a way to tell Hydra to disable jobsets if an evaluation error occurs regularly? | 23:47:47 | |
| * We have a main repository that contains Nix expressions for Hydra and core packages. We also have several auxiliary repositories with their own `default.nix` files. We generate jobsets for PRs to any repository. Some PRs, however, are from branches that are out of date, and either lack a `default.nix`, or are broken due to changes in the core repository. It seems that the generated jobsets with evaluation errors will keep getting evaluated periodically, even if the inputs do not change. This is a significant drain on resources. Is there a way to tell Hydra to disable jobsets if an evaluation error occurs regularly? | 23:48:24 | |
| 3 Sep 2023 | ||
| is there an overview of the time that evaluation takes in hydra? I see the latest evaluation's duration, but I'd love a duration over time... | 14:07:02 | |
| 4 Sep 2023 | ||
In reply to @antifuchs:asf.computeri remember there being a metrics endpoint, i forget if eval time was in it | 02:12:35 | |
| ah! metrics endpoint, right: I'll have a look, thanks for the pointer | 02:28:51 | |
| 08:19:58 | ||
| 20:11:54 | ||
| 5 Sep 2023 | ||
| 15:28:28 | ||
| 15:32:15 | ||
| 10 Sep 2023 | ||
| 04:24:43 | ||
| 13 Sep 2023 | ||
| 09:15:18 | ||
| 14 Sep 2023 | ||
would meta.timeout help with this? | 19:25:18 | |
*
would meta.timeout help with this? | 19:25:52 | |
*
would meta.timeout help with this? | 19:26:05 | |
| or maybe meta.maxSilent? | 19:26:16 | |
| Either could help, but what's up with the build? | 20:44:15 | |