Something went wrong. Try again.
the cms for static site generators on atproto
Something went wrong. Try again.
2.2 kB · 39 lines
at main
12345678910111213141516171819202122232425262728293031323334353637383940[pytest]# The suite's files are t_*.py; pytest's default python_files would collect none of them.python_files = t_*.py test_*.py
# Every module imports `test` from e2e.lib.harness, a decorator factory.# pytest collects imported names as module attributes, so the default `test*`# matches that import. That adds one item per file: 80 phantoms against 400.# Narrowing to `test_*` drops them.## It does NOT stop imported names being collected. An imported `test_something`# would still appear. A name imported here needs a prefix this pattern excludes.python_functions = test_*
markers = exclusive: runs alone, after every other phase has drained pool: leases one of the shared PDS slots oauth_domains: managed public HTTPS origins and a leased real PDS account loopback: free-port loopback integration tests bsky: uses the shared real-PDS account; serial lane real_pds: performs a real-PDS OAuth login using a worker pool account xdist_group: tests assigned to the same xdist scheduling group
# misc/ holds machinery that is not part of any run. Collecting it would run it.norecursedirs = misc .venv* __pycache__ node_modules sse publish hugo iroh-sync keycloak test-data .caddy-data
# `--max-worker-restart=0` IS NOT HERE, AND THAT IS DELIBERATE. It is an xdist option,# so it only parses when xdist is loaded -- and phase 3 runs `-p no:xdist`, which blocks# the plugin, so its `pytest_addoption` never runs and the flag becomes an UNRECOGNISED# ARGUMENT. An ini addopt applies to EVERY invocation, including the one that cannot# accept it: phase 3 exited on usage before collecting a single test.## Nobody saw it because phase 2 short-circuited every run before phase 3 could start. It# surfaced on the FIRST RUN WHERE PHASES 1 AND 2 BOTH PASSED -- exactly the run everyone# would be reading as the green one.## So the flag now lives on the two phases that actually run xdist, in run-linecov.sh,# where the coupling is visible instead of ambient. A setting that is meaningless in one# venue and fatal in another does not belong in the file that applies to all of them.addopts = -p no:cacheprovider