fix: Fix pytest warning filters

[ajcasagrande]

Summary

• Avoid importing the optional BoTorch warning category during pytest startup
• Make the flat-shape migration warning test resilient to unrelated caplog records

Test plan

• uv run pytest -n auto tests/unit/config/test_envelope_restructure.py -q

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Updated internal warning filter configuration for improved warning management consistency.

• Tests

  • Enhanced test coverage with improved log message filtering and assertion logic for migration validation tests.

[github-actions]

Try out this PR

Quick install:

pip install --upgrade --force-reinstall git+https://github.com/ai-dynamo/aiperf.git@0cd75755aaa529bfcf1bdf5154fa064978ab75cd

Recommended with virtual environment (using uv):

uv venv --python 3.12 && source .venv/bin/activate
uv pip install --upgrade --force-reinstall git+https://github.com/ai-dynamo/aiperf.git@0cd75755aaa529bfcf1bdf5154fa064978ab75cd

---

Last updated for commit: 0cd7575 • Browse code

[coderabbitai]

Walkthrough

This PR improves test stability by broadening the pytest warning filter for torch.float32 messages and refining test caplog filtering to tolerate unrelated warnings. The test now filters log records more precisely and asserts on matching records rather than relying on a fixed record position.

Changes

Test stability and warning handling

Layer / File(s)	Summary
Pytest warning filter broadening pyproject.toml	The pytest filterwarnings configuration is updated to ignore The model inputs are of type torch.float32.* messages regardless of warning category, removing the previous constraint to botorch.exceptions.warnings.InputDataWarning.
Test robustness improvements tests/unit/config/test_envelope_restructure.py	Test adds a logging import and emits an unrelated warning to verify robustness. The caplog assertion is refined to filter records matching both "flat shape" and "migrate_config_yaml.py", replacing the prior single-record substring check with a filtered collection assertion.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Warnings wild and logs run deep,
We filter out the chaff we reap,
Our tests stand tall through noise and haste,
No more flakes—just steady taste! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title accurately summarizes the main change: fixing pytest warning filters by broadening an ignore rule and updating test assertions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!