[sentry-junior]

With PYTEST_SENTRY_ALWAYS_REPORT=1 and pytest-rerunfailures, pytest_runtest_makereport re-captures the whole accumulated exception chain on every attempt. A test that fails N times therefore sends 1 + 2 + … + N events, and a flaky test that passes on retry re-sends all of its earlier failures, tagged pytest.result:passed. Events also can't tell "failed, will be retried" apart from "failed every attempt", so alerts on pytest.result:failed fire on flaky retries even when CI is green.

This came up in getsentry/sentry's master test alerting. There, one hard-failing test produced ~20 events per CI run, and the alert went critical on most weekday afternoons while master was green.

Changes:

• In always-report mode, each attempt captures only its own exception. Earlier attempts were already sent.
• The default mode is unchanged: flaky tests are still reported once, when they pass after failing.
• Call-phase events are tagged with pytest.attempt (rerunfailures' execution_count, 1-based) and pytest.final_attempt. pytest.final_attempt is true when rerunfailures won't retry the test again, or always when rerunfailures isn't installed or no reruns are configured. With these tags, pytest.result:failed pytest.final_attempt:true is a clean "this test actually failed" signal.

getsentry/sentry carries the same behavior as a local plugin for now, because it's still on pytest-sentry 0.3.0 with sentry-sdk 2.x (getsentry/sentry#128233).

Tooling port (second commit)

• uv: pyproject.toml (uv_build backend) + committed uv.lock replace setup.py, setup.cfg, dev-requirements.txt, .flake8 and Makefile.
• Python >=3.13 only (breaking); CI tests 3.13 and 3.14.
• Latest deps: pytest 9.1.1, sentry-sdk 3.0.0a7, wrapt 2.5.1, pytest-rerunfailures 16.7, Ruff 0.17.1, ty 0.0.90.
• Ruff select = ["ALL"] + preview (only formatter-conflicting / mutually exclusive rules ignored); ty with every rule as an error and error-on-warning. All findings fixed, no blanket suppressions.
• CI: new lint job (ruff check, ruff format --check, ty check), uv-based test matrix, uv build for dist (artifact name unchanged for craft), actions pinned to SHAs. bump-version.sh now updates pyproject.toml and uv.lock.

Why every test job was failing

Not this change: sentry-sdk 3.0.0a7 crashes at import with OpenTelemetry >=1.44 (contextvars_context.py calls Context.pop(), and Context became immutable in 1.44). The lockfile constrains opentelemetry-api/sdk<1.44 via [tool.uv] constraint-dependencies (dev/CI only, not in package metadata). Downstream users on OTel >=1.44 still hit it until sentry-sdk is fixed.

via @joshuarli.

--

View Junior Session [Sentry]

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit bd5114d. Configure here.}