CI: Pin GMT to a specific build on RTD #2684
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
The ReadTheDocs build started to fail recently. For example, in #2678, build https://readthedocs.org/projects/pygmt-dev/builds/21875786/ succeed but the next build https://readthedocs.org/projects/pygmt-dev/builds/21881327/ failed with the following errors:
Comparing these two builds:
The main difference is libabseil (20230125.3->20230802.0), which is likely due to the ongoing conda-forge migration https://conda-forge.org/status/#libabseil20230802_libgrpc157_libprotobuf4234.
For unknown reasons, the ReadTheDocs CI is using gmt-6.4.0_hf1dbac9_15 (the latest build) while the Docs workflow is using gmt-6.4.0_h4733502_10, which still works. Thus, in this PR, we can temporarily pin GMT to the specific build
h4733502_10
to make the RTD CI work again.