| 18 Feb 2022 |
|  @test:boba.best removed their display name Tseb (Old). | 11:48:49 |
| @test:boba.best left the room. | 12:59:15 |
| 19 Feb 2022 |
|  Rhys joined the room. | 08:15:26 |
 ma27 | as I'm currently going through my open PRs, anybody out there who wants to take a look at my oldest open PR (https://github.com/NixOS/hydra/pull/743,
Add a filter for maintainers in the jobset-eval view) these days? %) | 19:56:04 |
| 21 Feb 2022 |
|  cw (not sticky anymore) changed their display name from Chuck Winter to Chinchilla Wetreat. | 00:48:21 |
|  Rickard Nilsson joined the room. | 13:02:39 |
 @grahamc:nixos.org | I'd love a C++-competent review of https://github.com/NixOS/hydra/pull/1163 before I merge it in ~4h | 13:31:29 |
 @trofi:matrix.org | I think it's ok. (std::string) job["drvPath"] is a bit non-idiomatic. std::string (job["drvPath"]) would be more natural. | 15:13:30 |
| 25 Feb 2022 |
|  @schnecfk:ruhr-uni-bochum.de joined the room. | 10:57:54 |
| 28 Feb 2022 |
|  Florian | W3F changed their display name from Florian | W3F to Florian | W3F - OoO 02.03.. | 10:15:42 |
 toonn | Feature request: It would be really sweet if a default comparison could be set that is different from just the previous eval of a jobset. Example use case, when developing something targeting staging-next I'm only interested in comparing jobs to a specific staging-next evaluation. Finding that evaluation by the staging-next commit the branch is based on is a tedious process and if it's been | 12:43:52 |
| toonn | a while since I looked at an evaluation I have probably forgotten the point of comparison and need to go digging for it again. | 12:43:54 |
| @grahamc:nixos.org | I'm a little confused, because I think this is what it already does. | 14:57:10 |
| toonn | Not for me. When I navigate to an evaluation of a jobset the comparison is always relative to the previous eval of that same jobset. | 15:09:57 |
| @grahamc:nixos.org | ah | 15:10:16 |
| @grahamc:nixos.org | so is the idea you want to click "Compare to" and then click "staging-next" and have it pick the most recent? | 15:10:51 |
| @grahamc:nixos.org | can you give me an example jobset whose branch is targeting staging-next? | 15:11:12 |
| @grahamc:nixos.org | I want to see what this is like first hand | 15:11:18 |
| toonn | Not quite. I want to be able to pick a comparison that is from then on always used by default. | 15:11:27 |
| @grahamc:nixos.org | oh I see | 15:11:33 |
| @grahamc:nixos.org | still, can you give me an example? | 15:11:53 |
| toonn | This is an evaluation that I want to compare to staging-next rather than previous evals of the jobset, https://hydra.nixos.org/jobset/nixpkgs/toonn-wip | 15:12:07 |
| toonn | Ah, darn, I meant to link a specific eval of that, just pick the most recent one. | 15:12:28 |
| @grahamc:nixos.org | cool, I think I see one of the problems | 15:14:19 |
| @grahamc:nixos.org | you click the compare link and it takes you to https://hydra.nixos.org/eval/1746179?compare=staging-next&full=0 which is fixed in time | 15:14:31 |
| @grahamc:nixos.org | and so you have to do that clicky-around process to make this comparison | 15:14:47 |
| @grahamc:nixos.org | what if you could get a link that was like: https://hydra.nixos.org/jobset/nixpkgs/toonn-wip/latest-eval?compare=staging-next | 15:15:09 |
| toonn | grahamc: The link doesn't quite work for me. I already do that. But when I focus on something else for a while or something the urls in the history are close to useless because I don't know eval IDs by heart. That's why I'd love to have a way to set a little bit of state for an evaluation so that future me or others I link the eval to always end up with a useful comparison. | 15:20:00 |
| @grahamc:nixos.org | yeah | 15:20:20 |
| @grahamc:nixos.org | I understand, but I don't mean remember eval IDs -- I mean that URL would always be fresh with the most recent eval | 15:20:47 |
