Fix integration test failure #101
Merged
Conversation
This file contains 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
The integration test compares floating numbers directly, it failed due to numpy precision change (numpy/numpy#18371) This commit fixed the issue by adding pytest.approx.
milah
approved these changes
Feb 12, 2021
pinaraws
approved these changes
Feb 12, 2021
Satish615
approved these changes
Feb 12, 2021
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.
Issue #, if available:
The integration test is comparing floating numbers directly, it failed due to numpy precision change (numpy/numpy#18371)
I reproduced the issue on an AWS EC2 host, by
Description of changes:
This commit fixes the issue by adding pytest.approx.
devtool allpasseddevtool integ_testspassedBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.