chore: bump alloc_tracker from 0.6.0 to 0.7.0#568
Conversation
Bumps [alloc_tracker](https://github.com/folo-rs/folo) from 0.6.0 to 0.7.0. - [Release notes](https://github.com/folo-rs/folo/releases) - [Changelog](https://github.com/folo-rs/folo/blob/main/docs/release-automation.md) - [Commits](folo-rs/folo@alloc_tracker-v0.6.0...alloc_tracker-v0.7.0) --- updated-dependencies: - dependency-name: alloc_tracker dependency-version: 0.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
@copilot, do a proper upgrade |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #568 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 356 356
Lines 27388 27388
=======================================
Hits 27388 27388 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
| BytesBuf::new, | ||
| |buf| { | ||
| let _span = allocs_op.measure_thread(); | ||
| let _span = allocs_op.measure_thread().iterations(1); |
There was a problem hiding this comment.
The documentation of alloc_tracker specifically mentions that iterations should be batched. Forcing us to call .iterations(N) is the breaking change, to help highlight when we are doing iterations one by one, which includes huge (relatively) measurement overhead.
The proper upgrade would also fix the pattern we use to iter_custom() so we batch all our iterations for one Criterion sample, instead of measuring microbenchmark iterations one by one.
Bumps alloc_tracker from 0.6.0 to 0.7.0.
Commits
bee10e4Release4394bd9Simplify tracker span API and condense docs (#342)6935825Make cargo-bench-history collect tests hermetic against CARGO_TARGET_DIR (#341)d40a479Pin Cargo tool versions in constants.env; bump gungraun to 0.19.3 (#340)e630a6fAlign install-tools with CI, remove divergent tooling paths (#339)c646b29Verify cargo-semver-checks is operational64859ceAzurite optionalb104e4bDocument measurement overhead in alloc_tracker, align all_the_time (#338)b8cf5c2Attach discriminant-set filter flags to analyze reports (#337)0437b1eRelax workflow timeouts for cold-cache setup-environment (#336)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)