search

whoownsphilly / wop-web

https://wop-web.vercel.app
2 stars 1 forks source link

Bump pytest-benchmark from 3.2.3 to 3.4.1 #3

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps pytest-benchmark from 3.2.3 to 3.4.1.

Changelog

Sourced from pytest-benchmark's changelog.

3.4.1 (2021-04-17)

  • Republished with updated changelog.

    I intended to publish a 3.3.0 release but I messed it up because bumpversion doesn't work well with pre-commit apparently... thus 3.4.0 was set in by accident.

3.4.0 (2021-04-17)

  • Disable progress indication unless --benchmark-verbose is used. Contributed by Dimitris Rozakis in [#149](https://github.com/ionelmc/pytest-benchmark/issues/149) <https://github.com/ionelmc/pytest-benchmark/pull/149>_.
  • Added Python 3.9, dropped Python 3.5. Contributed by Miroslav Šedivý in [#189](https://github.com/ionelmc/pytest-benchmark/issues/189) <https://github.com/ionelmc/pytest-benchmark/pull/189>_.
  • Changed the "cpu" data in the json output to include everything that cpuinfo outputs, for better or worse as cpuinfo 6.0 changed some fields. Users should now ensure they are an adequate cpuinfo package installed. MAY BE BACKWARDS INCOMPATIBLE
  • Changed behavior of --benchmark-skip and --benchmark-only to apply early in the collection phase. This means skipped tests won't make pytest run fixtures for said tests unnecessarily, but unfortunately this also means the skipping behavior will be applied to any tests that requires a "benchmark" fixture, regardless if it would come from pytest-benchmark or not. MAY BE BACKWARDS INCOMPATIBLE
  • Added --benchmark-quiet - option to disable reporting and other information output.
  • Squelched unnecessary warning when --benchmark-disable and save options are used. Fixes [#199](https://github.com/ionelmc/pytest-benchmark/issues/199) <https://github.com/ionelmc/pytest-benchmark/issues/199>_.
  • PerformanceRegression exception no longer inherits pytest.UsageError (apparently a final class).
Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 3 years ago

Looks like pytest-benchmark is up-to-date now, so this is no longer needed.