MAINT: testing standards#130
Conversation
|
Test failure due to issue previously documents as #128. We could potentially put in a version limit (pysatNASA<=0.0.4) until the situation is sorted out. |
|
pysatNASA 0.0.5 is required to run on the operational system. As far as the version caps go, where do you want this to fail? |
| | ------------------ | ------------------ | | ||
| | numpy | pyForecastTools | | ||
| | pandas >= 1.4.0 | pysat >= 3.0.4 | | ||
| | requests | pysatNASA <= 0.0.4 | |
Co-authored-by: Angeline Burrell <aburrell@users.noreply.github.com>
|
OK, I have a local fix that will fix pysatNASA in the next release (pending another pull here). Options for the meantime are:
Preference? |
|
Let's go with: "Keep the version cap for now, and the operational version will just not run (old numpy incompatibility)" |
|
The local fix is up at #132, using the pysatNASA branch at pysat/pysatNASA#209 |
In which case, this is ready for review |
Description
Addresses #127, pysat roadmap
Updates pytest standards by removing
nosesyntax, which will be removed in a future version.Also updates the instrument test class usage, which will be updated in pysat 3.2.0.
The line "Updated tests to new pysat and pytest standards" in the changelog seems to describe these changes.
Type of change
How Has This Been Tested?
Via github actions and locally using pytest
Test Configuration:
Checklist:
develop(notmain) branchCHANGELOG.md, summarizing the changesIf this is a release PR, replace the first item of the above checklist with the
release checklist on the pysat wiki:
https://github.com/pysat/pysat/wiki/Checklist-for-Release