| 16 May 2026 |
 vcunat | * With a good GC strategy for S3 that might not be a problem (in future). | 13:54:09 |
 emily | yeah.... mostly I'm just sceptical that non-blocking tests get much consumption from Hydra anyway. package bumps, spot-checking if functionality is working, people including them in their configs for bonus assurance - Hydra building them is pretty extraneous | 13:57:01 |
| emily | the main case I can imagine them providing value is notification when they break. but uh, haven't seen much evidence that any maintainer is proactively checking when their stuff breaks, so probably a bigger deal to establish that norm for packages first. and anyone going to the trouble of setting up a notification system can probably spare the cycles to build the test | 13:58:16 |
| vcunat | A nice way to follow failures for particular jobs (packages/tests) would be a useful improvement, though that's tangential here. | 14:02:06 |
| emily | yeah, I agree. I'm very much in favour of better notifications and delegating work to maintainers | 14:04:50 |
| emily | but I'm guessing that even adding "every test anyone active is interested in following" back in would be relatively little 😅 | 14:05:12 |
| emily | I mean, it would be really nice if we could cut staging-nixos out of the process again. | 14:06:00 |
| vcunat | Oh right, I didn't realize that implication. | 14:24:31 |
| 17 May 2026 |
 Mic92 | we can move those here: https://github.com/NixOS/images | 06:05:12 |
| Mic92 | and not have them build at all by hydra | 06:05:24 |
| Mic92 | in the nix repo we already have some oidc set up to authenticate against s3 | 06:05:42 |
| Mic92 | * in the nix repo we already have some oidc set up to authenticate against s3 without having any secrets in the repo. | 06:06:21 |
| vcunat | These are specific images for individual VM tests, I think, not the ISO and stuff that you think. | 06:37:12 |
|  Tomas Rivera joined the room. | 12:30:47 |
 sinan | cache.nixos.org down ?
this is from hetzner, https://termbin.com/6kho | 17:22:09 |
| sinan |
curl -I -6 https://cache.nixos.org/
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to cache.nixos.org port 443 after 0 ms: Could not connect to server
Exit: 0
| 17:22:37 |
 Bart | bart@bart-pc ~ $ curl -I -6 https://cache.nixos.org/
HTTP/2 200
| 17:22:46 |
 hexa (signing key rotation when) | hetzner where | 17:23:11 |
| hexa (signing key rotation when) | and in general, no. the cache is never down. | 17:23:43 |
| hexa (signing key rotation when) | unless us-east1 busn | 17:23:51 |
| hexa (signing key rotation when) | Redacted or Malformed Event | 17:23:54 |
| sinan | geoiplookup 5.9.149.12
GeoIP Country Edition: DE, Germany
GeoIP City Edition, Rev 1: DE, SN, N/A, Falkenstein, 08223, 50.477699, 12.364900, 0, 0
GeoIP ASNum Edition: AS24940 Hetzner Online GmbH | 17:24:13 |
| hexa (signing key rotation when) | can't repro from falkenstein pop | 17:25:06 |
| sinan | yeah i just installed nixos on another Falkenstein node, but it was in a diffrent data center | 17:26:52 |
| hexa (signing key rotation when) | then that sounds like an issue with hetzner itself | 17:29:09 |
| sinan | Oo, i'll reach out to hetzner | 17:31:49 |
| sinan | another node has been hit | 17:46:09 |
| sinan | another node has been hit | 17:46:52 |
| hexa (signing key rotation when) | Hm? | 18:02:07 |
| sinan | i checked cache.nixos.org becase nixos-anywhere was lagging during substitution
just noticed it was substituting from my local machine not cache.nixos.org, and my isp has shitty peering with hetzner
so i routed it through my homeserver and everything went smoothly
all good 👍️ | 18:29:27 |
