build(deps): Bump pytest-xdist to 3.8.0, drop pytest-workaround-12888

[sentry-junior]

Bumps pytest-xdist 3.0.2 → 3.8.0 (latest), and with it execnet 1.9.0 → 2.1.2. Also removes the pytest-workaround-12888 dev dependency and keeps xdist's --dist=loadfile ordering exactly as it was.

Bump is done. getsentry/pypi#2626 mirrored pytest-xdist==3.8.0 and execnet==2.1.2 to internal PyPI (pypi.devinfra.sentry.io). The bump comes from that index via uv@0.12.10 add --dev "pytest-xdist>=3.8.0", the same command tools/bump_version.py runs in the bump-version workflow. It's applied on this branch rather than through a separate workflow PR so it lands together with the ordering guard below. No public index or override was added, and the lock's wheel hashes match the upstream release artifacts.

Removing pytest-workaround-12888

The package was only a .pth file that ran import readline early, to work around pytest-dev/pytest#12888. pytest-dev/pytest#13176 fixed that upstream, and pytest 9.0.3 (our locked version) already calls _readline_workaround() from _pytest/capture.py in pytest_load_initial_conftests. Nothing else in the repo refers to it.

Keeping test ordering the same (--dist=loadfile)

Starting in xdist 3.5.0 (pytest-dev/pytest-xdist#632), LoadScopeScheduling sorts work units by test count, largest first, before handing them out. LoadFileScheduling subclasses it, so --dist=loadfile is affected too, and this is on by default. On its own, the bump would change the order files are handed to workers. That changes which files share a worker and the order they run in. It would also override the SENTRY_SHUFFLE_TESTS ordering.

xdist 3.8.0 (pytest-dev/pytest-xdist#1083) added --no-loadscope-reorder to turn this off. This PR sets the same thing (config.option.loadscopereorder = False) in sentry.testutils.pytest.sentry:pytest_configure, so the work queue keeps collection order exactly as it did on 3.0.2. getsentry loads the same plugin, so it's covered too. --dist=loadfile and how we pick worker counts are not changed.

I checked the rest of the scheduler diff between 3.0.2 and 3.8.0 (scheduler/loadscope.py, scheduler/loadfile.py). Apart from the reorder, the changes are typing and switching OrderedDict to plain dict. Insertion order is kept, and dropping extra nodes still pops the last node. File scoping in _split_scope is unchanged. testrunuid is still uuid4().hex per run, so the deterministic PYTEST_XDIST_TESTRUNUID-seeded cell name works the same.

xdist 3.0.2 → 3.8.0 changes that matter for our CI (-n 2/3 --dist=loadfile)

• 3.4.0 syntax errors in the config file aren't handled gracefully #963: when a run stops early, the controller waits for workers to finish reporting. Results from in-progress tests are no longer dropped, so timeout and --maxfail output gets more useful.
• 3.5.0 Can't start http and udp services simultaneously #632: the loadscope/loadfile reorder. Neutralized here, see above.
• 3.6.0 Filters on tags not correct #1027 / Ability to change team owner via admin page #620: workers always run tests in the main thread (execnet main_thread_only execmodel). Before this, execnet could run tests in a non-main thread.
• 3.6.0 Include tags in e-mails #1024: workers now honor shouldstop/shouldfail (for example --maxfail) instead of running more tests before the controller stops them.
• 3.6.0 Fix two typos on Quotas page #1028: fixes looponfail with editable installs. Only matters locally, since we set looponfailroots.
• 3.6.1 Event navigation busted if two events have same timestamp #1071: fixes a deadlock between execnet's main_thread_only model and pytest-cov reading rinfo. Relevant to the coverage jobs (pytest-cov 4.0.0).
• 3.3.1 Notification settings aren't saved anymore. #907: no remote calls during worker startup, to avoid scheduling the worker into a non-main thread.
• Requirements: execnet>=2.1 (1.9.0 → 2.1.2) and pytest>=7. We're on pytest 9.0.3 and Python 3.13. 3.7.0 adds official 3.13 support.

Things that stay the same:

• The pytest_xdist_setupnodes hookspec.
• PYTEST_XDIST_WORKER / PYTEST_XDIST_TESTRUNUID / PYTEST_XDIST_WORKER_COUNT, still set in xdist/remote.py.
• The --looponfail/looponfailroots and --rsyncdir deprecation warnings: same text, so the existing filterwarnings entries still match.

Other changes in this range don't touch the code paths we use (--dist=loadfile, -n), and no scheduling options are adopted or proposed.

Verification (local, env synced from this branch's uv.lock via internal PyPI)

• pytest -n 3 --dist=loadfile --reuse-db -q tests/sentry/api/bases/: 159 passed, with the workaround package uninstalled.
• Ordering: with -n 1 --dist=loadfile on tests/sentry/api/bases/, files ran in collection order (test_organization 64 tests, test_organization_events 10, test_organizationmember 8, test_project 44, test_team 33), not sorted by size. A synthetic suite gave the same order on 3.0.2, on 3.8.0 + --no-loadscope-reorder, and on 3.8.0 + the plugin pin. Plain 3.8.0 reordered it.
• getsentry tests/getsentry/test_features.py with -n 2 --dist=loadfile: 121 passed, with and without -W ignore::DeprecationWarning:xdist.plugin. Checked earlier against the same xdist/execnet versions.
• prek run and mypy are clean.

via @joshuarli.

--

View Junior Session [Sentry]