NOTICE: This library is no longer being developed. Use Ensaio instead (https://www.fatiando.org/ensaio). -- Download geophysical models/datasets and load them in Python
BSD 3-Clause "New" or "Revised" License
34
stars
15
forks
source link
Avoid CIs from downloading large amount of data #77
CIs now download all files in registry while running tests and building the gallery.
After new datasets will be included into Rockhound, the amount of data needed to be fetched may grow too large that CIs may be not be capable of finishing the testing builds.
Because there's no way to permanently store this datasets on the CIs, we decided to remove test and gallery builds from being run on by the CIs. Instead, the maintainers should run the tests and build the gallery locally before each PR is merged into master. Test functions and gallery examples must still be included on every new PR (and 100% coverage is still a goal to achieve), but the difference is that CIs won't run them.
All files inside doc/gallery should be pushed to the repository so CIs can still build the docs (and deploy them) but avoiding to rerun the gallery examples.
A new minimal test function should be added that only checks if all files in the registry are available for download.
Add an extra point to PR checklist to remind contributors to build the gallery example and push any change on doc/gallery, and maintainers to run all tests before merging the PR.
Are you willing to help implement and maintain this feature? Yes
Description of the desired feature
CIs now download all files in registry while running tests and building the gallery.
After new datasets will be included into Rockhound, the amount of data needed to be fetched may grow too large that CIs may be not be capable of finishing the testing builds. Because there's no way to permanently store this datasets on the CIs, we decided to remove test and gallery builds from being run on by the CIs. Instead, the maintainers should run the tests and build the gallery locally before each PR is merged into
master
. Test functions and gallery examples must still be included on every new PR (and 100% coverage is still a goal to achieve), but the difference is that CIs won't run them. All files insidedoc/gallery
should be pushed to the repository so CIs can still build the docs (and deploy them) but avoiding to rerun the gallery examples. A new minimal test function should be added that only checks if all files in the registry are available for download. Add an extra point to PR checklist to remind contributors to build the gallery example and push any change ondoc/gallery
, and maintainers to run all tests before merging the PR.Are you willing to help implement and maintain this feature? Yes