| 6 Mar 2025 |
 K900 | That's basically free | 19:57:11 |
 polygon_ | Do I just use the Hydra links (e.g. https://hydra.nixos.org/build/291787217/nixlog/1/raw ) or something else? | 19:58:36 |
| polygon_ | Basically got a list of build IDs | 19:58:45 |
| K900 | Those Hydra links redirect to https://cache.nixos.org/log/3ipspns3k0gk8v9yp775w0blg8l6mm5w-clasp-2.6.0.drv | 19:59:07 |
| K900 | That last part is just the drv name | 19:59:20 |
| K900 | Or do you not have those? | 19:59:28 |
| polygon_ | I do not think so, is the redirect expensive on Hydra? I just have everything that is in the list of failed builds. | 19:59:53 |
| K900 | Expensive-ish | 20:00:07 |
| K900 | If you have the attrnames, just run an eval locally | 20:00:19 |
| K900 | And cross-reference | 20:00:24 |
| K900 | A full nixpkgs eval takes 10-15 minutes and is notably free for Hydra | 20:00:54 |
 ghpzin | I assumed it would use json api endpoints for that, assuming you still crawl every build by id after pulling list from eval. | 20:01:57 |
 das_j | Let me check | 20:02:36 |
| ghpzin | * I assumed it would use json api endpoints for that, assuming you still crawl every build by id after pulling list from eval.
https://github.com/NixOS/hydra/blob/master/doc/manual/src/api.md | 20:02:47 |
| das_j | given a build ID, I can give you lines in the form of auctex.aarch64-darwin 212687937 auctex-12.3 aarch64-darwin Failed. Would that be helpful? | 20:03:11 |
| das_j | Redacted or Malformed Event | 20:03:22 |
| polygon_ | I would need a mapping to the store path, then I can get them from S3 directly | 20:03:42 |
