| 20 Oct 2025 |
 Vladimír Čunát | Right now Hydra passed the point where it failed the last time. | 05:52:58 |
| Vladimír Čunát | It's Hydra's fourth attempt now. | 05:53:09 |
| Vladimír Čunát | So... I don't know. | 05:53:19 |
| Vladimír Čunát | But if it passes, I'd probably not block on it. | 05:53:44 |
| Vladimír Čunát | Ah, no. | 05:54:15 |
| Vladimír Čunát | It failed the same. | 05:54:20 |
| Vladimír Čunát | 🤔 weird. I don't get the logging. | 05:54:47 |
| Vladimír Čunát | I swear that I saw the Hydra's tail of the log that passed that point successfully. | 05:56:20 |
| Vladimír Čunát | But now it's shown as failed on that point again. | 05:56:32 |
| Vladimír Čunát | I wonder if it's not showing the log from the last failed attempt. | 05:57:09 |
| Vladimír Čunát | The same is shown by
nix log /nix/store/7g2rmbfwn0q0wa9wpn0phdjpaq6ndcnp-openssh-test-10.1p1.drv
| 05:57:50 |
| Vladimír Čunát | aah, on the central Hydra machine (mimas). | 05:58:38 |
| Vladimír Čunát | But if I run the same on the builder itself, I do see a newer log. | 05:58:56 |
| Vladimír Čunát | 🤔 maybe that's how Hydra behaves normally on failure retries? But it's annoying. | 06:00:49 |
| Vladimír Čunát | I think I've seen this test derivation fail in three places already. | 07:42:39 |
| Vladimír Čunát | This test has 5 .meta.maintainers 😏 | 08:12:43 |
| Vladimír Čunát | I'll open a GitHub issue with the logs attached. | 08:12:53 |
| Vladimír Čunát | https://github.com/NixOS/nixpkgs/issues/453782 | 08:49:09 |
| Vladimír Čunát | ooh, it fails also on x86_64-linux | 08:57:35 |
| Vladimír Čunát | I just confused opensshTest with nixosTests.openssh 😕 | 08:57:50 |
 K900 | Are those not the same thing | 08:58:40 |
| K900 | Oh it's openssh's own tests | 08:59:13 |
| Vladimír Čunát | The failure got triggered just by openssh update. Well, details on that issue. | 09:45:14 |
| Vladimír Čunát | BTW, I generally wonder why maintainers relevant to a PR/package so often don't finish their backports and just leave the backport PR hanging indefinitely. | 11:53:28 |
 ElvishJerricco | heh, this is kinda funky. I based my 258.1 branch on my staging-next fix yesterday since it reverts the commit. Now that that commit has gone staging-next -> staging, github still shows it as one of the commits for the 258.1 branch in the PR. Weird. | 12:10:30 |
| ElvishJerricco | ah, just pushing an update to the commit timestamps of the two new commits fixed that | 12:14:09 |
| Vladimír Čunát | Yes, you need to force-push via git or rebase in the UI or something to make it refresh the commit list. | 12:15:46 |
|  eveeifyeve joined the room. | 12:41:30 |
| eveeifyeve | does anyone know when the next merge of staging to staging next is? | 12:42:00 |
| Vladimír Čunát | I don't think so 😅 | 12:44:09 |
