https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=lcnr/rustc-dev-guide 2025-08-14T04:23:07+00:00 2025-08-14T04:23:07+00:00 bors bors@rust-lang.org 2025-08-14T04:23:07+00:00 urn:sha1:2c1ac85679678dfe5cce7ea8037735b0349ceaf3 Enforce in bootstrap that clippy must have stage at least 1 This mostly piggybacks on the previous `x check` [rework](https://github.com/rust-lang/rust/pull/143048). The new "rules" follow the new staging logic. So `x clippy <foo>` lints `foo` using stage0 Clippy. `x clippy --stage 2 <foo>` lints `foo` using stage1 Clippy (which is built from in-tree sources). I had to fix some latent issues with `prepare_compiler_for_check` along the way. Checking `rustc_private` tools should now check less compiler crates (or rather not check compiler examples/tests/etc.), potentially speeding it up slightly. I also had to make some manual adjustments to `x clippy ci` so that it doesn't do needless work. r? `@jieyouxu` 2025-08-13T15:56:00+00:00 bors bors@rust-lang.org 2025-08-13T15:56:00+00:00 urn:sha1:f5b8a11fecf23cb669f6d1feae81aafc2930aeb9 Update to LLVM 21.1.0 rc3 2025-08-13T12:25:53+00:00 Nikita Popov npopov@redhat.com 2025-08-13T12:25:53+00:00 urn:sha1:1d44bbe3f49fcca50664cc8229b0f36e4c30a92e 2025-08-13T06:11:00+00:00 Jakub Beránek berykubik@gmail.com 2025-08-08T19:47:18+00:00 urn:sha1:27347831bd9d90db879fa4bf550f440217dcf81f 2025-08-12T21:06:10+00:00 bors bors@rust-lang.org 2025-08-12T21:06:10+00:00 urn:sha1:1553adfe6884a8f6c28f5a673d3e605535ee0113 Consolidate stage directories and group logs in bootstrap My post-stage-0-redesign bootstrap fixes aren't done yet, but I think that enough steps have been migrated to the new system that it makes sense to actually modify the directories on disk, and what gets printed when bootstrap runs, so that it actually corresponds to the new system. Before, the printed stages didn't always make sense. This PR: - Fixes the numbering of `stageN` directories in the build directory. It was not corresponding to the correct stages before; notice that I did not modify `bootstrap/README.md`, as it was essentially describing what happens after this PR (first commit). - Unifies all steps that output a build group to use the `Builder::msg` method. It's probably not the final stage, and some of the test steps might not be fully accurate yet, because I didn't fix test step numbering yet, but I think that it's a clear improvement from before, and now that everything uses the same method, we can easily make changes across the board, to ensure that it stays unified (second commit). r? `@jieyouxu` try-job: dist-x86_64-msvc try-job: dist-x86_64-linux 2025-08-12T16:39:09+00:00 Jakub Beránek berykubik@gmail.com 2025-08-12T16:39:09+00:00 urn:sha1:72b606db89c7d2ce76ea41ea80ec92e6320bf20f 2025-08-12T10:37:55+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-08-12T10:37:55+00:00 urn:sha1:1c38519319a72ab197c0820d2e61b3bfea7d08fc Document compiler and stdlib in stage1 in `pr-check-2` CI job This restores the original behavior pre-https://github.com/rust-lang/rust/pull/145011 (I thought that stage 2 makes more sense here, but it made the job ~30m slower, which is bad). Let's see what will be the "new" duration, it should be ~55 minutes. r? ```````@jieyouxu``````` 2025-08-11T15:39:52+00:00 Jakub Beránek berykubik@gmail.com 2025-08-11T14:17:43+00:00 urn:sha1:79a134ac89f1e5ff19f8fe3efa8f025695d684de 2025-08-11T12:16:56+00:00 bors bors@rust-lang.org 2025-08-11T12:16:56+00:00 urn:sha1:fce0e74720d199eb7839fdb51af35ac5226da178 Enable RUST_BACKTRACE=1 on CI We should really see the backtrace if something in bootstrap fails on CI. https://github.com/rust-lang/rust/pull/145011#issuecomment-3172664934 doesn't show many details. 2025-08-10T18:48:39+00:00 Jakub Beránek berykubik@gmail.com 2025-08-10T14:22:15+00:00 urn:sha1:3fde438cecc2650ca34b510fef992ad595229306 We should really see the backtrace if something in bootstrap fails on CI.