about summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
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-8/+50
ci: split dist-arm-linux job try-job: `dist-arm-linux-*`
2025-05-21add missing PATHonur-ozkan-0/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-05-20ci: split powerpc64le-linux jobMarcoIeni-6/+58
2025-05-20Use Docker cache from the current repositoryJakub Beránek-3/+2
This is needed to make the cache work after moving CI from the `rust-lang-ci` org to `rust-lang`.
2025-05-20Miri CI: test aarch64-apple-darwin in PRs instead of the x86_64 targetRalf Jung-3/+3
2025-05-18ci: split dist-arm-linux jobMarcoIeni-8/+50
2025-05-17Rollup merge of #140917 - RalfJung:checktools, r=WaffleLapkinMatthias Krüger-1/+1
checktools.sh: fix bashism Follow-up to https://github.com/rust-lang/rust/pull/140903. Turns out `tests/{pass,panic}` only properly expands in bash, not in dash. :/ r? `@WaffleLapkin`
2025-05-15ci: split the dist-ohos jobMarcoIeni-18/+106
2025-05-11checktools.sh: fix bashismRalf Jung-1/+1
2025-05-10test intrinsic fallback bodies with MiriRalf Jung-0/+8
2025-05-06Rollup merge of #140135 - GuillaumeGomez:sidebars-image, r=rustdocGuillaume Gomez-1/+1
Unify sidebar buttons to use the same image Part of https://github.com/rust-lang/rust/issues/139832. The source sidebar looks like this with the new image: ![image](https://github.com/user-attachments/assets/df4fee52-fb71-4794-91b7-3afc6d2aab70) You can test it [here](https://rustdoc.crud.net/imperio/sidebar-images/src/foo/foo.rs.html). r? `@notriddle`
2025-04-29CI: rfl: move job forward to Linux v6.15-rc4Miguel Ojeda-1/+1
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-04-28Rollup merge of #140349 - marcoieni:codebuild-linux-large-runners, r=KobzolGuillaume Gomez-1/+1
ci: use aws codebuild for the `dist-x86_64-linux` job try-job: dist-x86_64-linux
2025-04-28ci: use aws codebuild for the `dist-x86_64-linux` jobMarcoIeni-1/+1
2025-04-27CI: docker: host-x86_64: test-various: uefi_qemu_test: Update r-efiAyush Singh-4/+4
- Update r-efi to 5.2.0 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
2025-04-25Rollup merge of #140148 - marcoieni:ci-aws-codebuild, r=KobzolMatthias Krüger-2/+2
CI: use aws codebuild for job dist-arm-linux try-job: dist-arm-linux
2025-04-23Update browser-ui-test version to 0.20.6Guillaume Gomez-1/+1
2025-04-23CI: use aws codebuild for job dist-arm-linuxMarcoIeni-2/+2
2025-04-20Remove the `add_dummy_commit.sh` hackJakub Beránek-25/+2
The new git tests should be enough to check this scenario. We should ideally not be creating dummy commits on CI.
2025-04-14ci: add runners for vanilla LLVM 20Josh Stone-0/+69
Ubuntu 25.04 has `llvm-20` packages that we can start testing with. The `Dockerfile` is otherwise the same as the `llvm-18`/`19` runners.
2025-04-08Rollup merge of #139386 - onur-ozkan:configurable-compiletest-libtest, ↵Stuart Cook-0/+2
r=jieyouxu,kobzol make it possible to use stage0 libtest on compiletest With https://github.com/rust-lang/rust/pull/119899, building the library tree will require a stage 1 compiler. This is because `compiletest` is defined as a `ToolStd` (since https://github.com/rust-lang/rust/pull/68019) in order to use the in-tree library. As a result, https://github.com/rust-lang/rust/pull/119899 makes certain development workflows more difficult as changes on the compiler tree will now require recompiling `compiletest` each time. This PR allows switching `ToolStd` to `ToolBootstrap` with a simple boolean option in `bootstrap.toml` to allow `compiletest` to use the stage 0 `libtest` instead. The changes under `src/ci` are clearly intended to make sure that `compiletest` doesn't break during future bootstrap beta bumps.
2025-04-07enable in-tree std on some runnersonur-ozkan-0/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-04-05Update the minimum external LLVM to 19Josh Stone-73/+5
2025-04-02Demote i686-pc-windows-gnu to Tier 2Noratrieb-2/+1
In accordance with RFC 3771. I also added a stub doc page for the target and renamed the windows-gnullvm page for consistency.
2025-03-27Add CI metadata to bootstrap metricsJakub Beránek-0/+2
This will allow us to provide links to CI workflows, jobs and summaries in the post-merge analysis report.
2025-03-21Disable CI mode when checking default bootstrap profilesJakub Beránek-1/+2
2025-03-16Auto merge of #137011 - LuuuXXX:promote-ohos-with-host-tools, r=Amanieubors-5/+27
Promote ohos targets to tier2 with host tools. ### What does this PR try to resolve? Try to promote the following [[Tier 2 without Host Tools](https://doc.rust-lang.org/rustc/platform-support.html#tier-2-without-host-tools)](https://doc.rust-lang.org/rustc/platform-support.html#tier-2-without-host-tools) targets to [[Tier 2 with Host Tools](https://doc.rust-lang.org/rustc/platform-support.html#tier-2-with-host-tools)](https://doc.rust-lang.org/rustc/platform-support.html#tier-2-with-host-tools): - `aarch64-unknown-linux-ohos` - `armv7-unknown-linux-ohos` - `x86_64-unknown-linux-ohos` ### More Information? see MCP: https://github.com/rust-lang/compiler-team/issues/811 ### Blockage to be solved? - [x] Submit an MCP - [x] Submit code of promote ohos targets - [x] Resolve related dependencies （`measureme`） The modified code of the measureme has been merged （see https://github.com/rust-lang/measureme/pull/238）. [done] The new version will was released (https://github.com/rust-lang/measureme/pull/240). [done]
2025-03-15Auto merge of #137665 - Kobzol:update-sccache, r=marcoienibors-2/+2
Update sccache to 0.10.0 This time, does it also for Windows and macOS. This unifies the sccache version across all OSes that we use. r? `@ghost` try-job: dist-aarch64-apple try-job: dist-x86_64-apple try-job: dist-x86_64-msvc try-job: dist-x86_64-msvc-alt try-job: dist-i686-msvc try-job: dist-aarch64-msvc try-job: dist-x86_64-linux try-job: dist-x86_64-netbsd
2025-03-15Rollup merge of #138507 - Kobzol:netbsd-mirror, r=Mark-SimulacrumLeón Orell Valerian Liehr-17/+9
Mirror NetBSD sources Should avoid issues with NetBSD servers. r? ``@Mark-Simulacrum`` try-job: `*netbsd*`
2025-03-15Rollup merge of #138451 - Kobzol:gcc-ci-build-gcc, r=GuillaumeGomezLeón Orell Valerian Liehr-1/+3
Build GCC on CI with GCC, not Clang It seems that GCC built with Clang misbehaves. I have tested that cg_gcc tests [pass](https://github.com/rust-lang/rust/actions/runs/13842365913/job/38732750617?pr=138451) on CI with a downloaded GCC that was built in this way. Prerequisite for https://github.com/rust-lang/rust/pull/138395. r? ```@ghost```
2025-03-14Mirror NetBSD sourcesJakub Beránek-17/+9
2025-03-14Rollup merge of #138487 - Kobzol:fix-doc-url-docker, r=marcoieniLeón Orell Valerian Liehr-0/+1
Pass `CI_JOB_DOC_URL` to Docker Fix-up for https://github.com/rust-lang/rust/pull/136911. I always forget to pass new environment variables to Docker images.. :man_facepalming: r? `@marcoieni` try-job: x86_64-fuchsia
2025-03-14Remove `RUN_CHECK_WITH_PARALLEL_QUERIES`Jakub Beránek-4/+0
It is useless after the removal of the parallel compiler configuration.
2025-03-14Pass `CI_JOB_DOC_URL` to DockerJakub Beránek-0/+1
2025-03-13Use GCC for building GCCJakub Beránek-1/+3
2025-03-12Update sccache to 0.10.0Jakub Beránek-2/+2
This time, does it also for Windows and macOS.
2025-03-06remove zip file in /tmp to save some space and use large runnerLuuuXXX-0/+1
2025-03-04Rollup merge of #137947 - Kobzol:fix-rfl, r=marcoieniJubilee-10/+8
Do not install rustup on Rust for Linux job Trying to fix the RfL job after the recent rustup update. r? ``@ghost`` try-job: x86_64-rust-for-linux
2025-03-04Rollup merge of #137667 - Kobzol:gcc-dist-build, r=onur-ozkanJubilee-1/+1
Add `dist::Gcc` build step This PR adds a `dist:Gcc` bootstrap step to distribute a prebuilt `libgccjit.so` from CI on x64 Linux. With primed sccache, the build takes ~4 minutes on CI, and produces a 50 MiB archive. I want to land this before adding something akin to `[gcc] download-ci-gcc = true`, to already have the artifacts available on CI, to make it easier to setup the download merge-base logic. r? ``@ghost``
2025-03-04add support for extend rust tools and sanitizerLuuuXXX-1/+4
2025-03-04Revert "add fix for full tools and sanitizer"LuuuXXX-4/+1
This reverts commit 6efacfb7a59ebde2620398861713fae136060a04.
2025-03-04add fix for full tools and sanitizerLuuuXXX-1/+4
2025-03-04promote ohos targets to tier to with host toolsLuuuXXX-4/+22
2025-03-03Do not use rustup to build Rust for LinuxJakub Beránek-10/+8
2025-03-03Fix docker run-local docsEric Huss-2/+2
2025-03-02Auto merge of #136864 - Kobzol:citool, r=marcoienibors-3/+3
Rewrite the `ci.py` script in Rust It would seem that I would learn by now that any script written in Python will become unmaintainable sooner or later, but alas.. r? `@marcoieni` try-job: aarch64-gnu try-job: dist-x86_64-linux-alt try-job: x86_64-msvc-ext2 Fixes: https://github.com/rust-lang/rust/issues/137013
2025-02-28Build GCC on the Linux x64 dist runnerJakub Beránek-1/+1
2025-02-26Auto merge of #136921 - Kobzol:gcc-build, r=onur-ozkanbors-46/+1
Build GCC on CI Previously, we have downloaded a specific commit of GCC and prebuilt it inside Docker using the `build-gccjit.sh` script. This PR removes that scripts and uses the bootstrap GCC step. This allows us to use the `src/gcc` submodule for determining which GCC should be built, and it also moves the logic closer to LLVM, which is also built by bootstrap. A few things to note: - The `sccache` option is currently in the `llvm` block, so the GCC build uses `llvm.ccache`, which is a bit weird :) We could either add `gcc.ccache`, or (what I think would be better) to just move `ccache` to the `build` section, as I don't think that it will be necessary to use ccache for LLVM, but not for GCC. - When the GCC codegen backend is built, it needs to depend on a step that first builds GCC. This is currently done in a hacky way. The proper solution is to create a separate step for the GCC codegen backend, but that is a larger change. Let me know what you think. r? `@onur-ozkan` try-job: i686-msvc-1 try-job: x86_64-mingw-1
2025-02-25Rollup merge of #137539 - GuillaumeGomez:copy-content-tests, r=notriddleLeón Orell Valerian Liehr-1/+1
Add rustdoc-gui regression test for #137082 Fixes https://github.com/rust-lang/rust/issues/137082. Added new commands in `browser-ui-test` allowing us to add a regression test for #137082 and also another to copy code examples content. r? `@notriddle`
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-10 13:52:45 +0000