| 25 Feb 2025 |
 shawn8901 | Is it? It should be 4g, at least that was where it limited before | 06:31:04 |
| shawn8901 | Yeah maybe that is then where it's choking | 06:31:31 |
| shawn8901 | I'll try it out when I am back at home, I just did not expect to break in such a way between a bump of Less then 2 weeks 😅 | 06:32:14 |
 hacker1024 | The unit is definitely mb now, and I'm pretty sure it always has been 👀
https://github.com/nix-community/nix-eval-jobs/blob/4b392b284877d203ae262e16af269f702df036bc/src/eval-args.cc#L59 | 06:32:31 |
| hacker1024 | So you'd just want 4096 | 06:32:41 |
| 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 |
