Set SYMPY_USE_CACHE environment variable to "no"
#684
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
Codecov Report
@@ Coverage Diff @@
## master #684 +/- ##
=======================================
Coverage 98.34% 98.34%
=======================================
Files 75 75
Lines 9163 9163
=======================================
Hits 9011 9011
Misses 152 152 Continue to review full report at Codecov.
|
josh146
approved these changes
Feb 25, 2022
Merged
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.
Context:
Quick fix for an issue with SymPy caching expressions and wrongly using a cached register reference instead of the new one. See issue #683 for details.
Description of the Change:
Sets the
SYMPY_USE_CACHEenvironment variable to "no" in CI, so that no caching is done when running tests.Benefits:
Certain cases when SymPy parameters are cached and incorrectly retrieved will (hopefully) no longer happen in the CI tests.
Possible Drawbacks:
This is just a quick fix for the CI tests. The issue is still present in the code-base.
Related GitHub Issues:
#683