Skip to content

Fix Store benchmarks - #20057

Merged
stuhood merged 1 commit into
pantsbuild:mainfrom
stuhood:stuhood/fix-benches
Oct 19, 2023
Merged

Fix Store benchmarks#20057
stuhood merged 1 commit into
pantsbuild:mainfrom
stuhood:stuhood/fix-benches

Conversation

@stuhood

@stuhood stuhood commented Oct 18, 2023

Copy link
Copy Markdown
Member

Fix the location of all_the_henries.txt to allow Store benchmarks to run.

@stuhood stuhood added the category:internal CI, fixes for not-yet-released features, etc. label Oct 18, 2023
@stuhood
stuhood requested review from huonw and thejcannon October 18, 2023 21:34
@stuhood
stuhood enabled auto-merge (squash) October 18, 2023 21:34

@huonw huonw left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ah oops, thanks.

(For our future reference, in case it matters, this was broken by #19958.)

I believe that cargo test --benches (or something along those lines) allows running benchmarks in "test mode" where they only execute once to provide some sort of assurance that they're functional. I wonder if we could do that too and how big of an impact on CI time it would be.

@stuhood
stuhood merged commit d9f609a into pantsbuild:main Oct 19, 2023
@stuhood
stuhood deleted the stuhood/fix-benches branch October 19, 2023 16:07
stuhood pushed a commit that referenced this pull request Oct 31, 2023
Cargo/criterion supports running benchmarks in "test" mode, where they
only execute once and don't actually benchmark, but at least validate
that the code seems to run. This fixes #20067 by switching CI to do
this.

The store benchmark (the only benchmarks at the moment) seems to take
~80s to run in CI. Is it worth it to avoid problems like #20057?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category:internal CI, fixes for not-yet-released features, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants