Fix warning filters in TestCase, introduce AxParameterWarning #2389
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.
These filters were not filtering out warning as expected, due to some regex issues and unnecessary
warnings.resetwarnings()
within unit tests.warnings.catch_warnings
resets the filters by default, so such calls were unnecessary.Note: The BoTorch dtype warnings are produced both as
InputDataWarning
&UserWarning
. This is only filtering forInputDataWarning
. We can reduce the warnings further by updating it on BoTorch to useInputDataWarning
.Test Plan:
Ran some tests locally and checked what warnings are produced.
pytest -ra ax/core
now produces ~250 warnings, down from ~700.test_fully_bayesian
now produces 68 warnings, down from 576.