Closed geekosaur closed 1 month ago
Confirmed: changing our tasty
constraint from <1.6
to <1.5.1
our tests build. Shouldn't this kind of change not happen in minor releases?
Isn't this caused by tasty-quickcheck-0.11
, which is a major release?
You can probably replace Nothing
with QuickCheckReplayNone
and Just
with QuickCheckReplayLegacy
. Or put tasty-quickcheck < 0.11
if time is short.
...and then show (intSeed, replaySeed)
instead of show replay
.
It would be better to fix the root cause for Cabal's workaround by implementing https://github.com/UnkindPartition/tasty/issues/359#issuecomment-2048523531. Should be pretty straightforward.
We're trying to get a release out, so I'm pushing the constraint. I just got a successful validate run.
We've been using tasty 1.5, but 1.5.1 was just released today and now our CI gets:
While the errors involve QuickCheck, it hasn't changed recently, while the build log says
Test.Tasty.Providers
did change and forced the rebuild.