| 24 Feb 2025 |
 shawn8901 | Okay, its locatable to the latest hydra bump, when I revert it, it's working again fine.
Should I create an issue in nixpks or more on hydras github? | 20:18:34 |
| 25 Feb 2025 |
 hacker1024 | There are only two places where nix-eval-jobs uses stoi. Have you set evaluator_workers or evaluator_max_memory_size in your Hydra configuration? | 02:14:18 |
| shawn8901 | In reply to @hacker1024:matrix.org
There are only two places where nix-eval-jobs uses stoi. Have you set evaluator_workers or evaluator_max_memory_size in your Hydra configuration? Yeah, I am limiting that. So stoi = out of memory? | 06:25:39 |
| hacker1024 | No, stoi is a function that parses an integer. What is the exact contents of that part of your config? | 06:26:39 |
| shawn8901 | evaluator_max_memory_size = ${toString (4 * 1024 * 1024 * 1024)} which was totally fine previously | 06:27:35 |
| shawn8901 | And I am setting evaluator_workers = 2 | 06:28:15 |
| hacker1024 | Hmm yeah that does seem fine | 06:28:30 |
| hacker1024 | Still maybe try without it for a bit and see if that helps? | 06:28:42 |
| hacker1024 | Wait that size is in mb though? You're allocating 4EB | 06:29:20 |
| hacker1024 | * Wait that size is in mb though? You're allocating 4PB | 06:29:39 |
| hacker1024 | That's also 2x the signed integer limit | 06:30:53 |
| 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 |
