Skip to content

Releases: CodSpeedHQ/pytest-codspeed

v4.0.0

10 Jul 08:50
v4.0.0
f3b85bc
Compare
Choose a tag to compare

What's Changed

This release introduces profiling to the walltime instrument and includes several key improvements to the existing benchmark fixture API! 🎉

Warning

Since we're now using CodSpeedHQ/instrument-hooks to control the instrument state, the performance may slightly change in tiny microbenchmarks when upgrading.

🚀 Features

  • Support perf profiling in Python walltime instrument by @not-matthias in #79
  • Support pytest-benchmark marker attributes by @art049 in #80
  • Support the pedantic API by @art049 in #81

New Contributors

Full Changelog: v3.2.0...v4.0.0

v3.2.0

31 Jan 14:31
v3.2.0
253b1be
Compare
Choose a tag to compare

What's Changed

This release improves the reliability of the measurement, primarily focusing on the wall-time instrument.

🚀 Features

  • Increase the min round time to a bigger value (+/- 1ms) by @art049

  • Fix the random seed while measuring with instruments by @art049 in #48

🐛 Bug Fixes

  • Use time per iteration instead of total round time in stats by @art049

🏗️ Refactor

  • Replace hardcoded outlier factor for improved readability by @art049 in #67

⚙️ Internals

⚠️ Since the wall-time instrument is still in beta, this minor release might create unexpected performance changes for this new instrument.

Full Changelog: v3.1.2...v3.2.0

v3.1.2

09 Jan 13:42
v3.1.2
da9270d
Compare
Choose a tag to compare

What's Changed

🐛 Bug Fixes

  • fix: update package_data to include header and source files for valgrind wrapper by @art049 in #64

Full Changelog: v3.1.1...v3.1.2

v3.1.1

07 Jan 16:31
v3.1.1
11de031
Compare
Choose a tag to compare

What's Changed

⚙️ Internals

  • Add a py3-none-any fallback wheel by @art049 in #61

Full Changelog: v3.1.0...v3.1.1

v3.1.0

09 Dec 09:50
v3.1.0
3b1a30c
Compare
Choose a tag to compare

What's changed

🚀 Features

  • Build the native extension during packaging to avoid runtime build issues by @art049 in #57

Full Changelog: v3.0.0...v3.1.0

v3.0.0

29 Oct 16:58
v3.0.0
4f45b41
Compare
Choose a tag to compare

What's Changed

This new release includes a new wall time instrument that allows measurement of real execution timings. This will be very useful for macro benchmarks running on properly isolated machines. You can now use our CodSpeed Macro runners without changing anything to your existing CI workflows.

Find more info on our Walltime instrument here.

image

Breaking changes

  • Dropped support for Python 3.8 since it reached its EOL

Features

  • feat: add walltime clock benchmarking by @art049 in #41
  • feat/add max time and quartiles by @art049 in #45
  • feat: also save the lower and upper fences in the json data by @art049 in #46

Fixes

  • fix: pytest-benchmark 5.0.0 compatibility by @art049 in #54
  • fix: don't override pytest's default protocol by @kenodegard in #32

Internals

  • chore: Add TCH, FA, and UP lints by @kenodegard in #29
  • Expose type information by @Dreamsorcerer in #53
  • ci: bump actions/checkout to v4 by @fargito in #47
  • chore: support python 3.13 and drop 3.7 by @art049 in #40
  • feat: use a true semver version by @art049 in #44
  • test: add benches for TheAlgorithms/backtracking by @art049 in #43
  • test: add benches for TheAlgorithms/audio_filters by @art049 in #42
  • docs(readme): update action version in the CI workflow configuration by @frgfm in #39

New Contributors

Full Changelog: v2.2.1...v3.0.0

v2.2.1

19 Mar 22:00
v2.2.1
7546a2f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.2.0...v2.2.1

v2.2.0

01 Sep 12:59
v2.2.0
faa4b7d
Compare
Choose a tag to compare

What's Changed

pytest-xdist is now fully supported. Thus if you have a lot of benches, you can totally leverage xdist test distribution (on the same CPU) to speed up benchmark execution.

Details

  • feat: fix pytest-xdist-compatibility by @art049 in #18

Full Changelog: v2.1.0...v2.2.0

v2.1.0

27 Jul 13:38
v2.1.0
a752fb9
Compare
Choose a tag to compare

What's Changed

Relative paths are now properly handled when using the working-directory action parameter.

Details

  • fix: git relative path with working-directory by @art049 in #15

Internals

Full Changelog: v2.0.1...v2.1.0

v2.0.1

22 Jul 09:27
v2.0.1
3704ce0
Compare
Choose a tag to compare

What's Changed

Added

  • Added support for returning values by @patrick91 in #12
  • Add a return type to the benchmark fixture by @art049 in #13

New Contributors

Full Changelog: v2.0.0...v2.0.1