| 21 May 2026 |
 Sergei Zimmerman (xokdvium) | What’s the overall plan to continue maintaining HNO deployment? For now infra pins a specific commit, but it would be valuable to have a branch where additional fixes can be applied while the new queue runner is not in a good state. | 12:15:36 |
 vcunat | I'm not sure why it pins the commit, but it's exactly on the tip of the infra branch. | 12:18:19 |
| vcunat | * I'm not sure why it pins the commit, but it's exactly on the tip of the infra branch currently. | 12:18:36 |
| Sergei Zimmerman (xokdvium) | Ah ok | 12:19:35 |
 hexa | huh? it is what? | 13:29:15 |
| hexa | hydra = {
url = "github:NixOS/hydra/a40d42862da88cce78a27dd594e1484a034aac4d";
inputs.nixpkgs.follows = "nixpkgs";
inputs.nix.follows = "nix";
};
| 13:29:41 |
| vcunat | The infra branch points to a40d42862da88cce78a27dd594e1484a034aac4d right now. | 13:30:16 |
| hexa | sorry, but what infra branch where? | 13:30:37 |
| hexa | oh, in hydra | 13:30:49 |
| vcunat | github:NixOS/hydra/infra | 13:30:52 |
| vcunat | Sounds better to me to have this in there (and relock), but that's just a nit. | 13:31:21 |
| hexa | that was created very recently | 13:31:27 |
| hexa | 3 days ago in fact | 13:31:44 |
| hexa | I'd prefer naming this legacy-queue-runner or sth | 13:32:10 |
| hexa | better describes the purpose | 13:32:32 |
| vcunat | I thought the purpose is to have a branch which shows what's running on hydra.nixos.org | 13:32:54 |
| vcunat | * I thought the purpose of infra is to have a branch which shows what's running on hydra.nixos.org | 13:33:01 |
| vcunat | * I thought the purpose of NixOS/hydra/infra is to have a branch which shows what's running on hydra.nixos.org | 13:33:13 |
| vcunat | * I thought the purpose of NixOS/hydra/infra is to have a branch which shows what's running on hydra.nixos.org right now | 13:33:22 |
| hexa | what we track is ultimately in our lockfiles | 13:34:32 |
| hexa | but I'd rather follow a branch than pin a commit | 13:34:45 |
| 22 May 2026 |
|  chayleaf changed their profile picture. | 08:48:01 |
 Janne | I created that a couple of days ago to PR against it | 11:06:25 |
| hexa | infra- > queue-runner-legacy | 11:08:01 |
| hexa | Redacted or Malformed Event | 11:08:05 |
|  Jon Hermansen changed their display name from jonhermansen to Jon Hermansen. | 19:18:50 |
| 24 May 2026 |
|  maurice joined the room. | 18:20:21 |
| 26 May 2026 |
|  phanirithvij changed their display name from loudgolem to phanirithvij. | 11:42:05 |
| 27 May 2026 |
|  Carsten Kragelund Jørgensen joined the room. | 21:03:27 |
| Carsten Kragelund Jørgensen | Is there a preferred way to get bulk data from hydra? I'm looking to build out a dataset of build failures, but don't want to be rude and just have a script running 24/7 downloading individual build results. | 21:34:02 |
