| 25 Feb 2025 |
 shawn8901 | Hum, the. Old hydra did not cry about it | 06:32:56 |
| shawn8901 | The value is unchanged for 8month in my config | 06:33:27 |
| shawn8901 | I'll check that out and report later, thank you very much for your help! | 06:33:49 |
 hacker1024 | No problem | 06:33:56 |
| shawn8901 | Okay I guess I found where my initial confused comes from. There are old log outputs, where those has been printed out in bytes, and few years ago evaluator max heap size on hydra was also set in bytes (as the envvar that was passed did understand that), and I just blindly assumed that it's just then bytes 🫣 old hydra then possibly did just use the default (which is also 4g) and that's likely why it matched my observations | 06:54:43 |
| 26 Feb 2025 |
| shawn8901 | It was that issue at the end. New version works fine now. 🎉 | 04:49:57 |
| 27 Feb 2025 |
|  @adam:robins.wtf joined the room. | 14:02:49 |
| 3 Mar 2025 |
 John Ericson | hexa: https://github.com/NixOS/hydra/pull/1451 put up a revert of that issue | 15:13:42 |
| John Ericson | until I have time to fix it properly | 15:13:48 |
| 6 Mar 2025 |
 polygon_ | Hello, is there a way to get lists (newly failing jobs, still failing jobs) as JSON or another easily machine readable format? E.g. https://hydra.nixos.org/eval/1810654?full=1#tabs-now-fail | 18:09:04 |
 K900 | No | 18:10:55 |
 @janne.hess:helsinki-systems.de | In reply to @k900:0upti.me
No Actually I crawl them for zh.fail and parse the HTML. Maybe I can just serve the cache files with nginx 🤔 | 19:25:49 |
| polygon_ | Do you happen to also crawl the logs? I noticed that quite some packages failed (and less popular ones still do) after moving to GCC14 due to some warnings that got turned to errors. I compiled a list of packages that failed in the first eval after the GCC change and a current eval. Identified 400 packages that failed first then and still fail now. Would the Hydra people be unhappy if I pulled all the logs for that, the ones caused by these warnings should be easily identifiable. | 19:56:25 |
| K900 | Logs are available on the S3 | 19:56:59 |
| K900 | You can pull from there | 19:57:02 |
| 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 (moved to @ghpzin:envs.net) | 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 |
| @janne.hess:helsinki-systems.de | Let me check | 20:02:36 |
| ghpzin (moved to @ghpzin:envs.net) | * 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 |
| @janne.hess:helsinki-systems.de | 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 |
