| 18 Mar 2026 |
| debtquity joined the room. | 21:56:55 |
| 19 Mar 2026 |
Vladimír Čunát | Hydra now shows lots of abortions from S3 uploads.
Aborted: [31;1merror:[0m … while uploading to S3 binary cache at '[35;1ms3://nix-cache[0m' [31;1merror:[0m unable to upload '[35;1mhttps://nix-cache.s3.us-east-1.amazonaws.com/nar/0fi6dj94id8fla40n3h98b9spmsbszl7i7k2bkpnjbqk9fcgyad8.nar.xz[0m': HTTP error [35;1m400[0m[35;1m[0m response body: [35;1m<?xml version="1.0" encoding="UTF-8"?> <Error><Code>RequestTimeout</Code><Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message><RequestId>2SDA6N47EBP0Y9TY</RequestId><HostId>DzalNia2QC6pPMWG4tSso2PO0E+w+ZmqUrCtA+oI2GP1hMZV3IVW5WibfNELfak4rQVKuh6OrCw=</HostId></Error>[0m
| 08:08:00 |
hexa | RequestTimeout
| 08:08:37 |
hexa | hydra surely retries uplodas, right? | 08:08:50 |
Vladimír Čunát | The Hydra jobs certainly remained failed/aborted until I restarted them manually. | 08:11:34 |
Sergei Zimmerman (xokdvium) | The queue runner is at 2.34 now? | 08:59:09 |
hexa | Hydra 0.1.20260316.a40d428 (using nix-2.34.1 and nix-eval-jobs-2.34.1)
| 09:03:48 |
hexa | Mar 17 16:25:15 mimas hydra-queue-runner[4333]: warning: error: unable to upload 'https://s3.us-east-1.amazonaws.com/nix-cache/yak3aj118k761cgsnc79k0wpk4y5598c.ls': Timeout was reached (28) Operation timed out after 15942 milliseconds with 0 bytes received; retrying in 287 ms
they started here | 09:04:57 |
hexa | and there have been ~17.8k of these since | 09:05:14 |
hexa | that coincides with https://github.com/NixOS/infra/pull/978 | 09:06:09 |
Vladimír Čunát | I've seen these abortions occasionally in the past few months. | 09:08:09 |
Vladimír Čunát | * I've seen these S3 abortions occasionally in the past few months. | 09:08:19 |