| 10 Jan 2022 |
 @grahamc:nixos.org | I'm thinking about adding the sha256 hash of a path's input to the "revision" of a PathInput. Right now it is just a timestamp which causes problems if you evaluate the same path input twice in the same second and it has changed | 15:51:29 |
| @grahamc:nixos.org | re: https://github.com/NixOS/hydra/pull/1096 | 16:01:34 |
| @grahamc:nixos.org | any reason this is a bad idea? | 16:01:42 |
 das_j | In reply to @andreas.schraegle:helsinki-systems.de
which remindes me, hydra-eval-jobs started segfaulting for us yesterday and I haven't figured out why, yet. https://github.com/NixOS/nix/pull/5875 | 17:00:08 |
| @grahamc:nixos.org | exciting | 17:00:30 |
 ajs124 | In reply to @grahamc:nixos.org
exciting I'd prefer it boring, tbh | 17:01:26 |
| das_j | In reply to @grahamc:nixos.org
any reason this is a bad idea? Don't really see one | 17:08:06 |
| @grahamc:nixos.org | dang das_j good stuff | 18:44:27 |
| das_j | I'm surprised myself :D | 18:44:36 |
| das_j | Just emptying out our local patches | 18:44:44 |
| @grahamc:nixos.org | nice | 18:45:04 |
| das_j | oof theres still sed -i 's/evalSettings.restrictEval = true/evalSettings.restrictEval = false/' "$(find -name hydra-eval-jobs.cc)" 👀 | 18:45:24 |
| @grahamc:nixos.org | das_j: I'm inclined to just hit merge on this PR. | 18:58:52 |
| das_j | I won't keep you from it ;) | 19:05:30 |
| das_j | we have these blessed PRs that we've been running for some time now:
# restart buttons
"836" = "sha256-BKtSgJQarVxkveeU4QqtOtqpgq76826COvL5BdRPvbc=";
# GitInput: Avoid fetch if rev is available
"868" = "sha256-dTFGWhfiANs5Z5ScmZxFaCZPZfAVBJOceEOvVMHShSw=";
# queue-runner status in topbar
"869" = "sha256-iFpMV4Z5VE7YmvnAHAydUQYk0FNKNarPYqRHEAuT4/w=";
# tailon
"957" = "sha256-M7MiBcG3DCezdyg7HgNnLWPlJcU2NgLUyI1LXlihXrU=";
# improved UI
"965" = "sha256-VJ6JwPFWwT5qy+dBsqecnvKtmHZ+VemCqYE6EmiWQQM=";
# print whats being evaluated
"1094" = "sha256-U6m8XySqZ/j6qYWGvSeZ7zLip25NGk4PREMo4HJS/X8=";
# fix warnings and logging
"1098" = "sha256-RD9zvAjzVLFq0hzZiFg7JrPvLdlwL249wQLlx9OKU4s=";
| 19:05:57 |
| @grahamc:nixos.org | https://github.com/NixOS/hydra/pull/1101 is in prep to this commit: https://github.com/NixOS/hydra/commit/6f387b363cc9b687c859756d153908add8065149 which proposes sending cached_build_finished and cached_build_queued events to be able to send status events externally in a non-spammy way | 21:56:50 |
|  @ius:nltrix.net joined the room. | 23:20:37 |
| 11 Jan 2022 |
| @ius:nltrix.net | Has anyone investigated why the search is so slow (particularly on NixOS hydra, but I guess it's a general defect at least in theory)? | 00:51:33 |
| @grahamc:nixos.org | I've done a lot of research in to it, and there are a bunch of options on making it faster | 00:53:09 |
| @grahamc:nixos.org | it depends on what you're searching for | 00:53:32 |
| @ius:nltrix.net | Perhaps it's in part my novice interactions with Hydra (I hardly know 'er), but it's not helping in getting me familiar. (end of rant part) | 00:54:35 |
| @ius:nltrix.net | Now I did do some sleuthing, and found e.g. https://github.com/NixOS/hydra/pull/854 | 00:54:52 |
| @grahamc:nixos.org | yeah, and the comments on https://github.com/NixOS/hydra/pull/853 include some of my research | 00:55:11 |
| @grahamc:nixos.org | in general I haven't worked on making them faster because of time limits :) | 00:55:25 |
| @ius:nltrix.net | Yes, I saw that ticket as well. | 00:55:38 |
| @ius:nltrix.net | Anyhow, it's exactly the issue I'm experiencing. Times out on buildoutputs.path ILIKE ?, which relates to: https://github.com/NixOS/hydra/blob/master/src/lib/Hydra/Controller/Root.pm#L477-L487 | 00:56:38 |
| @grahamc:nixos.org | what is your use case for search? | 00:57:00 |
| @ius:nltrix.net | Both seem to involve derivation paths, so I'm wondering why there's a LIKE in the first place? | 00:57:11 |
| @ius:nltrix.net | I wanted to search a nix path in this case | 00:57:22 |
| @ius:nltrix.net | To be really precise, my input was: yah9mf7x2ycalb28gg9ximh49g0akkrn-audit-riscv64-unknown-linux-gnu-2.8.5-bin | 00:57:54 |
