Also note that there is a small test failure to do with a line change on test_call_module_error_message (See https://github.com/GenericMappingTools/pygmt/pull/668/checks?check_run_id=1298142572#step:10:454), only for the GMT master branch (i.e. GMT 6.2.0):

E               assert "Module 'info...ogus-data.bla" == "Module 'info...ogus-data.bla"
E                 - Module 'info' failed with status code 71:
E                 ?                                        ^
E                 + Module 'info' failed with status code 72:
E                 ?   

Also note that there is a small test failure to do with a line change on test_call_module_error_message.

Yes, please see this: GenericMappingTools/gmt#4347 (comment).

Although the test failure is caused by upstream change, but I think it's a bad test to check the undocumented status codes. We can see if we can improve the test.

E               assert "Module 'info...ogus-data.bla" == "Module 'info...ogus-data.bla"
E                 - Module 'info' failed with status code 71:
E                 ?                                        ^
E                 + Module 'info' failed with status code 72:
E                 ?  

Should we check that the status code is 71 for GMT<=6.1.1, and 72 for GMT>=6.2.0? It's really a bad idea to test against the undocumented status codes.

I would do something like assert "Module 'info' failed with status code" in ..., thus skipping the number check. Or we could do a regex-style check to handle any non-zero number.

Let's wait for more discussions in GenericMappingTools/gmt#4347.