Continue on fail when max_fail is gt 0#332
Merged
jmid merged 4 commits intoc-cube:mainfrom Mar 5, 2025
Merged
Conversation
Collaborator
|
Thanks a bunch for digging into this issue and suggesting a fix 🙏 🙂 I've added a couple of tests, filed updated expect test outputs for 32+64 bit builds, and added a CHANGELOG entry. |
Contributor
Author
|
Thanks for adding tests! All seems good to me. |
Collaborator
|
Cool, thanks again 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think I ran into #182, where I want to set
max_failto be some value greater than 1.In my limited sleuthing, I believe the check could have been accidentally removed in 3a9bf2e#diff-07dbdff6f84a44f565ad4871c5790ad598ceda123f0b8190a711d303d3be28efR1718-R1720 (Hmm, it's highlighted in the link, but it doesn't automatically go to the corresponding line number which is 1767 in file
src/core/QCheck2.ml). Here, it use to be that if some small parameter andstate.cur_max_fail > 0, then it would continue otherwise yield. I've just added that latter back in. In the current codebase, it doesn't seem likecur_max_faildoes anything(4 matches for searching this keyword).Besides just running this locally and seeing that in my example I can report multiple failures in the failure column, I haven't looked into how to test this. I also haven't confirmed is this actually solves #182 other than seeing that the suspected commit was in April 2021 and the issue was filed in September 2021