about summary refs log tree commit diff
path: root/src/ci
AgeCommit message (Collapse)AuthorLines
2025-06-03run `x check` on mingw-check-2onur-ozkan-0/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-06-03Use 4-core large disk runner for the alt jobJakub Beránek-11/+16
2025-06-02Auto merge of #141912 - Kobzol:rollup-wurlnsx, r=Kobzolbors-1/+1
Rollup of 5 pull requests Successful merges: - rust-lang/rust#141767 (ci: use free runner for aarch64-gnu-llvm-19-1 PR job) - rust-lang/rust#141858 (Fix typo in `StructuralPartialEq` docs) - rust-lang/rust#141865 (Optionally don't steal the THIR) - rust-lang/rust#141874 (add f16_epsilon and f128_epsilon diagnostic items) - rust-lang/rust#141904 (test-float-parse: apply `cfg(not(bootstrap))`) r? `@ghost` `@rustbot` modify labels: rollup
2025-06-02Rollup merge of #141767 - marcoieni:free-pr-job, r=KobzolJakub Beránek-1/+1
ci: use free runner for aarch64-gnu-llvm-19-1 PR job
2025-06-02Fix `create-docs-artifacts.sh` with new borsJakub Beránek-1/+2
2025-06-02Fix citool tests when executed ocallyJakub Beránek-0/+2
They couldn't be executed locally before due to some additional environment reads.
2025-06-02Auto merge of #119899 - onur-ozkan:redesign-stage0-std, ↵bors-25/+61
r=albertlarsan68,jieyouxu,mark-simulacrum,kobzol,jyn514,Noratrieb,WaffleLapkin,RalfJung,bjorn3 redesign stage 0 std ### Summary **Blog post: https://blog.rust-lang.org/inside-rust/2025/05/29/redesigning-the-initial-bootstrap-sequence/** This PR changes how bootstrap builds the stage 1 compiler by switching to precompiled stage 0 standard library instead of building the in-tree one. The goal was to update bootstrap to use the beta standard library at stage 0 rather than compiling it from source (see the motivation at https://github.com/rust-lang/compiler-team/issues/619). Previously, to build a stage 1 compiler bootstrap followed this path: ``` download stage0 compiler -> build in-tree std -> compile stage1 compiler with in-tree std ``` With this PR, the new path is: ``` download stage0 compiler -> compile stage1 compiler with precompiled stage0 std ``` This also means that `cfg(bootstrap)`/`cfg(not(bootstrap))` is no longer needed for library development. ### Building "library" Since stage0 `std` is no longer in-tree `x build/test/check library --stage 0` is now no-op. The minimum supported stage to build `std` is now 1. For the same reason, default stage values in the library profile is no longer 0. Because building the in-tree library now requires a stage1 compiler, I highly recommend library developers to enable `download-rustc` to speed up compilation time. <hr> **Blog post: https://blog.rust-lang.org/inside-rust/2025/05/29/redesigning-the-initial-bootstrap-sequence/** If you encounter a bug or unexpected results please open a topic in the [#t-infra/bootstrap](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap) Zulip channel or create a [bootstrap issue](https://github.com/rust-lang/rust/issues/new?template=bootstrap.md). (Review thread: https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Review.20thread.3A.20stage.200.20redesign.20PR/with/508271433) ~~Blocked on https://github.com/rust-lang/rust/pull/122709~~ try-job: dist-x86_64-linux try-job: `x86_64-msvc*` try-job: `x86_64-apple-*` try-job: `aarch64-apple` try-job: x86_64-gnu try-job: `x86_64-gnu-llvm*`
2025-06-01ci: switch `x86_64-msvc-{1,2}` back to Windows Server 2025 imagesJieyou Xu-8/+2
New Windows Server 2025 images have been released (20250527).
2025-06-01Rollup merge of #141277 - RalfJung:miri-ci, r=oli-obkJacob Pratt-4/+6
Miri CI: test aarch64-apple-darwin in PRs instead of the x86_64 target The aarch64 target is more important, and also this ensures we cover all main architectures (x86_64, i686, aarch64) in PR CI.
2025-05-31Rollup merge of #141646 - jieyouxu:distcheck, r=Mark-SimulacrumMatthias Krüger-0/+12
Document what `distcheck` is intended to exercise Or at least attempt to. Closes rust-lang/rust#141387. cc `@marcoieni` (re. [#t-infra/bootstrap > Speed up distcheck](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Speed.20up.20distcheck/with/520208870)) r? `@Mark-Simulacrum` (as you may have some clues about if this is accurate)
2025-05-30Do not run PGO/BOLT in x64 Linux alt buildsJakub Beránek-8/+31
Signed-off-by: Jakub Beránek <berykubik@gmail.com>
2025-05-30fix fs bug on CI and update ming-check-1 Dockerfileonur-ozkan-0/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-30split `mingw-check` into twoonur-ozkan-24/+59
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-30use stage 1 for std on CIonur-ozkan-6/+6
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-30ci: use free runner for aarch64-gnu-llvm-19-1 PR jobMarcoIeni-1/+1
2025-05-30Rollup merge of #141749 - ↵Matthias Krüger-5/+0
Noratrieb:RUSTC_ACTUALLY_DO_NOT_RETRY_LINKER_ON_SEGFAULT, r=petrochenkov Remove RUSTC_RETRY_LINKER_ON_SEGFAULT hack It looks like this was added in rust-lang/rust#40422 6 years ago because of issues with the MacOS linker. MacOS got a new linker in the meantime, so that should probably be resolved now. Hopefully. r? petrochenkov
2025-05-30build dist for x86_64-pc-solaris and sparcv9-sun-solarisPetr Sumbera-169/+280
2025-05-29Remove RUSTC_RETRY_LINKER_ON_SEGFAULT hackNoratrieb-5/+0
It looks like this was added 6 years ago because of issues with the MacOS linker. MacOS got a new linker in the meantime, so that should probably be resolved now. Hopefully.
2025-05-29Rollup merge of #141705 - GuillaumeGomez:eslint-tidy, r=KobzolGuillaume Gomez-5/+10
Add eslint as part of `tidy` run Rustdoc uses `eslint` to run lints on the JS files. Currently you need to run it by hand since it's not part of any `x.py` command. This PR makes it part of `test tidy`. However, to prevent having all rust developers to install `npm` and `eslint`, I made it optional: if `eslint` is not installed, then the check is simply skipped (but will tell that it is being skipped). The second commit removes the manual checks from the docker file since `eslint` is run as part of tidy. cc `@lolbinarycat,` [#t-rustdoc > eslint seems to only be run in CI](https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/eslint.20seems.20to.20only.20be.20run.20in.20CI/with/520761477)
2025-05-29Fix npm install errorGuillaume Gomez-3/+2
2025-05-29Centralize the eslint version between tidy and dockerGuillaume Gomez-1/+3
2025-05-29Install eslint in host-x86_64 DockerfileGuillaume Gomez-0/+7
2025-05-29Auto merge of #141717 - jhpratt:rollup-neu8nzl, r=jhprattbors-1/+3
Rollup of 4 pull requests Successful merges: - rust-lang/rust#138285 (Stabilize `repr128`) - rust-lang/rust#139994 (add `CStr::display`) - rust-lang/rust#141571 (coretests: extend and simplify float tests) - rust-lang/rust#141656 (CI: Add cargo tests to aarch64-apple-darwin) Failed merges: - rust-lang/rust#141430 (remove `visit_clobber` and move `DummyAstNode` to `rustc_expand`) - rust-lang/rust#141636 (avoid some usages of `&mut P<T>` in AST visitors) r? `@ghost` `@rustbot` modify labels: rollup
2025-05-29Rollup merge of #141656 - ehuss:cargo-aarch64-macos, r=marcoieni,jieyouxuJacob Pratt-1/+3
CI: Add cargo tests to aarch64-apple-darwin This adds running of cargo's tests to the aarch64-apple-darwin job. The reason for this is that tier-1 targets are ostensibly supposed to run tests for host tools, but we are not doing that here. We do have fairly good coverage in Cargo's CI, but we don't cover the beta or stable branches here. I think it would be good to have a fallback here. I think this should only add about 7 minutes of CI time, but I have not measured it. The current job is about 1.5 hours. In summary of the tier-1 targets: | Target | rust-lang/cargo | rust-lang/rust | |--------|-----------------|----------------| | aarch64-apple-darwin | stable/nightly | ❌ (this PR) | | aarch64-unknown-linux-gnu | stable/nightly | ✓ | | x86_64-apple-darwin | nightly | ❌ | | x86_64-pc-windows-gnu | nightly | ❌ | | x86_64-pc-windows-msvc | stable | ✓ | | x86_64-unknown-linux-gnu | stable/beta/nightly | ✓ | | i686-pc-windows-msvc | ❌ | ❌ | | i686-unknown-linux-gnu | ❌ | ❌ | try-job: aarch64-apple
2025-05-29Rollup merge of #141643 - marcoieni:codebuild-check, r=KobzolJacob Pratt-1/+67
ci: verify that codebuild jobs use ghcr.io
2025-05-28Remove checks that are run with `tidy`Guillaume Gomez-3/+0
2025-05-28Auto merge of #141576 - marcoieni:pr-free-runners-aarch, r=Kobzolbors-3/+71
ci: move tests from x86_64-gnu-llvm-19 job to aarch64
2025-05-28Auto merge of #141501 - marcoieni:dist-x86_64-linux-codebuild-again, r=Kobzolbors-2/+2
ci: move dist-x86_64-linux job to codebuild
2025-05-28ci: verify that codebuild jobs use ghcr.ioMarcoIeni-1/+67
2025-05-27Rollup merge of #141591 - marcoieni:fix-llvm-test-coverage, r=KobzolTrevor Gross-2/+2
ci: fix llvm test coverage try-job: x86_64-gnu-llvm-19-1 try-job: x86_64-gnu-llvm-20-1
2025-05-27CI: Add cargo tests to aarch64-apple-darwinEric Huss-1/+3
This adds running of cargo's tests to the aarch64-apple-darwin job. The reason for this is that tier-1 targets are ostensibly supposed to run tests for host tools, but we are not doing that here. We do have fairly good coverage in Cargo's CI, but we don't have much coverage of beta or stable. I think it would be good to have a fallback here.
2025-05-27distcheck: document what distcheck is intended to exerciseJieyou Xu-0/+12
2025-05-27ci: use ghcr registry for x86_64-gnu-tools jobMarcoIeni-1/+1
2025-05-26ci: move tests from x86_64-gnu-llvm-19 job to aarch64MarcoIeni-3/+71
2025-05-26ci: fix llvm test coverageMarcoIeni-2/+2
2025-05-26ci: move dist-x86_64-linux job to codebuildMarcoIeni-2/+2
2025-05-26Rollup merge of #141502 - marcoieni:x86_64-gnu-tools-codebuild, r=KobzolJacob Pratt-1/+1
ci: move PR job x86_64-gnu-tools to codebuild
2025-05-24Rollup merge of #141487 - GuillaumeGomez:update-askama, r=notriddleGuillaume Gomez-7/+7
Update askama to `0.14.0` [Askama 0.14.0 release notes](https://github.com/askama-rs/askama/releases/tag/v0.14.0) Just one change needed for a filter in rustdoc. r? ```@notriddle```
2025-05-24ci: move PR job x86_64-gnu-tools to codebuildMarcoIeni-1/+1
2025-05-24Update `askama` version to `0.14.0` in `citool`Guillaume Gomez-7/+7
2025-05-23Remove #![feature(let_chains)] from libcoreest31-1/+2
2025-05-22Auto merge of #141388 - Kobzol:x64-github-runner, r=marcoienibors-1/+1
Move `dist-x86_64-linux` CI job to GitHub temporarily To make it easier to migrate off the `rust-lang-ci/rust` repository. r? `@marcoieni`
2025-05-22Rollup merge of #141382 - marcoieni:distcheck-free-x86, r=KobzolMatthias Krüger-1/+1
ci: convert distcheck to free runner try-job: x86_64-gnu-distcheck
2025-05-22Rollup merge of #141355 - marcoieni:citool-errors, r=KobzolMatthias Krüger-4/+10
ci: improve citool job db errors
2025-05-22Move `dist-x86_64-linux` CI job to GitHub temporarilyJakub Beránek-1/+1
To make it easier to migrate off the `rust-lang-ci/rust` repository.
2025-05-22ci: convert distcheck to free runnerMarcoIeni-1/+1
2025-05-21ci: improve citool job db errorsMarcoIeni-4/+10
2025-05-21Rollup merge of #141280 - Kobzol:docker-rust-lang-cache, r=marcoieniMatthias Krüger-3/+2
Use Docker cache from the current repository This is needed to make the cache work after moving CI from the `rust-lang-ci` org to `rust-lang`. Shouldn't be merged until we actually move bors. Context: https://github.com/rust-lang/infra-team/issues/188 r? `@marcoieni`
2025-05-21Rollup merge of #140994 - onur-ozkan:cc2ar-removal, r=albertlarsan68Matthias Krüger-0/+3
replace `cc_detect::cc2ar` with `cc::try_get_archiver` ~~Awaiting new release of [cc](https://crates.io/crates/cc) version with https://github.com/rust-lang/cc-rs/pull/1456 to bump the version.~~ ~~Blocked by https://github.com/rust-lang/cc-rs/pull/1456.~~ Kind a self-explanatory. try-job: dist-android
2025-05-21Rollup merge of #141078 - marcoieni:split-dist-arm-linux, r=KobzolMatthias Krüger-10/+55
ci: split dist-arm-linux job try-job: `dist-arm-linux-*`