summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
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-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-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
2024-09-17Add zlib to musl dist image so rust-lld will support zlib compression for ↵Kyle Huey-0/+1
debug info there. Fixes #130063.
2024-09-14Auto merge of #129974 - cuviper:ci-llvm-19, r=Mark-Simulacrumbors-0/+62
ci: add a runner for vanilla LLVM 19 Ubuntu 24.10 has `llvm-19` packages that we can start testing with. The `Dockerfile` is otherwise the same as the `llvm-18` runner.
2024-09-07Fix bash syntaxChris Denton-1/+1
2024-09-07Fix checktools.sh non-msvc buildsChris Denton-4/+7
2024-09-07Split x86_64-msvc-ext into two jobsChris Denton-5/+7
2024-09-05Rollup merge of #128928 - ojeda:ci-rfl-more-tools, r=KobzolMatthias Krüger-7/+43
CI: rfl: add more tools and steps This will add some time for the tool building -- the actual steps should be quick, though, and allows us to cover quite a few more tools and unstable features in use. Please see the individual commits for a few details. Cc: `@GuillaumeGomez` `@tgross35` r? `@Kobzol` try-job: x86_64-rust-for-linux
2024-09-05Rollup merge of #101339 - the8472:ci-randomize-debug, r=Mark-SimulacrumMatthias Krüger-0/+1
enable -Zrandomize-layout in debug CI builds This builds rustc/libs/tools with `-Zrandomize-layout` on *-debug CI runners. Only a handful of tests and asserts break with that enabled, which is promising. One test was fixable, the rest is dealt with by disabling them through new cargo features or compiletest directives. The config.toml flag `rust.randomize-layout` defaults to false, so it has to be explicitly enabled for now.
2024-09-04ci: add a runner for vanilla LLVM 19Josh Stone-0/+62
2024-09-04Auto merge of #129356 - nikic:llvm19-host, r=Mark-Simulacrumbors-1/+2
Update x86_64-linux host compiler to LLVM 19 rc 3
2024-08-31enable layout randomization in x86_64-gnu-llvm-17 CI jobThe 8472-0/+1
2024-08-28CI: rfl: factor out build targetsMiguel Ojeda-8/+9
It will make it easier to add more in the future. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add macro expanded source build (`-Zunpretty=expanded`)Miguel Ojeda-0/+8
This particular target does not expand into much code, so it is a good first candidate to see if we could keep this in the CI. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a `rustfmt` runMiguel Ojeda-2/+9
This change will also remove the current warnings in the build due to `rustfmt` not being available (for `bindgen` output): error: 'rustfmt' is not installed for the custom toolchain 'local'. note: this is a custom toolchain, which cannot use `rustup component add` help: if you built this toolchain from source, and used `rustup toolchain link`, then you may be able to build the component with `x.py` Failed to run rustfmt: Internal rustfmt error (non-fatal, continuing) Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a Clippy buildMiguel Ojeda-2/+13
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: switch to a stage 2 buildMiguel Ojeda-2/+2
Apparently tools like `rustfmt` require it in order to find the right `librustc_driver.so` without extra tweaks. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a couple comments to split the steps and document themMiguel Ojeda-0/+9
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-27Rollup merge of #128935 - lqd:needs-zstd, r=KobzolTrevor Gross-4/+5
More work on `zstd` compression r? ``@Kobzol`` as we've discussed this. This is a draft to show the current approach of supporting zstd in compiletest, and making the tests using it unconditional. Knowing whether llvm/lld was built with `LLVM_ENABLE_ZSTD` is quite hard, so there are two strategies. There are details in the code, and we can discuss this approach. Until we know the config used to build CI artifacts, it seems our options are somewhat limited in any case. zlib compression seems always enabled, so we only check this in its dedicated test, allowing the test to ignore errors due to zstd not being supported. The zstd test is made unconditional in what it tests, by relying on `needs-llvm-zstd` to be ignored when `llvm.libzstd` isn't enabled in `config.toml`. try-job: x86_64-gnu try-job: x86_64-msvc try-job: x86_64-gnu-distcheck
2024-08-25enable `llvm.libzstd` on test x64 linux builderRémy Rakic-1/+2
2024-08-25move and rename zstd scriptRémy Rakic-3/+3
move it where it's used, and name it like the other scripts
2024-08-23CI: rfl: move to temporary commitMiguel Ojeda-2/+2
Link: https://github.com/rust-lang/rust/pull/129416 Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-21Update x86_64-linux host compiler to LLVM 19 rc 3Nikita Popov-1/+2
2024-08-19Auto merge of #128722 - tgross35:new-resolver-root, r=Mark-Simulacrumbors-1/+1
Switch to using the v2 resolver in most workspaces Pinning the resolver to v1 was done in 5abff3753a7c ("Explicit set workspace.resolver ...") in order to suppress warnings. Since there is no specific reason not to use the new resolver and since it fixes issues, change to `resolver = "2"` everywhere except library.
2024-08-18Rollup merge of #129048 - heiher:update-crosstool-loongarch64, r=Mark-SimulacrumTrevor Gross-7/+7
Update `crosstool-ng` for loongarch64 The current cross-compilation toolchain for the LoongArch64 target consists of GCC 13.2.0, Binutils 2.40, and Glibc 2.36. However, Binutils 2.40 has known issues that in broken binaries without any error reports: - https://github.com/rust-lang/rust/issues/121289 - https://github.com/cross-rs/cross/issues/1538 This patch upgrades the cross-compilation toolchain for the LoongArch64 target to resolve these issues. - GCC: 13.2.0 -> 14.2.0 - Binutils: 2.40 -> 2.42 The new binaries remain compatible with the existing GCC 13.2.0/Glibc 2.36 distribution, and no issues have been identified. try-job: dist-loongarch64-linux
2024-08-18Switch to using the v2 resolver in most workspacesTrevor Gross-1/+1
Pinning the resolver to v1 was done in 5abff3753a7c ("Explicit set workspace.resolver ...") in order to suppress warnings. Since there is no specific reason not to use the new resolver and since it fixes issues, change to `resolver = "2"` everywhere except library and submodules.
2024-08-13Update `crosstool-ng` for loongarch64WANG Rui-7/+7
The current cross-compilation toolchain for the LoongArch64 target consists of GCC 13.2.0, Binutils 2.40, and Glibc 2.36. However, Binutils 2.40 has known issues that in broken binaries without any error reports: - https://github.com/rust-lang/rust/issues/121289 - https://github.com/cross-rs/cross/issues/1538 This patch upgrades the cross-compilation toolchain for the LoongArch64 target to resolve these issues. - GCC: 13.2.0 -> 14.2.0 - Binutils: 2.40 -> 2.42 The new binaries remain compatible with the existing GCC 13.2.0/Glibc 2.36 distribution, and no issues have been identified.
2024-08-12don't use `--rustc-args` to test the stdlib's size optimizations featureRémy Rakic-3/+3
2024-08-09Install zstd in dist builder image.Kyle Huey-0/+33
Build libzstd from source because the EPEL package is built without fPIC.
2024-08-09Add zlib and zstd dev packages for building lld.Kyle Huey-0/+2
2024-08-09Enable zstd for debug compression.Kyle Huey-0/+1
Set LLVM_ENABLE_ZSTD alongside LLVM_ENABLE_ZLIB so that --compress-debug-sections=zstd is an option. Use static linking to avoid a new runtime dependency. Add an llvm.libzstd bootstrap option for LLVM with zstd. Set it off by default except for the dist builder. Handle llvm-config --system-libs output that contains static libraries.
2024-08-07Fuchsia Test Runner: enable ffx repository serverJeff Martin-0/+13
The default repository server setting has changed on Fuchsia (default is newly "false"). Now, in order to start the repository server, the config `repository.server.enabled` must be set to true.
2024-08-03Promote riscv64gc-unknown-linux-musl to tier 2Amanieu d'Antras-2/+12
2024-07-29CI: rfl: build the documentationMiguel Ojeda-0/+3
Since the `rfl` CI job has not had almost any issue for some weeks, it is a good time to try to increase a bit the scope of what it tests. The kernel does not use any particular `rustdoc` unstable issue (apart from the doctests ones) so far, so in principle it should not introduce extra issues here, and may be a good extra test case for Rust. In addition, it may help to test new unstable features in the future. In the worst case, we can revert it. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-07-29CI: rfl: build the generated doctestsMiguel Ojeda-1/+2
We were already generating the doctests, which should already catch most issues with our hack around `--test-builder` and `--no-run`. However, we were not building the result of that transformation, thus build it for completeness and to ensure the hack may not have produced something completely broken. In the worst case, we can revert it. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-07-29Rollup merge of #128322 - ojeda:rfl-ci-update, r=KobzolMatthias Krüger-1/+1
CI: move RFL job forward to v6.11-rc1 The tag has been released today, and since the original hash we had in the Rust CI (which was ~v6.10-rc1), we have accumulated a fair amount of changes and new code. In particular, v6.11-rc1 is the first Linux tag where the kernel is supporting an actual minimum Rust version (1.78.0), rather than a single version. --- Let's try to do the move independently first. r? ``@Kobzol`` try-job: x86_64-rust-for-linux
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 05:17:07 +0000