skipping tests causing cran error, see comments in #205 #206
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 don’t like punting and just skipping the tests, but I don’t know where I’m going to find that special dataset that is not updated, doesn’t risk changing order, and has only NULL values for the first 1,000 rows for at least one field.
And for the second test, I don’t even know what it was testing. It’s also hard to reconstruct without any example. It looks a little familiar and I think we may have developed the example together. I don’t recall though.
The new pull request passes CRAN tests documented in #205