Update GMT Dev Tests workflow to test on macOS-12 and ubuntu-22.04

[weiji14]

Description of proposed changes

Look GitHub Actions has some public beta runners available:

• macOS-12.0 (Monterey) as of 27 Apr 2022 (macOS 12 (Monterey) is available as a public beta in GitHub Actions and Azure DevOps actions/runner-images#5446)
• ubuntu-22.04 (Jammy Jellyfish) as of 5 May 2022 ((Public Beta) Ubuntu 22.04 is now available actions/runner-images#5490)

So let's test it out on the GMT Dev Tests workflow!

Also updating the cron tab to run GMT Dev Tests on Monday/Wednesday/Friday only. A bit annoying to have the tests failing everyday, especially during the weekend. See also #1833 (comment) about having less frequent tests. Edit: cherry-picked this to #1922

Supersedes #1105.

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[seisman]

It seems that the macOS-12.0 agent doesn't respond:
https://github.com/GenericMappingTools/pygmt/runs/6315841035?check_suite_focus=true

[weiji14]

Interesting. I saw that the macos-12.0 didn't repond either when in PR at google/santa#798, but their macos-12.0 CI worked in the main branch after merging. Maybe one of those permissions thing again. Do you think we shoud just merge and see?

[seisman]

Interesting. I saw that the macos-12.0 didn't repond either when in PR at google/santa#798, but their macos-12.0 CI worked in the main branch after merging. Maybe one of those permissions thing again. Do you think we shoud just merge and see?

I've applied your changes to the main branch of my own fork (https://github.com/seisman/pygmt). The macOS-12.0 runner still doesn't respond (https://github.com/seisman/pygmt/runs/6332825323?check_suite_focus=true).

[weiji14]

Ok, let's wait until next week and try again.

[seisman]

Perhaps we can pick the commits fdd64ac and 6b9c5ab into #1833, so that we run full tests 3 times a week, then #1833 may be OK to merge?

[weiji14]

Perhaps we can pick the commits fdd64ac and 6b9c5ab into #1833, so that we run full tests 3 times a week, then #1833 may be OK to merge?

I've cherry-picked the Mon/Wed/Fri crontab to #1922. Would prefer the full tests in #1833 to run on a less frequent schedule, but let's discuss that in #1833.

[weiji14]

Testing on Ubuntu 22.04 (Jammy Jellyfish) at https://github.com/GenericMappingTools/pygmt/runs/6389148872?check_suite_focus=true, seems to be running. The macOS-12.0 still seems stuck though.

[weiji14]

The macos-12 runners should be generally available now, see https://github.blog/changelog/2022-06-13-github-actions-macos-12-for-github-hosted-runners-is-now-generally-available/

[weiji14]

@seisman, seems to be working now (see https://github.com/GenericMappingTools/pygmt/runs/6886313572?check_suite_focus=true). Just realized at #1918 (comment) that it was a typo 😅 Should be macos-12, not macos-12.0 🤷