!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

481 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.149 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
19 Jun 2026
@hexa:lossy.networkhexawhenever it runs again it will retry applying it14:44:34
@hexa:lossy.networkhexathe merge queue will block dns changes until gandi gets that fixed14:44:52
@hexa:lossy.networkhexa
Download
14:45:38
@hexa:lossy.networkhexano outage for iocaine customers 😉14:45:46
@hexa:lossy.networkhexaand tagging bots for the maze is working14:46:06
@joerg:thalheim.ioMic92So my plan is to quickly test the build-support code in staging and than do a deployment of hydra + builder again14:48:09
@hexa:lossy.networkhexaok14:48:27
@joerg:thalheim.ioMic92I had now for a couple of hour staging running and restarted builders to see if they leave builds behind in the db14:48:28
@dramforever:matrix.orgdramforeveri checked the "preliminary list" on the github issue and it looks like neither TUNA nor ISCAS has grabbed any of the wrong store paths. it seems that none of the new? store paths have made it to a channel bump?14:55:12
@joerg:thalheim.ioMic92Okay nixos-manual rebuilds correctly from the binary cache14:55:13
@dramforever:matrix.orgdramforeverknocking on wood but if so that would be a relief14:55:36
@joerg:thalheim.ioMic92Okay, I didn't finished the parquet file fetch yet.14:56:08
@dramforever:matrix.orgdramforeveryeah but i need to sleep 🥲14:56:29
@joerg:thalheim.ioMic92* Okay nixos-manual hydra product rebuilds correctly from the binary cache14:57:25
@joerg:thalheim.ioMic92 hexa (signing key rotation when): I will now go ahead and first all builder and than hydra 14:57:56
@dramforever:matrix.orgdramforever("we" don't re-download paths that already have a narinfo, so if none of the store paths have made it into the closure of a new store-paths.xz, then all we need to do after is restart and go back to normal polling)14:59:08
@joerg:thalheim.ioMic92That's the only one I knew that was new: /nix/store/lq8laawx5ii4jrs3rcvyjya3gvk5d6lq-ruby3.4-serverengine-2.4.0 but I think I deleted it from the binary cache before any channel bump15:02:25
@dramforever:matrix.orgdramforever yes, that and /nix/store/9wzl5nkynf6727nabm2kjq523a57qyin-gst-libav-1.26.11 15:03:18
@dramforever:matrix.orgdramforeverafaict. neither of which has been pulled to TUNA/ISCAS yet15:03:41
@dramforever:matrix.orgdramforeveras i would expect if the channels have not bumped to include them yet15:04:42
@dramforever:matrix.orgdramforeverso, good sign15:04:49
@mightyiam:matrix.orgShahar "Dawn" Or joined the room.15:05:33
@joerg:thalheim.ioMic92If someone has some spare cycles going over store-paths.xz would be a different way to vet the cache15:06:02
@dramforever:matrix.orgdramforever 🥲 we would have been doing that if i hadn't got lazy 6.5 years ago and skipped on checking FileHash 15:08:09
@joerg:thalheim.ioMic92Maybe also should do a GC on all builders before taking them back online?15:26:09
@hexa:lossy.networkhexalooks like we're back up15:56:03
@mightyiam:matrix.orgShahar "Dawn" OrThank you for bringing it back up so quickly 🙏16:05:14
@joerg:thalheim.ioMic92I think I was able to observe this now. Apparently if a multi-part complete request returns an error, one has to check if the object was created successfully. Our retry code was just retrying on already invalidated part ids.16:29:27
@joerg:thalheim.ioMic92New version is deployed16:29:39
@joerg:thalheim.ioMic92Looks like hydra's disk no longer get trashed with nars... good so far. However NAR streaming is still quiet heavy and blocks the queue-runner async code a bit, so I should get this out of the event loop. My first attempt will be switching to ls files since the vast majority of uncached nars won't have any hydra build productions.17:03:03

Show newer messages


Back to Room ListRoom Version: 6