mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Auto merge of #140786 - Kobzol:try-builds-no-deny-warnings, r=jieyouxu 

Do not deny warnings in "fast" try builds

When we do the classic ``@bors` try` build without specifying `try-job` in the PR description, we want to get a compiler toolchain for perf./crater/local experimentation as fast as possible. We don't run any tests in that case, so it seems reasonable to also ignore warnings.

Fixes: https://github.com/rust-lang/rust/issues/140753

r? `@jieyouxu`

try-job: dist-x86_64-linux
This commit is contained in:
bors 2025-05-08 18:21:54 +00:00
parent 1492fcb8bd ff2b6fd0cb
commit 7403775e7e
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/tests/ci.md
View File

@ -135,12 +135,16 @@ There are several use-cases for try builds:
- Run a specific CI job (e.g. Windows tests) on a PR, to quickly test if it - Run a specific CI job (e.g. Windows tests) on a PR, to quickly test if it
passes the test suite executed by that job. passes the test suite executed by that job.
You can select which CI jobs will By default, if you send a comment with `@bors try`, the jobs defined in the `try` section of
be executed in the try build by adding lines containing `try-job: [`jobs.yml`] will be executed. We call this mode a "fast try build". Such a try build
<job pattern>` to the PR description. All such specified jobs will be executed will not execute any tests, and it will allow compilation warnings. It is useful when you want to
in the try build once the `@bors try` command is used on the PR. If no try get an optimized toolchain as fast as possible, for a crater run or performance benchmarks,
jobs are specified in this way, the jobs defined in the `try` section of even if it might not be working fully correctly.
[`jobs.yml`] will be executed by default.
If you want to run a custom CI job in a try build and make sure that it passes all tests and does
not produce any compilation warnings, you can select CI jobs to be executed by adding lines
containing `try-job: <job pattern>` to the PR description. All such specified jobs will be executed
in the try build once the `@bors try` command is used on the PR.
Each pattern can either be an exact name of a job or a glob pattern that matches multiple jobs, Each pattern can either be an exact name of a job or a glob pattern that matches multiple jobs,
for example `*msvc*` or `*-alt`. You can start at most 20 jobs in a single try build. When using for example `*msvc*` or `*-alt`. You can start at most 20 jobs in a single try build. When using