dholroyd / mpeg2ts-reader

Rust reader for MPEG2 Transport Stream data
Apache License 2.0
51 stars 14 forks source link

Update iai-callgrind requirement from 0.11.0 to 0.13.3 #70

Closed dependabot[bot] closed 5 days ago

dependabot[bot] commented 1 week ago

Updates the requirements on iai-callgrind to permit the latest version.

Release notes

Sourced from iai-callgrind's releases.

v0.13.3

Changelog

[0.13.3] - 2024-09-05

The installation of iai-callgrind-runner with cargo install did not use the cache when trying to install the same version again and acted as if cargo install --force was given which leads to longer installation times in case the binary was already installed. See this issue for more details.

This problem is fixed in this and the following releases, but not in older versions of iai-callgrind-runner. Please use binstall instead of cargo install for these versions if installation time is a concern. binstall seems to correctly recognize the same installation and does not install iai-callgrind-runner from scratch again.

Added

  • (#254): Added the option to switch off the entry point EntryPoint::None or use a custom entry point (EntryPoint::Custom). The default entry point stays the same and is the toggle Iai-Callgrind sets with --toggle-collect to the benchmark function.

Changed

  • (#254): Due to the changes required to handle the different entry points options, the flamegraphs created in binary benchmarks and flamegraphs from library benchmarks with EntryPoint::None include all events, not only the events from main downwards.

Fixed

  • (#261): Reinstalling iai-callgrind-runner with cargo install when it was already installed acted as if cargo install --force was given.

Full Changelog: https://github.com/iai-callgrind/iai-callgrind/compare/v0.13.2...v0.13.3

Changelog

Sourced from iai-callgrind's changelog.

[0.13.3] - 2024-09-05

The installation of iai-callgrind-runner with cargo install did not use the cache when trying to install the same version again and acted as if cargo install --force was given which leads to longer installation times in case the binary was already installed. See this issue for more details.

This problem is fixed in this and the following releases, but not in older versions of iai-callgrind-runner. Please use binstall instead of cargo install for these versions if installation time is a concern. binstall seems to correctly recognize the same installation and does not install iai-callgrind-runner from scratch again.

Added

  • (#254): Added the option to switch off the entry point EntryPoint::None or use a custom entry point (EntryPoint::Custom). The default entry point stays the same and is the toggle Iai-Callgrind sets with --toggle-collect to the benchmark function.

Changed

  • (#254): Due to the changes required to handle the different entry points options, the flamegraphs created in binary benchmarks and flamegraphs from library benchmarks with EntryPoint::None include all events, not only the events from main downwards.

Fixed

  • (#261): Reinstalling iai-callgrind-runner with cargo install when it was already installed acted as if cargo install --force was given.

[0.13.2] - 2024-09-03

Fixed

  • (#252): When using callgrind client requests like start_instrumentation, stop_instrumentation together with --collect-at-start=no then all metrics were zero. Thanks to @​hargut
  • (#257): A small cosmetic fix for the factor in the benchmark output if it was negative infinite. [++-inf+++] was changed to [---inf---].
  • (#258): The

... (truncated)

Commits
  • 9f47f13 Update CHANGELOG
  • 4188829 Merge branch 'release'
  • 9fdfe86 Update CHANGELOG
  • 43d4324 Bump version v0.13.2 -> v0.13.3
  • 0e09a24 Update CHANGELOG
  • e03b173 Merge pull request #254 from gamma0987/adjustable-entry-point
  • d26ce89 feat(entry_point): Update CHANGELOG
  • 14f9930 feat(entry_point): Fix formatting in rust source files
  • 6e553cb docs(book): Improve flamegraph docs and add example images
  • 39698c9 docs(book): Add entry point docs to the guide
  • Additional commits viewable in compare view


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)
github-actions[bot] commented 1 week ago

🐰Bencher

ReportFri, September 6, 2024 at 06:44:17 UTC
Projectmpeg2ts-reader
Branch70/merge
Testbedlocalhost

⚠️ WARNING: The following Measures do not have a Threshold. Without a Threshold, no Alerts will ever be generated!

  • Instructions (instructions)
  • L1 Hits (l1-hits)
  • L2 Hits (l2-hits)
  • RAM Hits (ram-hits)
  • Total read+write (total-read-write)

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds CLI flag.

Click to view all benchmark results
BenchmarkEstimated CyclesEstimated Cycles Results
estimated cycles | (Δ%)
Estimated Cycles Lower Boundary
estimated cycles | (%)
InstructionsInstructions Results
instructions
L1 HitsL1 Hits Results
hits
L2 HitsL2 Hits Results
hits
RAM HitsRAM Hits Results
hits
Total read+writeTotal read+write Results
reads/writes
ci_bench::ci::reader✅ (view plot)33,791,621.00 (+15.43%)27,811,339.20 (82.30%)➖ (view plot)20,346,236.00➖ (view plot)26,393,641.00➖ (view plot)4,409.00➖ (view plot)210,741.00➖ (view plot)26,608,791.00

Bencher - Continuous Benchmarking
View Public Perf Page
Docs | Repo | Chat | Help
dependabot[bot] commented 5 days ago

Superseded by #71.