| 23 May 2024 |
 cole-h | (Not much is ~500GiB, fwiw, so not "too little" either) | 18:19:26 |
 hexa | I thin not, in that I had to fiddle with the ttl in nix | 18:25:25 |
| hexa | because nix is not kind about failed substitution | 18:25:34 |
| hexa | narinfo-cache-positive-ttl = 3600;
| 18:26:09 |
| hexa | with gc.automatic enabled and no further tuning | 18:26:28 |
| cole-h | Then a follow up: is there something harmonia does better than attic? | 18:26:55 |
| hexa | the default is like a month | 18:26:59 |
| hexa | serves directly from the /nix/store, no central binary store required | 18:27:17 |
| hexa | attic with a small binary cache and aggressive gcing would work as well | 18:28:39 |
 ris_ | ahem https://github.com/risicle/nix-heuristic-gc | 20:25:16 |
| ris_ | i actually originally built that with the intention to use it on a binary cache | 20:27:20 |
| 24 May 2024 |
 trofi | I keep finding huge amount of accidental $foo.tests eval failures. An example fix is https://github.com/NixOS/nixpkgs/pull/314109. Looking at https://github.com/NixOS/nixpkgs/runs/24606477687 ofborg shown it as green while it said explicitly it fails to evaluate: The following builds were skipped because they don't evaluate on x86_64-linux: githooks.passthru.tests. Shouldn't it be at least gray in the UI? I vaguely remember it doing that in the past. | 06:08:11 |
 7c6f434c | Tests failing to evaluate is usually having no tests specified. A majority of packages failing to evaluate is something not being in the platforms. | 06:13:50 |
| 7c6f434c | Distinguishing the cases is some non-trivial work, not just switching a single constant | 06:15:26 |
