-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error reports returned as :cause string in an exception when produced by instrumentation within generative testing #160
Comments
@WhittlesJr Thanks for reporting this. I agree this is not great, but I'll have to think a bit about how to resolve. Just for posterity (mostly for future self, so I don't forget my context), here is my sense of what's going on:
I'm not immediately clear to me what to do here. I suppose the best thing would be to write an exception printer similar to what Clojure does in the REPL? I would need to think about how to best format this so it's clear that the exception is connected to the test failure. I also want to ensure this works with:
|
Oh, if it matters, I'll add that this was run with kaocha from the command line (no REPL involved, but probably it doesn't make a difference). |
Hey @bhb, this is the solution needed for absolutely free generative testing! Looks like this issue still happens even under kaocha's new spec-test-check feature, but the repro for this issue can be reduced to :
And then run:
|
I’m wondering if maybe I’ve run into the same problem, or a variant of it. I’m using Kaocha and Expound. My
|
Quick follow-up, I’ve found a possible clue as to what’s been happening in my project: I’d wanted to use I just discovered that switching those I don’t know why/how exactly, but it seems maybe there’s some issue with the combination of providing an expound printer to clojure.spec and then calling |
@aviflax Thanks for the info! I appreciate it. I'm super busy right now, but as soon as I get some cycles, I'll dig into this a bit more and see if I can isolate it. |
Yup, I’ll give those a try tomorrow. Thanks! |
Yup, 391e45f seems to have resolved the problem. Thank you! I can use this version of the code for now; using gitlibs via tools.deps is my normal modus operandi so it’s really no big deal. That said, it’s one more thing I have to document and explain in the Thanks Ben! |
@aviflax Sorry for the delayed reply, but this was fixed in 0.8.5 |
No worries — thanks for letting me know! |
My far-from-minimal reproduction:
Yields:
The text was updated successfully, but these errors were encountered: