Include expected warning text in @test_logs

[tsj5]

PULL REQUEST

Purpose and Content

Purpose

Change use of @test_logs to allow unit tests to pass when dependencies raise deprecation warnings. The writeup in issue #175 makes the case that the solution implemented here is the best way to deal with the case where the deprecation warning is raised in code we don't control.

Content

For all uses of @test_logs in unit tests,

1. add a filter to match the text of the expected warning message,
2. add match_mode=:any, to allow the test to pass when deprecation errors are raised.

Benefits and Risks

Benefits

Unit test suite now passes without needing to wait for the deprecations in Distributions.jl to be fixed in a new release;

Risks

If other, "serious" warnings are raised in addition to the warning being tested for, this implementation will give a false negative. As discussed in issue #175, as far as I know there's no way to optionally filter out deprecation warnings only.

Linked Issues

• Closes Make use of @test_logs less brittle #175

PR Checklist

• This PR has a corresponding issue OR is linked to an SDI.
• I have followed CliMA's codebase contribution and style guidelines OR N/A.
• I have followed CliMA's documentation policy.
• I have checked all issues and PRs and I certify that this PR does not duplicate an open PR.
• I linted my code on my local machine prior to submission OR N/A.
• Unit tests are included OR N/A.
• Code used in an integration test OR N/A.
• All tests ran successfully on my local machine OR N/A.
• All classes, modules, and function contain docstrings OR N/A.
• Documentation has been added/updated OR N/A.

[ilopezgp]

LGTM

[tsj5]

bors r+

[bors]

Build succeeded:

• docs-build
• format
• test_success