about summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
2024-12-04Reformat Python code with `ruff`Jakub Beránek-91/+126
2024-12-03CI: rfl: move job forward to Linux v6.13-rc1Miguel Ojeda-2/+2
Linux v6.13-rc1 contains commit 28e848386b92 ("rust: block: fix formatting of `kernel::block::mq::request` module"), which in turn contains commit c95bbb59a9b2 ("rust: enable arbitrary_self_types and remove `Receiver`"), which is why we had a hash rather than a tag. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-12-03CI: use free runners for i686-gnu jobsMarcoIeni-22/+26
2024-11-28Bump unsupported `ubuntu` CI images to 24.04 LTSrami3l-5/+6
2024-11-25Run the license-metadata check in CI.Jonathan Pallant-0/+1
This will tell you if license-metadata.json is out of date.
2024-11-23ci: don't force CI rustc for `x86_64-gnu-tools`Jieyou Xu-1/+4
CI alt rustc builds do not have rustc debug assertions currently.
2024-11-17Auto merge of #132646 - jieyouxu:liberate-aarch64-gnu-debug, r=Kobzolbors-1/+1
Liberate `aarch64-gnu-debug` from the shackles of `--test-args=clang` ### Changes - Drop `--test-args=clang` from `aarch64-gnu-debug` so run-make tests that are `//@ needs-force-clang-based-tests` no longer only run if their test name contains `clang` (which is a very cool footgun). - Reorganize run-make-suport library slightly to accommodate a raw gcc invocation. - Fix `tests/run-make/mte-ffi/rmake.rs` to use `gcc` instead of *a* c compiler. try-job: aarch64-gnu try-job: aarch64-gnu-debug
2024-11-15Auto merge of #132967 - klensy:docker-unite, r=Kobzolbors-1/+3
fix REGISTRY_USERNAME to reuse cache between auto and pr jobs see https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/reuse.20.28some.29.20docker.20images.20for.20pr.2Fauto.3F
2024-11-13define all the clippy lints we check in CI in a stepPietro Albini-3/+1
2024-11-13fix REGISTRY_USERNAME to reuse cache between auto and pr jobsklensy-1/+3
2024-11-12ci: liberate `aarch64-gnu-debug` from the shackles of `--test-args=clang`Jieyou Xu-1/+1
And run all eligible run-make tests.
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-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-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-28CI: build FreeBSD artifacts on FreeBSD 13.4Alan Somers-6/+6
13.2 is EoL, and 13.3 will be EoL too in about 2 months. Plus, both suffer from a bug in LLVM's libunwind. It causes a segfault inside of std::backtrace::Backtrace::capture(). Fixes #132185
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-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 #131917 - jieyouxu:rmake-clang, r=Kobzolbors-3/+1
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-25Auto merge of #131207 - davidtwco:pac-ret-lto-test, r=Mark-Simulacrumbors-0/+58
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-24ci: add aarch64-gnu-debug jobDavid Wood-0/+58
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: 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 #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-18checktools.sh: add link to issue for more context about disabled Miri testsRalf Jung-0/+2
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-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-11move dummy commit logic into x86_64-gnu-llvm-18onur-ozkan-12/+16
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-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/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08fix `ci_rustc_if_unchanged_logic` testonur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-08handle CI rustc incompatible runnersonur-ozkan-0/+1
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-08make an explicit change on compiler then run bootstrap testonur-ozkan-1/+14
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-10-07CI: rfl: move job forward to Linux v6.12-rc2Miguel Ojeda-1/+1
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-10-06Enable sanitizers for loongarch64-unknown-*WANG Rui-0/+2
2024-10-04Enable `--no-sandbox` option by default for rustdoc GUI testsGuillaume Gomez-1/+1
2024-09-28Update `browser-ui-test` version to `0.18.1`Guillaume Gomez-1/+1
2024-09-28update Docker ?David Carlier-1/+1
2024-09-28ci update freebsd version proposal, freebsd 12 being eol.David Carlier-10/+10
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 #120589, therefore breaks the backward compatibility with the previous FreeBSD releases.
2024-09-27Update libgccjit version used in CIGuillaume Gomez-1/+1
2024-09-22Reformat using the new identifier sorting from rustfmtMichael Goulet-1/+1
2024-09-20Add --enable-profiler to armhf distElli Howard-1/+1
Adds the --enable-profiler flag to the RUST_CONFIGURE_ARGS for armhf distribution for Linux. This enables running coverage for tests
2024-09-18Update the minimum external LLVM to 18Josh Stone-62/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 09:15:10 +0000