edited test_wilcoxon check to ignore minor differences in conf.level#172
Merged
edited test_wilcoxon check to ignore minor differences in conf.level#172
Conversation
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
2 participants
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.
@adw96 The issue is coming from the
test_wilcoxon.Rfile, where I believe after an R-devel update, the actual achieved confidence level up to 4 decimal points is being reported, causing it to be "different" than 0.95. I tried fixing it by just forcingexpect_equalto ignore the attributeconf.level.I would love your guidance as to how to see if this fixes all the CRAN check errors. I know win-builder is an option, but haven't tried it before.