Skip to content

fix(cutile): pass the smoke-test feature to the benchmark smoke run - #1634

Open
0z5a wants to merge 1 commit into
NVIDIA:mainfrom
0z5a:fix/cutile-bench-smoke-feature
Open

0z5a wants to merge 1 commit into
NVIDIA:mainfrom
0z5a:fix/cutile-bench-smoke-feature

Conversation

@0z5a

@0z5a 0z5a commented Oct 24, 2026

Copy link
Copy Markdown

Summary

scripts/test_benchmarks.sh calls

run_benches "$REPO_ROOT/cutile-benchmarks/benches" "smoke-test"

Since run_benches was changed to parse cargo flags, it takes --features X and drops every bare word. So smoke-test never reaches Cargo. run_all.sh and the README's "fast, discards results" smoke test then run every benchmark with full criterion settings. They also save base baselines, which the smoke mode is meant to leave alone. The script's output is discarded, so nothing shows this.

Changes

  • test_benchmarks.sh: pass --features smoke-test.

Testing

B300, softmax bench, run the way run_benches runs it:

before (argument dropped):            exit=0  19 s  "Warming up for 500.00 ms" x6
after  (--features smoke-test):       exit=0   9 s  "Warming up for 1.0000 ms" x6

With the fix, test_benchmarks.sh reports 4 passed / 4 failed on B300. The four failures (fmha, fmha_causal, gemm, launch_overhead) are unrelated to this change: on my host they come from a tileiras/toolkit version mismatch, which I am checking separately.

  • bash syntax check
  • just check -- not run; script-only change

Checklist

  • All commits signed off (git commit -s)

run_benches takes cargo flags (--features X) and ignores bare words, so
the plain "smoke-test" argument from test_benchmarks.sh was dropped:
every benchmark ran with full criterion measurement, and saved results to
the criterion baselines the smoke mode is meant to leave alone.

Signed-off-by: 0z5a <dezhen.lu@student.uni-tuebingen.de>
@0z5a
0z5a requested a review from elibol as a code owner October 24, 2026 18:37
@copy-pr-bot

copy-pr-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

This branch has not been deployed

No deployments
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.

1 participant