-
Notifications
You must be signed in to change notification settings - Fork 224
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
Add a workflow and Makefile target to test old GMT versions every Tuesday #2079
Conversation
9f19869
to
8d3cf45
Compare
Co-authored-by: Max Jones <[email protected]>
Ping @weiji14 and @maxrjones for another round of review. |
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.
Some suggestions to run these tests on lower versions of Python and Operating Systems.
@@ -0,0 +1,105 @@ | |||
# This workflow installs PyGMT and runs tests with old GMT versions | |||
|
|||
name: GMT Backward Tests |
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.
Not so sure if 'backward' is a good word, how about 'legacy' (https://en.wikipedia.org/wiki/Legacy_system)? Maybe we need to ask a native English speaker 🙂
name: GMT Backward Tests | |
name: GMT Legacy Tests |
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.
Legacy sounds good and let's wait for some inputs for native English speakers.
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.
Done in be81f36
Co-authored-by: Wei Ji <[email protected]>
@@ -0,0 +1,105 @@ | |||
# This workflow installs PyGMT and runs tests with old GMT versions |
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.
Remember to rename the workflow file if we decide to call it "GMT Legacy Tests"
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.
Done in be81f36.
…sday (GenericMappingTools#2079) Co-authored-by: Max Jones <[email protected]> Co-authored-by: Wei Ji <[email protected]>
Description of proposed changes
To test PyGMT with old GMT versions, a new Makefile target and a new workflow are added in this PR.
Makefile target
test_no_images
Because the baseline images usually have slight changes for different GMT versions, it makes little sense to compare the baseline images generated by GMT 6.4 when running the tests with GMT 6.3. However, we still want to run these image-building tests to make sure they don't crash or raise errors. This is done by NOT adding the
--mpl
option to pytest.New workflow "GMT Backwards Tests"
This workflow is modified from the "GMT Dev Tests" workflow. It will run when a PR is marked ready for review and will run every Tuesday.
Fixes #1991.
Reminders
make format
andmake check
to make sure the code follows the style guide.doc/api/index.rst
.Slash Commands
You can write slash commands (
/command
) in the first line of a comment to performspecific operations. Supported slash commands are:
/format
: automatically format and lint the code/test-gmt-dev
: run full tests on the latest GMT development version