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 #138350 - Kobzol:rollup-4kj94rq, r=Kobzol 

Rollup of 10 pull requests

Successful merges:

 - #135987 (Clarify iterator by_ref docs)
 - #137967 ([AIX] Fix hangs during testing)
 - #138063 (Improve `-Zunpretty=hir` for parsed attrs)
 - #138147 (Add maintainers for powerpc64le-unknown-linux-gnu)
 - #138288 (Document -Z crate-attr)
 - #138300 (add tracking issue for unqualified_local_imports)
 - #138307 (Allow specifying glob patterns for try jobs)
 - #138315 (use next_back() instead of last() on DoubleEndedIterator)
 - #138330 (Remove unnecessary `[lints.rust]` sections.)
 - #138335 (Fix post-merge workflow)

r? `@ghost`
`@rustbot` modify labels: rollup
This commit is contained in:
bors 2025-03-11 15:08:43 +00:00
parent eb9d046031 00f083a6d1
commit ec1915f162
1 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
src/tests/ci.md
View File

@ -133,29 +133,37 @@ There are several use-cases for try builds:
Again, a working compiler build is needed for this, which can be produced by Again, a working compiler build is needed for this, which can be produced by
the [dist-x86_64-linux] CI job. the [dist-x86_64-linux] CI job.
- 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. You can select which CI jobs will passes the test suite executed by that job.
be executed in the try build by adding up to 10 lines containing `try-job:
<name of job>` to the PR description. All such specified jobs will be executed You can select which CI jobs will
be executed in the try build 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. If no try in the try build once the `@bors try` command is used on the PR. If no try
jobs are specified in this way, the jobs defined in the `try` section of jobs are specified in this way, the jobs defined in the `try` section of
[`jobs.yml`] will be executed by default. [`jobs.yml`] will be executed by default.
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
glob patterns, you might want to wrap them in backticks (`` ` ``) to avoid GitHub rendering
the pattern as Markdown.
> **Using `try-job` PR description directives** > **Using `try-job` PR description directives**
> >
> 1. Identify which set of try-jobs (max 10) you would like to exercise. You can > 1. Identify which set of try-jobs you would like to exercise. You can
> find the name of the CI jobs in [`jobs.yml`]. > find the name of the CI jobs in [`jobs.yml`].
> >
> 2. Amend PR description to include (usually at the end of the PR description) > 2. Amend PR description to include a set of patterns (usually at the end
> e.g. > of the PR description), for example:
> >
> ```text > ```text
> This PR fixes #123456. > This PR fixes #123456.
> >
> try-job: x86_64-msvc > try-job: x86_64-msvc
> try-job: test-various > try-job: test-various
> try-job: `*-alt`
> ``` > ```
> >
> Each `try-job` directive must be on its own line. > Each `try-job` pattern must be on its own line.
> >
> 3. Run the prescribed try jobs with `@bors try`. As aforementioned, this > 3. Run the prescribed try jobs with `@bors try`. As aforementioned, this
> requires the user to either (1) have `try` permissions or (2) be delegated > requires the user to either (1) have `try` permissions or (2) be delegated