[pytest]
testpaths = suite
addopts = -vv --durations=0 -p no:cacheprovider
log_cli = true
# WARNING (not INFO) so we don't stream every httpx ``INFO HTTP Request: ...``
# line for the ~250k+ requests these scenarios make — under -n 2 + the
# SDK's connection-monitor daemon, that previously dumped ~70k traceback
# lines per CI run. Per-test metrics are written to
# ``tests_load/.last_run/<test_name>.json`` regardless of log level, and
# the workflow summary step renders them on the run page, so we don't
# need INFO lines on stdout. SDK errors / warnings still surface.
log_cli_level = WARNING
python_files = test_*.py
# Global hang-guard: any individual scenario that runs longer than this
# is killed and reported as a failure, so a deadlock (e.g. SDK lock
# regression) never silently consumes the entire workflow budget.
# The longest legitimate scenario is `test_spread_over_time` at ~10 min
# at scale 1.0; 1200 s gives ~2x headroom. Scenarios with a tighter
# expected ceiling can override via @pytest.mark.timeout(...).
timeout = 1200
timeout_method = thread