Skip to content

Conversation

@not-matthias
Copy link
Member

@not-matthias not-matthias commented Feb 9, 2026

We can panic, since there's no way that the integration should continue to run when we don't support it. This is needed to prevent running old pytest-codspeed versions with memory instrument, since we only print the errors as warnings.

@codspeed-hq
Copy link

codspeed-hq bot commented Feb 9, 2026

Merging this PR will not alter performance

✅ 4 untouched benchmarks


Comparing cod-2206-memtrack-integration-version-check-not-working-for-pytest (3cefb08) with main (9bcf7fc)

Open in CodSpeed

@not-matthias not-matthias force-pushed the cod-2206-memtrack-integration-version-check-not-working-for-pytest branch from 16e3217 to 3cefb08 Compare February 9, 2026 14:50
@not-matthias not-matthias merged commit 3cefb08 into main Feb 9, 2026
13 checks passed
@not-matthias not-matthias deleted the cod-2206-memtrack-integration-version-check-not-working-for-pytest branch February 9, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants