ci: upload benchmark input files

[AvivYossef-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[github-actions]

Artifacts upload workflows:

• Started at 2025-10-19T10:38:31Z
• Started at 2025-10-19T10:58:28Z
• Started at 2025-10-19T10:58:28Z
• Started at 2025-10-19T11:31:48Z
• Started at 2025-10-19T11:52:07Z
• Started at 2025-10-19T11:55:06Z
• Started at 2025-10-19T13:02:06Z
• Started at 2025-10-19T13:02:34Z
• Started at 2025-10-20T06:26:10Z
• Started at 2025-10-22T06:16:10Z
• Started at 2025-10-22T06:32:30Z
• Started at 2025-10-22T06:32:30Z
• Started at 2025-10-22T06:42:18Z
• Started at 2025-10-22T06:45:08Z
• Started at 2025-10-22T12:13:07Z
• Started at 2025-10-22T12:23:20Z
• Started at 2025-10-22T12:54:57Z
• Started at 2025-10-23T09:36:54Z
• Started at 2025-10-23T10:08:06Z
• Started at 2025-10-23T10:08:48Z
• Started at 2025-10-23T10:25:00Z
• Started at 2025-10-23T10:25:32Z

[AvivYossef-starkware]

• infra: test committer benchmark ci #9526
• ci: use benchtools to benchmark the committer #9707
• bench_tools: run and compare benchmark #9699
• bench_tools: support deserialization of criterion change #9698
• bench_tools: save specific benchmark result #9742
• bench_tools: add criterion benchmark names to benchmark config #9697
• bench_tools: add bench tools to allowed scopes #9696
• ci: run benchmark command #9636
• ci: download bench input from gcs #9634
• ci: add input to benchmark config #9633
• ci: add dummy bench with input #9632
• ci: upload benchmark input files #9627 👈 (View in Graphite)
• ci: add benchmark config #9625 : 1 other dependent PR (#9626 )
• ci: deserialize cargo bench result #9624
• ci: add bench_tools CLI scaffold #9612
• main-v0.14.1

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Benchmark movements: No major performance changes detected.

[avi-starkware]

@avi-starkware reviewed 5 of 6 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @meship-starkware)

---

Cargo.toml line 386 at r2 (raw file):

void = "1.0.2"
waker-fn = "1.2.0"
walkdir = "2.5"

where is this used?

Code quote:

walkdir = "2.5"

---

bench_tools/src/gcs.rs line 12 at r2 (raw file):

///
/// Files are uploaded to: `gs://{BENCHMARKS_BUCKET}/{benchmark_name}/input/`
pub async fn upload_inputs(benchmark_name: &str, input_dir: &Path) {

why is async needed here?

Code quote:

pub async fn upload_inputs(benchmark_name: &str, input_dir: &Path) {

[avi-starkware]

@avi-starkware reviewed 2 of 2 files at r4, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @AvivYossef-starkware and @meship-starkware)

[avi-starkware]

@avi-starkware reviewed 2 of 2 files at r5, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @AvivYossef-starkware and @meship-starkware)

[graphite-app]

Merge activity

• Oct 23, 10:25 AM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.

[AvivYossef-starkware]

Reviewable status: 5 of 9 files reviewed, 1 unresolved discussion (waiting on @avi-starkware and @meship-starkware)

---

bench_tools/src/gcs.rs line 12 at r2 (raw file):

Previously, avi-starkware (Avi Cohen) wrote…

I don't mind using async, I just don't understand which other tasks tokio runs concurrently with this one

removed

[AvivYossef-starkware]

@AvivYossef-starkware reviewed 3 of 4 files at r6, all commit messages.
Reviewable status: 8 of 9 files reviewed, all discussions resolved (waiting on @avi-starkware and @meship-starkware)

[avi-starkware]

@avi-starkware reviewed 4 of 4 files at r6, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @meship-starkware)