Skip to content

Commit ed458f5

Browse files
authored
Merge pull request #4442 from rust-lang/rustup-2025-07-04
Automatic Rustup
2 parents 10d7cfe + f9d850d commit ed458f5

File tree

2 files changed

+15
-2
lines changed

2 files changed

+15
-2
lines changed

src/tests/ci.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,8 +66,8 @@ kinds of builds (sets of jobs).
6666
### Pull Request builds
6767

6868
After each push to a pull request, a set of `pr` jobs are executed. Currently,
69-
these execute the `x86_64-gnu-llvm-X`, `x86_64-gnu-tools`, `mingw-check-1`, `mingw-check-2`
70-
and `mingw-check-tidy` jobs, all running on Linux. These execute a relatively short
69+
these execute the `x86_64-gnu-llvm-X`, `x86_64-gnu-tools`, `pr-check-1`, `pr-check-2`
70+
and `tidy` jobs, all running on Linux. These execute a relatively short
7171
(~40 minutes) and lightweight test suite that should catch common issues. More
7272
specifically, they run a set of lints, they try to perform a cross-compile check
7373
build to Windows mingw (without producing any artifacts) and they test the
@@ -148,6 +148,13 @@ for example `*msvc*` or `*-alt`. You can start at most 20 jobs in a single try b
148148
glob patterns, you might want to wrap them in backticks (`` ` ``) to avoid GitHub rendering
149149
the pattern as Markdown.
150150

151+
The job pattern needs to match one or more jobs defined in the `auto` or `optional` sections
152+
of [`jobs.yml`]:
153+
154+
- `auto` jobs are executed before a commit is merged into the `master` branch.
155+
- `optional` jobs are executed only when explicitly requested via a try build.
156+
They are typically used for tier 2 and tier 3 targets.
157+
151158
> **Using `try-job` PR description directives**
152159
>
153160
> 1. Identify which set of try-jobs you would like to exercise. You can

src/tests/minicore.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,12 @@ If you find a `core` item to be missing from the [`minicore`] stub, consider
3939
adding it to the test auxiliary if it's likely to be used or is already needed
4040
by more than one test.
4141

42+
## Staying in sync with `core`
43+
44+
The `minicore` items must be kept up to date with `core`. For consistent
45+
diagnostic output between using `core` and `minicore`, any `diagnostic`
46+
attributes (e.g. `on_unimplemented`) should be replicated exactly in `minicore`.
47+
4248
## Example codegen test that uses `minicore`
4349

4450
```rust,no_run

0 commit comments

Comments
 (0)