| 20 Jun 2026 |
 dramforever | okay, going through the keys list, it looks like we haven't grabbed many zstd compressed paths anyway, only ~100, which we'll just delete and redo next time and it should be all good | 14:46:28 |
 Sergei Zimmerman (xokdvium) | Some cursed build failure: https://hydra.nixos.org/build/331701865/nixlog/1
Doesn’t seem like a nix build issue, since other platforms are fine. Will try to take a look later | 18:26:11 |
 hexa | yeah, that's some early gc | 18:27:20 |
| hexa | was fixed in the last deploy | 18:27:24 |
| Sergei Zimmerman (xokdvium) | Thanks. Will kick it then | 18:27:59 |
| hexa | https://github.com/NixOS/hydra/commit/09ee2bd5d39f49b8238e7b204d5e2e1c56808bc3 | 18:28:22 |
| dramforever | good ol' gc race | 18:36:41 |
| dramforever | oh already fixed? nice | 18:37:23 |
| hexa | 
Download | 22:41:36 |
| hexa | I'm sure the number will go down quickly, but | 22:41:42 |
| hexa | new eval and now all older evals have gained the 250k queued jobs, too??? | 22:42:07 |
| hexa | is that the weird | 22:44:49 |
| hexa | Redacted or Malformed Event | 22:44:58 |
| hexa |
fetchurl: add TeX historic archive mirrors
| 22:45:03 |
| hexa | oh well, the eval also took suspiciously long | 22:46:30 |
| hexa |
2026-06-20 23:53:46 (took 2 hours, 15 minutes, 2 seconds)
| 22:46:33 |
| hexa | when the previous one took 23 minutes | 22:46:38 |
| hexa | did it do stupid things? | 22:46:47 |
| hexa | 
Download | 22:48:20 |
| hexa | looks like it is now realizing it has already built those jobs | 22:48:30 |
| hexa | peaks at 149 steps/min | 22:49:09 |
| hexa | which would be a whopping 216k steps/day … bonkers | 22:49:25 |
| hexa | Redacted or Malformed Event | 22:49:43 |
| hexa | does that mean it needs a day to check the validity of these jobs? 🤔 | 22:50:35 |
| hexa | that would be pretty bad | 22:50:40 |
| hexa | 
Download | 22:55:58 |
| hexa | that was the "before" picture | 22:56:03 |
| hexa | so it also restarted failed builds? | 22:56:40 |
| 21 Jun 2026 |
 Mic92 | I actually thought I made that part faster, because before it was doing S3 checks for every store path and than I added an DB Check to make it faster. But I never compared it with what the old scheduler was doing. | 03:27:11 |
 K900 | https://grafana.nixos.org/goto/ffptmam7o9a80c?orgId=1 | 16:48:31 |
