| 19 Feb 2026 |
 woobilicious | Never used it before, so can't comment on it, wouldn't we want to just disable tests instead? | 04:43:53 |
| woobilicious | wait hold up we have a newer verision but its called sbv_12 hmm | 04:50:17 |
| woobilicious | but that is also marked as broken lol | 04:52:16 |
| woobilicious | note the only suppposed working version on hackage is v13.5 | 04:53:04 |
| woobilicious | well, looks like the reason why our version is 11.7 is that that is what stackage lts uses. | 05:22:52 |
| woobilicious | peddie: you might be right there, we don't mark it dontCheck by the looks. checks are also extremely slow. I've disabled now because I'm impatient lol | 05:33:03 |
 peddie | I looked at it a couple times and it was always only that issue, and I don't think Levent has a lot of time to support "unusual" platforms like nixpkgs :) | 05:34:34 |
| peddie | I guess one option would be to patch the golden test files when we build! | 05:36:52 |
| woobilicious | I guess we could fix it for him, or just disable tests. | 05:37:46 |
| peddie | well the tests compare exact string equality with the golden output files. IIRC the ones it ships with just contain the SMT solver name, like z3 or cvc5, but when we run tests in nixpkgs we get the full path /nix/store/blahblahblah/bin/z3, so they fail. but it doesn't make any sense to insert any full path upstream | 05:39:05 |
| woobilicious | I mean the test itself shouldn't care about fullpath v not, so there must be some way to fix this false negative without a "hacky" solution like inserting hard coded paths. | 05:44:45 |
| peddie | yes, this is really a spurious failure. we could just mask out the initial line that contains the solver name from both the output and the reference file, or something like that | 05:45:29 |
| woobilicious | do we have a link to the failing test? I assume it's on hydra somewhere | 05:46:01 |
| woobilicious | lol, why is hydra's UI so confusing, do periods break hydra search? wtf | 05:51:57 |
| woobilicious | Ahh it hasn't been tested since v10.9 in 2023 | 05:59:01 |
| woobilicious | Okay fixed: https://github.com/LeventErkok/sbv/pull/772 | 06:56:25 |
| peddie | the hero we don't deserve! nice one! | 07:09:40 |
| woobilicious | yeah was easy find :D | 07:09:51 |
| woobilicious | I also like feeling productive instead of wasting time on the actual code I was gonna write lol | 07:10:19 |
|  catsarecute joined the room. | 19:05:45 |
 alexfmpe | https://github.com/cdepillabout/nix-haskell-updates-status is nearly a month outdated, is that expected? | 22:27:45 |
|  -> @n:rab.lol left the room. | 22:43:10 |
 maralorn | Nope, that is a known problem caused by an eval error. | 22:51:54 |
| woobilicious | The failing tests on sbv go deeper, than just the fix I made, we should probably just disable tests | 22:58:36 |
| woobilicious | Is there a logic to the configuration-common.nix file order? | 23:09:56 |
| woobilicious | I'll add the changes and open a PR against the haskell-updates branch. | 23:17:32 |
| alexfmpe | roughly grouping related things lots of conflict-avoidance by not adding stuff at the end I guess | 23:21:23 |
| alexfmpe | I do wonder if it shouldn't just be alphabetized and when we apply the same fix to several things, float it to a let at the start | 23:22:20 |
| woobilicious | Oh I think I found the "general" section | 23:23:20 |
| alexfmpe | we have one? | 23:23:28 |
