about summary refs log tree commit diff
path: root/src/ci
AgeCommit message (Collapse)AuthorLines
2024-10-04Rollup merge of #131230 - GuillaumeGomez:no-sandbox, r=notriddleGuillaume Gomez-1/+1
Enable `--no-sandbox` option by default for rustdoc GUI tests It's apparently common enough for people to have issues with the `sandbox` mode in chromium, so better disable it by default. r? `@notriddle`
2024-10-04Enable `--no-sandbox` option by default for rustdoc GUI testsGuillaume Gomez-1/+1
2024-10-02Auto merge of #125771 - Kobzol:ci-datadog-metrics, r=jdnobors-0/+81
[CI] Upload average CPU utilization of CI jobs to DataDog This PR adds a new CI step that uploads the average CPU utilization of the current GH job to Datadog. I want to add more metrics in follow-up PRs. r? `@jdno` try-job: dist-i686-msvc try-job: aarch64-apple try-job: x86_64-gnu-llvm-18
2024-09-28Update `browser-ui-test` version to `0.18.1`Guillaume Gomez-1/+1
2024-09-28Rollup merge of #130940 - workingjubilee:remove-space-saving-operations, ↵Matthias Krüger-20/+3
r=Kobzol Revert space-saving operations The "all of our artifacts" `mv` seems like it may save enough space to matter sometimes, since it can range up to a gigabyte of difference, if memory serves. For the rest, I think we're good. try-job: dist-aarch64-apple
2024-09-27Update libgccjit version used in CIGuillaume Gomez-1/+1
2024-09-27Partially revert "ci: Use mv instead of cp in upload step"Jubilee Young-3/+3
This partially reverts commit fe7c97c2e732de8dfc93ef21ee84ccfbc04c7d0c. I kept a mv, not a cp, for the one that shuffles major artifacts around, because the size of those artifacts are big enough to matter, sometimes. I don't think the diagnostic info will be that heavy, by comparison.
2024-09-27Revert "ci: Try to remove unused Xcode dirs"Jubilee Young-17/+0
This reverts commit 06f49f6d5326440192b8d31d69fa490dbfe01cfe.
2024-09-27Upload average CPU consumption of CI jobs to DataDogJakub Beránek-1/+82
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-68/+3
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-15Rollup merge of #130151 - ChrisDenton:slow-ci, r=Mark-SimulacrumMatthias Krüger-1/+5
Use a small runner for msvc-ext2 job Hopefully this should eliminate the errors from this job. The only question is how long it takes. try-job: x86_64-msvc-ext2
2024-09-14Auto merge of #129974 - cuviper:ci-llvm-19, r=Mark-Simulacrumbors-0/+67
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-09Auto merge of #128939 - bjorn3:windows_cg_clif_component, r=albertlarsan68bors-0/+4
Distribute rustc_codegen_cranelift for Windows With support for raw-dylib recently added to cg_clif, and inline assembly support working on Windows for quite a while now, all blockers for distributing cg_clif on Windows that I mentioned in https://github.com/rust-lang/rust/pull/81746#issuecomment-1774099637 are fixed now.
2024-09-09Use small runner for msvc-ext2 jobChris Denton-1/+5
2024-09-09Rollup merge of #119229 - mati865:update-mingw-toolchain, ↵Jubilee-2/+2
r=jieyouxu,petrochenkov Update mingw-w64 + GNU toolchain The list of packaged tools and their versions is available at: https://github.com/niXman/mingw-builds-binaries/releases/tag/14.1.0-rt_v12-rev0 Fixes: https://github.com/rust-lang/rust/issues/112368
2024-09-07Fix bash syntaxChris Denton-1/+1
2024-09-07Fix checktools.sh non-msvc buildsChris Denton-6/+7
2024-09-07Split x86_64-msvc-ext into two jobsChris Denton-5/+21
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/+67
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-09-01Upgrade CI's mingw-w64 toolchainMateusz Mikuła-2/+2
2024-08-31enable layout randomization in x86_64-gnu-llvm-17 CI jobThe 8472-0/+1
2024-08-30ci: Take tail instead of head to avoid broken pipesJubilee Young-3/+1
2024-08-30ci: Avoid legacy backticks in upload-artifacts.shJubilee Young-1/+1
2024-08-30ci: Use mv instead of cp in upload stepJubilee Young-4/+4
2024-08-30ci: Try to remove unused Xcode dirsJubilee Young-0/+17
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-18Auto merge of #126450 - madsmtm:promote-mac-catalyst, r=Mark-Simulacrumbors-2/+4
Promote Mac Catalyst targets to Tier 2, and ship with rustup Promote the Mac Catalyst targets `x86_64-apple-ios-macabi` and `aarch64-apple-ios-macabi` to Tier 2, as per [the MCP](https://github.com/rust-lang/compiler-team/issues/761) (see that for motivation and details). These targets are now also distributed with rustup, although without the sanitizer runtime, as that currently has trouble building, see https://github.com/rust-lang/rust/issues/129069.
2024-08-14Promote Mac Catalyst targets to tier 2, and ship with rustupMads Marquart-2/+4
- aarch64-apple-ios-macabi - x86_64-apple-ios-macabi
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-10Distribute rustc_codegen_cranelift for Windowsbjorn3-0/+4