Update OS/BLAS test matrix workflow #1036
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slivingston
reviewed
Aug 8, 2024
control/tests/nyquist_test.py
Outdated
| assert issubclass(records[0].category, UserWarning) | ||
| assert "encirclements does not match" in str(records[0].message) | ||
| else: | ||
| pytest.fails("multiple warnings in nyquist_response (?)") |
There was a problem hiding this comment.
Suggested change
| pytest.fails("multiple warnings in nyquist_response (?)") | |
| pytest.fail("multiple warnings in nyquist_response (?)") |
https://docs.pytest.org/en/stable/reference/reference.html#pytest-fail
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the OS/BLAS test matrix workflow that is used to test releases against various combinations of operating systems and BLAS implementations. Changes:
nyquist_test.pyin which some calls with a manually specified frequency response would generate a user warning and others wouldn't. Both cases are not handled properly (and a redundant check has been removed).No changes to the actual control toolbox itself.