The workflow for the pysat RC tests in Github Actions needs to be updated for usage with with new pyproject / coveralls standards. Adds directly to guvi pull since it will be needed there.
Type of change
Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
running the action manually.
Test Configuration:
github actions
Checklist:
[ ] Make sure you are merging into the develop (not main) branch
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] Add a note to CHANGELOG.md, summarizing the changes
[x] Update zenodo.json file for new code contributors
The pysat RC tests are failing here when they get to the timed guvi data, as on my local machine. Adding these to the other branch should also fail, but at least complete the run
Description
The workflow for the pysat RC tests in Github Actions needs to be updated for usage with with new pyproject / coveralls standards. Adds directly to guvi pull since it will be needed there.
Type of change
How Has This Been Tested?
running the action manually.
Test Configuration: github actions
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 wiki: https://github.com/pysat/pysat/wiki/Checklist-for-Release