-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test case for IWater and PWater subroutines #151
Conversation
5d25f95
to
e61a817
Compare
Request review from @PaulDudaRESPEC and @rburghol |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing all this @austinorr ! One request though, we've been trying to channel all the PRs into the develop branch instead of the main, so that we can move all the enhancements together into main at once when we're ready for a new release. I know you have a lot of expertise in this area... Is that OK with you as a standard operating procedure?
@PaulDudaRESPEC yep, that sounds fine. Is that the long-term branch management pattern that this project intends to use, or is this just temporary while we manage the current push of changes? |
e61a817
to
912b771
Compare
912b771
to
1decc4f
Compare
@PaulDudaRESPEC ok, rebased revisions on the develop branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @austinorr ! Yes, our intent was to direct all changes to the develop branch until ready for a new release -- I guess I should have mentioned it when we talked.
Revisions include:
jitclass(spec)
when we are spec'ing another jit class. To get past this barrier quickly I've just checked to see if we're running tests with the flag NUMBA_DISABLE_JIT=1. If set to one (jit disabled), we use the python class in the spec, if not we default to using the jitclass.pytest
andcoverage
like so:This shows the ~70% coverage for HSP2/IWater and HSP2/PWater modules.
We can also run the suite with the numba jit to ensure we didn't break anything.
Here we see the tests pass, but line coverage can't be measured since it's all been compiled.