Skip to content

Conversation

@sunshowers
Copy link
Contributor

@sunshowers sunshowers commented Jun 22, 2025

New in cargo-nextest 0.9.117: see https://nexte.st/docs/features/benchmarks.

Created using spr 1.3.6-beta.1
@sunshowers sunshowers requested a review from smklein June 22, 2025 20:07
Created using spr 1.3.6-beta.1
@sunshowers sunshowers changed the title [nexus-db-queries] demo showing cargo nextest bench [nexus-db-queries] use cargo nextest bench Jan 2, 2026
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1
group.bench_function(&name, |b| {
// Force evaluation of the harness outside to_async to
// avoid nested block_on.
let harness = &*harness;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit; I think there's a method called Lazy::force to do the same thing as this https://doc.rust-lang.org/std/cell/struct.LazyCell.html#method.force with the intention of being explicit. Don't have a strong preference about it tho

// You can run these with the following command:
//
// ```bash
// cargo bench -p nexus-db-queries
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone still uses the cargo bench invocation, do we have a way to tell that poor developer to "please use nextest; if you use cargo bench, your database won't get configured correctly"?

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.

3 participants