Fix SA dialect suite collapse under pytest 9 --strict-markers

[ShawnChen-Sirius]

Summary

Scheduled CI on main has been failing every day since 2026-06-08 with:

INTERNALERROR> Failed: 'mypy' not found in `markers` configuration option

(See e.g. run 27606145536.)

Root cause

SQLAlchemy's testing plugin registers a handful of pytest markers dynamically:

• At import time via config.add_to_marker.<name>: mypy, memory_intensive, timing_intensive
• During collection via test_class.add_marker(...): backend, sparse_backend, sparse_driver_backend

pytest 9.x tightened --strict-markers so these lookups now fail() before SA's session-start hook can register the markers itself, aborting the whole sa_suite session at collection.

The repo opts into --strict-markers globally via pyproject.toml addopts — intentional, it catches typos in our own markers — and the sa_suite job inherits the flag. Dropping --strict-markers globally would lose that safety net on the rest of the tree.

Fix

Pre-register the SA-internal markers in tests/sa_suite/conftest.py so the lookup succeeds. Scoped to the sa_suite directory; no effect on the unit / contract / fuzz / perf / integration / differential jobs.

Test plan

• Reproduced locally with pytest 9.1.0 + SQLAlchemy 2.0.51 + chdb 4.1.9 (same versions as CI)
• sa_suite: 595 passed, 673 skipped (skip count matches the pre-regression baseline)
• pytest -ra -m "not integration and not differential and not perf and not fuzz": 314 passed
• CI green on this PR

Generated with Claude Code
via Happy