about summary refs log tree commit diff
path: root/src/ci
AgeCommit message (Collapse)AuthorLines
2024-11-06Auto merge of #132664 - matthiaskrgr:rollup-i27nr7i, r=matthiaskrgrbors-1/+0
Rollup of 5 pull requests Successful merges: - #131261 (Stabilize `UnsafeCell::from_mut`) - #131405 (bootstrap/codegen_ssa: ship llvm-strip and use it for -Cstrip) - #132077 (Add a new `wide-arithmetic` feature for WebAssembly) - #132562 (Remove the `wasm32-wasi` target from rustc) - #132660 (Remove unused errs.rs file) Failed merges: - #131721 (Add new unstable feature `const_eq_ignore_ascii_case`) r? `@ghost` `@rustbot` modify labels: rollup
2024-11-05Rollup merge of #132409 - MarcoIeni:ci-remove-linux-4c-large, r=KobzolMatthias Krüger-7/+9
CI: switch 7 linux jobs to free runners try-job: x86_64-gnu-aux try-job: x86_64-gnu-nopt try-job: x86_64-gnu-tools
2024-11-05CI: switch 7 linux jobs to free runnersMarcoIeni-7/+9
2024-11-03Remove the `wasm32-wasi` target from rustcAlex Crichton-1/+0
This commit is the final step in the journey of renaming the historical `wasm32-wasi` target in the Rust compiler to `wasm32-wasip1`. Various steps in this journey so far have been: * 2023-04-03: rust-lang/compiler-team#607 - initial proposal for this rename * 2024-11-27: rust-lang/compiler-team#695 - amended schedule/procedure for rename * 2024-01-29: rust-lang/rust#120468 - initial introduction of `wasm32-wasip1` * 2024-06-18: rust-lang/rust#126662 - warn on usage of `wasm32-wasi` * 2024-11-08: this PR - remove the `wasm32-wasi` target The full transition schedule is in [this comment][comment] and is summarized with: * 2024-05-02: Rust 1.78 released with `wasm32-wasip1` target * 2024-09-05: Rust 1.81 released warning on usage of `wasm32-wasi` * 2025-01-09: Rust 1.84 to be released without the `wasm32-wasi` target This means that support on stable for the replacement target of `wasm32-wasip1` has currently been available for 6 months. Users have already seen warnings on stable for 2 months about usage of `wasm32-wasi` and stable users have another 2 months of warnings before the target is removed from stable. This commit is intended to be the final step in this transition so the source tree should no longer mention `wasm32-wasi` except in historical reference to the older name of the `wasm32-wasip1` target. [comment]: https://github.com/rust-lang/rust/pull/120468#issuecomment-1977878747
2024-11-02Rollup merge of #132411 - MarcoIeni:ci-switch-to-free-runners, r=KobzolMatthias Krüger-1/+1
CI: switch dist-x86_64-musl to free runner try-job: dist-x86_64-musl
2024-11-01CI: switch dist-x86_64-musl to free runnerMarcoIeni-1/+1
2024-10-31Rollup merge of #132294 - tmandry:bump-fuchsia, r=lqdJubilee-1/+1
Bump Fuchsia r? `@Kobzol` try-job: x86_64-fuchsia https://fxbug.dev/376114512
2024-10-31Bump FuchsiaTyler Mandry-1/+1
2024-10-31Rollup merge of #132396 - ↵Matthias Krüger-2/+2
MarcoIeni:ci-use-free-runners-for-x86_64-gnu-tools-and-x86_64-rust-for-linux, r=Kobzol CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linux try-job: x86_64-gnu-tools try-job: x86_64-rust-for-linux
2024-10-31Rollup merge of #132316 - MarcoIeni:ci-free-runners-windows, r=Mark-SimulacrumMatthias Krüger-3/+3
CI: use free runners for 3 fast windows jobs try-job: dist-i686-msvc try-job: dist-i686-mingw try-job: dist-x86_64-mingw try-job: dist-x86_64-msvc-alt
2024-10-31CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linuxMarcoIeni-2/+2
2024-10-31CI: use free runners for 3 fast windows jobsMarcoIeni-3/+3
2024-10-29Rollup merge of #131375 - klensy:clone_on_ref_ptr, r=cjgillotJubilee-1/+2
compiler: apply clippy::clone_on_ref_ptr for CI Apply lint https://rust-lang.github.io/rust-clippy/master/index.html#/clone_on_ref_ptr for compiler, also see https://github.com/rust-lang/rust/pull/131225#discussion_r1790109443. Some Arc's can be misplaced with Lrc's, sorry. https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/enable.20more.20clippy.20lints.20for.20compiler.20.28and.5Cor.20std.29
2024-10-28split clippy task for library and compiler, so different lints can be enabledklensy-1/+2
2024-10-27Revert "ci update freebsd version proposal, freebsd 12 being eol."David Carlier-10/+10
This reverts commit 1239c81c145d2bfb96f32856f377cd741d5c7256. Fix GH-132185 revert for now until early next year/FreeBSD 13.3 becomes EOL.
2024-10-26Rollup merge of #132163 - claywilkinson:master, r=tmandryMatthias Krüger-30/+22
Update Fuchsia CI script for package serving This updates the "start" and "stop" methods of the test runner to use the standalone package server. r? `@tmandry`
2024-10-25Fix indentationTyler Mandry-2/+2
2024-10-25Update Fuchsia CI script for package servingClayton Wilkinson-30/+22
This updates the "start" and "stop" methods of the test runner to use the standalone package server.
2024-10-25Auto merge of #132148 - matthiaskrgr:rollup-c155tcy, r=matthiaskrgrbors-5/+0
Rollup of 3 pull requests Successful merges: - #132106 (Pass Ident by reference in ast Visitor) - #132130 (remove `change-id` from CI script) - #132137 (library: consistently use American spelling for 'behavior') r? `@ghost` `@rustbot` modify labels: rollup
2024-10-25Auto merge of #131917 - jieyouxu:rmake-clang, r=Kobzolbors-4/+4
Run the full stage 2 `run-make` test suite in `x86_64-gnu-debug` Run the full `run-make` test suite in the `x86_64-gnu-debug` CI job. This is currently the *only* CI job where `//@ needs-force-clang-based-test` will be satisfied, so some `run-make` tests will literally never be run otherwise. Before this PR, the CI job only ran `run-make` tests which contains the substring `clang` in its test name, which is both (1) a footgun because it's very easy to forget and (2) it masks tests that would otherwise fail (even failing to compile) because the test is skipped if doesn't have a `clang` in its test name. With the environment of `x86_64-gnu-debug`, two `run-make` tests failed before this PR: 1. `tests/run-make/issue-84395-lto-embed-bitcode/rmake.rs`: this was broken for a long time because `objcopy` in llvm bin tools was renamed to `llvm-objcopy`. This test was converted into a rmake.rs test, rather straight forward. 2. `tests/run-make/cross-lang-lto-riscv-abi/rmake.rs`: this was broken for a long time and never worked. The old version inspected human-readable output of `llvm-readobj --file-header` looking for substring `EF_RISCV_FLOAT_ABI_DOUBLE`, but the human-readable output will only contain something like `Flags: 0x5, RVC, double-float ABI`, hence it will never match. This test was fixed by instead using the `object` crate to actually decode the ELF headers looking for the specific `e_flags` based on reading the RISCV ELF psABI docs. This PR is best reviewed commit-by-commit, two commits setup the support library for functionality and two commits are for each of the failing `run-make` tests. I had to bump the `x86_64-gnu-debug` job to be ran with a runner with larger disk space. Part of #132034. try-job: x86_64-gnu-debug
2024-10-25Rollup merge of #132130 - onur-ozkan:remove-ci-change-id, r=KobzolMatthias Krüger-5/+0
remove `change-id` from CI script It's not necessary to set `change-id` for CI since https://github.com/rust-lang/rust/pull/130356.
2024-10-25Auto merge of #131207 - davidtwco:pac-ret-lto-test, r=Mark-Simulacrumbors-0/+61
ci: aarch64-gnu-debug job - Adds a new CI job which checks that the compiler builds with `--enable-debug` and tests that `needs-force-clang-based-tests` pass (where cross-language LTO is tested). - Add a test confirming that `-Zbranch-protection=pac-ret` and cross-language LTO work together. r? `@Mark-Simulacrum` try-job: aarch64-gnu-debug
2024-10-25remove `change-id` from CI scriptonur-ozkan-5/+0
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-24ci: add aarch64-gnu-debug jobDavid Wood-0/+61
Adds a new CI job which checks that the compiler builds with `--enable-debug` and tests that `needs-force-clang-based-tests` pass (where cross-language LTO is tested).
2024-10-23Rollup merge of #132058 - adetaylor:use-rust-next-in-ci, r=lqdLeón Orell Valerian Liehr-1/+1
CI: rfl: use rust-next temporary commit Commit c95bbb59a9b22f9b838b15d28319185c1c884329 within rust-next contains some changes required to be compatible with upcoming arbitraty self types work. Roll RFL CI forward to the latest rust-next to include that work. Related: https://github.com/rust-lang/rust/pull/130225 https://github.com/rust-lang/rust/issues/44874 r? ``@ojeda`` try-job: x86_64-rust-for-linux
2024-10-23CI: rfl: use rust-next temporary commitAdrian Taylor-1/+1
Commit c95bbb59a9b22f9b838b15d28319185c1c884329 within rust-next contains some changes required to be compatible with upcoming arbitraty self types work. Roll RFL CI forward to the latest rust-next to include that work. Related: https://github.com/rust-lang/rust/pull/130225 https://github.com/rust-lang/rust/issues/44874
2024-10-22Address review comments on wasm32v1-none targetGraydon Hoare-0/+1
2024-10-22ci: switch `x86_64-gnu-debug` to use a large disk runner许杰友 Jieyou Xu (Joe)-1/+3
Full stage 2 build + run-make with full debug info seems to overwhelm the standard 4c runner's storage capacity.
2024-10-22ci: run the full `run-make` test suite许杰友 Jieyou Xu (Joe)-3/+1
Instead of filtering `run-make` tests whose test names contain the `clang` substring.
2024-10-21Auto merge of #131570 - ehuss:update-xcode, r=Mark-Simulacrumbors-5/+5
(ci) Update macOS Xcode to 15 This updates the macOS builders to Xcode 15. The aarch64 images will be removing Xcode 14 and 16 very soon (https://github.com/actions/runner-images/issues/10703), so we will need to make the switch to continue operating. The linked issue also documents GitHub's new policy for how they will be updating Xcode in the future. Also worth being aware of is the future plans for x86 runners documented in https://github.com/actions/runner-images/issues/9255 and https://github.com/actions/runner-images/issues/10686, which will impact our future upgrade behaviors. I decided to also update the Xcode in the x86_64 runners, even though they are not being removed. It felt better to me to have all macOS runners on the same (major) version of Xcode. However, note that the x86_64 runners do not have the latest version of 15 (15.4), so I left them at 15.2 (which is currently the default Xcode of the runner). Xcode 15 was previously causing problems (see #121058) which seem to be resolved now. `@bjorn3` fixed the `invalid r_symbolnum` issue with cranelift. The issue with clang failing to link seems to be fixed, possibly by the update of the pre-built LLVM from 14 to llvm 15 in https://github.com/rust-lang/rust/pull/124850, or an update in our source version of LLVM. I have run some try builds and at least LLVM seems to build (I did not run any tests). Closes #121058
2024-10-21Auto merge of #120869 - devnexen:update_fbsd_ci, r=Mark-Simulacrumbors-11/+11
ci update freebsd version proposal, freebsd 12 being eol raising to the lowest still active supported freebsd version. From 13.1 (already eol too), freebsd introduces a cpu affinity layer with linux. It also introduces a api compatible copy_file_range which can be used like its linux's counterpart. The former is essential to build https://github.com/rust-lang/rust/pull/120589, therefore breaks the backward compatibility with the previous FreeBSD releases. Blocked on https://github.com/rust-lang/rust/issues/130465
2024-10-18Auto merge of #131887 - jieyouxu:rollup-ftik4ni, r=jieyouxubors-0/+4
Rollup of 9 pull requests Successful merges: - #130136 (Partially stabilize const_pin) - #131755 (Regression test for AVR `rjmp` offset) - #131774 (Add getentropy for RTEMS) - #131802 (Dont ICE when computing coverage of synthetic async closure body) - #131809 (Fix predicate signatures in retain_mut docs) - #131858 (Remove outdated documentation for `repeat_n`) - #131866 (Avoid use imports in `thread_local_inner!`) - #131874 (Default to the medium code model on OpenHarmony LoongArch target) - #131877 (checktools.sh: add link to issue for more context about disabled Miri tests) r? `@ghost` `@rustbot` modify labels: rollup
2024-10-18checktools.sh: add link to issue for more context about disabled Miri testsRalf Jung-0/+4
2024-10-18Auto merge of #131362 - Kobzol:ci-free-runners-linux-4c, r=Mark-Simulacrumbors-7/+12
CI: use free runners for 4-core Linux jobs It looks like the [free runners](https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories) already have the same spec as the `4c` custom "large" runner (4 cores, 16 GiB of memory, Ubuntu 20.04). try-job: arm-android try-job: armhf-gnu try-job: dist-aarch64-linux try-job: dist-android try-job: dist-arm-linux try-job: dist-armhf-linux try-job: dist-armv7-linux try-job: dist-i586-gnu-i586-i686-musl try-job: dist-i686-linux try-job: dist-loongarch64-linux try-job: dist-loongarch64-musl try-job: dist-ohos try-job: dist-powerpc-linux try-job: dist-powerpc64-linux try-job: dist-powerpc64le-linux try-job: dist-riscv64-linux try-job: dist-s390x-linux try-job: dist-various-1 try-job: dist-various-2 try-job: dist-x86_64-freebsd try-job: dist-x86_64-illumos try-job: dist-x86_64-netbsd try-job: mingw-check try-job: test-various try-job: x86_64-gnu try-job: x86_64-gnu-stable try-job: x86_64-gnu-aux try-job: x86_64-gnu-debug try-job: x86_64-gnu-nopt
2024-10-15Make fuchsia-test-runner.py compatible with new JSON output from llvm-readelfc6c7-11/+31
[A recent commit in LLVM](https://github.com/llvm/llvm-project/commit/ab930ee7cad8b8bf7968bb8d0c0d72524e2313c4) modified the JSON output of LLVM. The LLVM change renamed "Notes" to "NoteSections" and inserted a new "Notes" key nested under each "NoteSection". This change shores up exceptions around reading the JSON output of llvm-readelf and reads from "NoteSections" instead of the non-existent "Notes".
2024-10-14Rollup merge of #131533 - workingjubilee:update-emscripten-version, r=KobzolMatthias Krüger-2/+2
emscripten: Use the latest emsdk 3.1.68 This should fix our precompiled std being unsound in `std::fs` code. Should resolve #131467 I hope.
2024-10-13CI: use free runners for 4core Linux jobsJakub Beránek-7/+12
2024-10-12Rollup merge of #131358 - onur-ozkan:129528, r=Mark-SimulacrumTrevor Gross-0/+36
force "HEAD" for non-CI and `git_upstream_merge_base` for CI environment When rust-lang/rust is configured as remote, some of the git logic (for tracking changed files) that uses get_closest_merge_commit starts to produce annoying results as the upstream branch becomes outdated quickly (since it isn't updated with git pull). We can rely on HEAD for non-CI environments as we specifically treat bors commits as merge commits, which also exist on upstream. As for CI environments, we should use `git_upstream_merge_base` to correctly track modified files as bors commits may be in `HEAD` but not yet on the upstream remote. This is also an alternative fix for https://github.com/rust-lang/rust/issues/129528 since https://github.com/rust-lang/rust/pull/131331 reverts the previous fix attempts.
2024-10-12Rollup merge of #131334 - heiher:loong-sanitizers, r=Mark-SimulacrumTrevor Gross-0/+2
Enable sanitizers for loongarch64-unknown-* Enable sanitizers for `loongarch64-unknown-linux-{gnu,musl,ohos}` targets.
2024-10-12add new CI step: "setup upstream remote"onur-ozkan-0/+36
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-11(ci) Update macOS to Xcode 15Eric Huss-5/+5
2024-10-11move dummy commit logic into x86_64-gnu-llvm-18onur-ozkan-17/+19
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-10emscripten: Use the latest emsdk 3.1.68Jubilee Young-2/+2
This should fix our precompiled std being unsound in `std::fs` code.
2024-10-08Fix quotation marks around debug line in `src/ci/run.sh`Josh Stone-1/+1
Without this change, the markdown-style backticks are treated as a shell command substitution, which fails like so: /checkout/src/ci/run.sh: line 58: DISABLE_CI_RUSTC_IF_INCOMPATIBLE: command not found debug: configured.
2024-10-08Auto merge of #131412 - matthiaskrgr:rollup-478o6h6, r=matthiaskrgrbors-1/+1
Rollup of 3 pull requests Successful merges: - #131378 (CI: rfl: move job forward to Linux v6.12-rc2) - #131400 (Simplify the compiletest directives for ignoring coverage-test modes) - #131408 (Remove unneeded argument of `LinkCollector::verify_disambiguator`) r? `@ghost` `@rustbot` modify labels: rollup
2024-10-08force `download-rustc=if-unchanged` for x86_64-gnu-tools runneronur-ozkan-0/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08fix `ci_rustc_if_unchanged_logic` testonur-ozkan-2/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08handle CI rustc incompatible runnersonur-ozkan-0/+6
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08disable download-rustc on x86_64-gnu-integrationonur-ozkan-0/+4
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08disable read-only mode in mingw-check image for merge pipelineonur-ozkan-0/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 20:44:43 +0000