Skip to content

Commit 109d8fb

Browse files
committed
sembr src/tests/ci.md
1 parent aa6871c commit 109d8fb

1 file changed

Lines changed: 5 additions & 8 deletions

File tree

src/tests/ci.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,15 @@ The primary goal of our CI system is to ensure that the `main` branch of
66
From a high-level point of view, when you open a pull request at
77
`rust-lang/rust`, the following will happen:
88

9-
- A small [subset](#pull-request-builds) of tests and checks are run after each
10-
push to the PR.
9+
- A small [subset](#pull-request-builds) of tests and checks are run after each push to the PR.
1110
This should help catch common errors.
1211
- When the PR is approved, the [bors] bot enqueues the PR into a [merge queue].
1312
- Once the PR gets to the front of the queue, bors will create a merge commit
1413
and run the [full test suite](#auto-builds) on it.
1514
The merge commit either contains only one specific PR or it can be a ["rollup"](#rollups) which
1615
combines multiple PRs together, to reduce CI costs and merge delays.
17-
- Once the whole test suite finishes, two things can happen. Either CI fails
18-
with an error that needs to be addressed by the developer, or CI succeeds and
16+
- Once the whole test suite finishes, two things can happen.
17+
Either CI fails with an error that needs to be addressed by the developer, or CI succeeds and
1918
the merge commit is then pushed to the `main` branch.
2019

2120
If you want to modify what gets executed on CI, see [Modifying CI jobs](#modifying-ci-jobs).
@@ -303,8 +302,7 @@ This is worth it because these release artifacts:
303302

304303
- Allow perf testing even at a later date.
305304
- Allow bisection when bugs are discovered later.
306-
- Ensure release quality since if we're always releasing, we can catch problems
307-
early.
305+
- Ensure release quality since if we're always releasing, we can catch problems early.
308306

309307
### Rollups
310308

@@ -449,8 +447,7 @@ If you want to determine which `bootstrap.toml` settings are used in CI for a
449447
particular job, it is probably easiest to just look at the build log.
450448
To do this:
451449

452-
1. Go to
453-
<https://github.com/rust-lang/rust/actions?query=branch%3Aauto+is%3Asuccess>
450+
1. Go to <https://github.com/rust-lang/rust/actions?query=branch%3Aauto+is%3Asuccess>
454451
to find the most recently successful build, and click on it.
455452
2. Choose the job you are interested in on the left-hand side.
456453
3. Click on the gear icon and choose "View raw logs"

0 commit comments

Comments
 (0)