Skip to content

MAINT: Improve benchmarking code #3315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2025

Conversation

stefan6419846
Copy link
Collaborator

This PR updates some outdated references in the benchmarking job and fixes compatibility with the latest pytest versions. With our settings and the benchmarking and xdist plugins enabled, running the tests on pytest>=8.4.0 would break/fail otherwise.

Copy link

codecov bot commented Jun 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.71%. Comparing base (05300d5) to head (db4ed3d).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3315   +/-   ##
=======================================
  Coverage   96.71%   96.71%           
=======================================
  Files          53       53           
  Lines        9029     9029           
  Branches     1674     1674           
=======================================
  Hits         8732     8732           
  Misses        177      177           
  Partials      120      120           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@stefan6419846 stefan6419846 merged commit 67d1ba1 into py-pdf:main Jun 17, 2025
16 checks passed
@stefan6419846 stefan6419846 deleted the pytest-benchmark branch June 17, 2025 12:03
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.

1 participant