@rust-timer supports several commands, the most common (and simple) being
@rust-timer queue. This command is usually invoked as
@bors try @rust-timer queue,
which starts a bors "try" run (not a merge).
@rust-timer will wait for the try run to finish,
and if it succeeds will then queue a perf run.
@rust-timer queue has a few extra options that can be useful:
include=<INCLUDE>only runs benchmarks with
<INCLUDE>in their title. For example, if you just want to run rustdoc benchmarks, do
@bors try @rust-timer queue include=-doc; the
-docappended to rustdoc benchmarks.
<INCLUDE>is a comma-separated list of substrings; only one of the items in the list of substrings must match.
exclude=<EXCLUDE>is similar to
include=, but instead skips any benchmarks that have one of the items in the list of substrings as a substring of its name.
runs=<RUNS>configures how many times the benchmark is run.
<RUNS>is an integer. All benchmarks run at least once by default, but some run more than one time. You can use the
runsoption to override the default run count and make every benchmark run for
@rust-timer queue, but the
queue command is the most used.
@rust-timer build $commit will queue a perf run for the given commit
It is usually invoked with the commit from a successful "try" run. (The
queue command can be seen as a shortcut that automatically selects the
"try" run's commit for the
This command also supports the same
The other two commands are a work in progress and will be documented here when they're finalized. They are dedicated to helping diagnose the cause of regressions in rollup PRs.