Skip to content

Add a bit more documentation about using rustc commits for benchmarking directly #1321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 13, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion collector/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,11 @@ The following arguments are mandatory.
should choose consistently. **Alternatively**, it can be a `+`-prefixed
toolchain specifier such as `+nightly` or
`+f7bb8e3677ba4277914e85a3060e5d69151aed44` in which case `rustup` will be
used to obtain the toolchain, downloading it if necessary.
used to obtain the toolchain, downloading it if necessary. The commit SHA
of the toolchain does not need to be in the `rustc` `master` branch, it can be e.g.
the result of a `try` CI run. You will need to have
[`rustup-toolchain-install-master`](https://github.com/kennytm/rustup-toolchain-install-master)
installed in order for this to work.

The identifier under which the results will be put into the database varies.
- If the `--id` option is specified, that identifer will be used.
Expand Down