Fix 13 pytest warnings by registering timeout marker and removing inv…#448
Conversation
…alid config Remove the `timeout = 30` config option (requires pytest-timeout plugin to be installed) and register the `timeout` marker to eliminate PytestUnknownMarkWarning across all test files. https://claude.ai/code/session_015dvuwK9VyLDZ2FZNcV1Pbn
There was a problem hiding this comment.
Pull request overview
Updates pytest configuration to eliminate warnings related to the timeout marker/config when pytest-timeout isn’t present, by removing an unrecognized ini option and explicitly registering the marker used throughout the test suite.
Changes:
- Removed
timeout = 30from[tool.pytest.ini_options](avoids unknown ini option warnings whenpytest-timeoutis not installed). - Registered the
timeoutmarker in pytest ini options to avoidPytestUnknownMarkWarningfor@pytest.mark.timeout(...).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| timeout = 30 | ||
| markers = [ | ||
| "timeout(seconds): set a timeout for the test (requires pytest-timeout)", | ||
| ] |
There was a problem hiding this comment.
Removing the global timeout = 30 ini option changes test behavior: any test file that does not set @pytest.mark.timeout (most files in tests/ currently don’t) will no longer have a safety timeout and could hang indefinitely. If the intent is to keep a default timeout while eliminating warnings, consider enforcing/ensuring pytest-timeout is installed for test runs (e.g., via required_plugins) and keep the ini option, or add a global timeout mark via tests/conftest.py/common pytest configuration so all tests remain bounded.
| ] | |
| ] | |
| timeout = 30 | |
| required_plugins = ["pytest-timeout"] |
…alid config
Remove the
timeout = 30config option (requires pytest-timeout plugin to be installed) and register thetimeoutmarker to eliminate PytestUnknownMarkWarning across all test files.