test-check

mattly 2016-11-08T20:18:38.000117Z

is there any way to tell test.check to give up and just show me the smallest failing result so far after a certain number of iterations?

mattly 2016-11-08T20:18:57.000118Z

I've got one failure that I'm having a really hard time tracking down, but it'll run for 100k iterations without settling

2016-11-08T21:29:18.000119Z

@mattly there are a couple tickets surrounding that

2016-11-08T21:30:10.000120Z

@mattly there is also a callback function you can register on the master branch, that would let you "listen" for things as it's shrinking

2016-11-08T21:31:14.000121Z

there's a ticket for a max-shrink-time option, and for capturing C-c interruptions and returning the smallest value so far

2016-11-08T21:31:34.000122Z

I think the latter one is hairy though so I don't know if it will get implemented :/

2016-11-08T21:32:35.000123Z

C-c would probably be the most useful, so if it turns out to be straightforward I would love to add it

2016-11-08T21:33:22.000124Z

if it's hairy it's probably because of varying details in different repls vs. unix signals when running test processes and that sort of thing

mattly 2016-11-08T21:51:38.000125Z

oh fun