| 7 Oct 2025 |
 dramforever | and "i guess nothing to build" | 20:50:04 |
| dramforever | it's like { } | 20:50:18 |
 fzakaria | empty attrs build ? | 20:50:36 |
| fzakaria | weird | 20:50:39 |
| fzakaria | feels like the output should always be derivation | 20:50:49 |
| fzakaria | Im surprised it even evaluated. | 20:50:59 |
| dramforever | it can be attrset of derivation | 20:51:00 |
| dramforever | try nix-build -E '{ inherit (import <nixpkgs> {}) hello coreutils; }' | 20:52:37 |
| dramforever | this gives you two | 20:52:42 |
| fzakaria | hmm; i wonder if i can set something to always expect 1 | 20:52:56 |
| fzakaria | so i can try this excercise again | 20:53:02 |
 lovesegfault | fzakaria: i'm running the parallel one, and then the stats look different | 20:53:26 |
| lovesegfault | Summary stats
=============
Fuzzers alive : 32
Dead or remote : 1 (excluded from stats)
Total run time : 6 days, 3 hours
Total execs : 8156 millions
Cumulative speed : 490855 execs/sec
Total average speed : 15339 execs/sec
Current average speed : 469074 execs/sec
Pending items : 0 faves, 0 total
Pending per fuzzer : 0 faves, 0 total (on average)
Coverage reached : 34.83%
Crashes saved : 12
Hangs saved : 7
Cycles without finds : 4/174/6/216/12/70/251/10/220/443/41/154/365/48/246/50/97/31/396/382/95/92/82/173/72/166/3/63/90/140/363/416/350
Time without finds : 1 minutes, 7 seconds
| 20:53:36 |
| lovesegfault | i'm at almost 35% coverage now that i added the dictionary, it's pretty cool | 20:54:09 |
| lovesegfault | okay, 2.32 is branched off, version has been bumped, can someone hit merge on https://github.com/NixOS/nix/pull/14147 for me now? | 21:07:29 |
| lovesegfault | * okay, 2.32 is branched off, version has been bumped, can someone hit merge on https://github.com/NixOS/nix/pull/14147 for me? | 21:07:34 |
 Sergei Zimmerman (xokdvium) | I really wish we could clean github actions before doing this | 21:07:59 |
| Sergei Zimmerman (xokdvium) | Now they are a total mess | 21:08:08 |
| Sergei Zimmerman (xokdvium) | Like vm tests should just be part of regular tests | 21:08:38 |
| lovesegfault | my hope is that change is just reverted after we're done churning this code | 21:08:45 |
| Sergei Zimmerman (xokdvium) | But also you are not running s3 tests in ci anyway? | 21:08:55 |
| Sergei Zimmerman (xokdvium) | I'd hope that it's not. We just should run vm/s3 tests all the time | 21:09:29 |
| lovesegfault | anyway, the main benefit is that in while we work on s3 you don't have to trust me that i tested that it still builds with s3 disabled or with the legacy s3 enabled :P | 21:10:51 |
| lovesegfault | the variant testing we can revert | 21:10:59 |
| Sergei Zimmerman (xokdvium) | I'm very much in favor of running tests/builds for s3 store. We just shouldn't have 2 new matrices for this and even more copy-pasta | 21:13:41 |
| Sergei Zimmerman (xokdvium) | If we could just add the vm tests to regular tests and add a new config to build with the new s3 that'd be great | 21:14:15 |
| Sergei Zimmerman (xokdvium) | Then we'd get the benefit of running vm tests with sanitizers as well | 21:14:49 |
| lovesegfault | 🫠| 21:14:53 |
| lovesegfault | i won't have time to do that for a while, and i'm spending too much time on this curl work as it is | 21:15:39 |
| Sergei Zimmerman (xokdvium) | Sure, I had a draft branch for the cleanup. I wasn't suggesting you needed to tackle that | 21:17:51 |
