about summary refs log tree commit diff
path: root/src/ci/docker/host-x86_64/x86_64-gnu-tools
AgeCommit message (Collapse)AuthorLines
2025-09-30Remove usage of `compiletest-use-stage0-libtest` from CIJakub Beránek-1/+0
2025-09-16ci: x86_64-gnu-tools: Add `--test-args` regression testMartin Nordholts-0/+7
2025-07-15ci cleanup: rustdoc-gui-test now installs browser-ui-testbinarycat-12/+0
this removes the need for --unsafe-perm in the Dockerfile.
2025-07-03Update browser-ui-test version to `0.21.1`Guillaume Gomez-1/+1
2025-06-25Update `browser-ui-test` version to `0.20.7`Guillaume Gomez-1/+1
2025-06-10ci: split x86_64-gnu-tools jobMarcoIeni-55/+0
2025-06-01Rollup merge of #141277 - RalfJung:miri-ci, r=oli-obkJacob Pratt-3/+3
Miri CI: test aarch64-apple-darwin in PRs instead of the x86_64 target The aarch64 target is more important, and also this ensures we cover all main architectures (x86_64, i686, aarch64) in PR CI.
2025-05-27ci: use ghcr registry for x86_64-gnu-tools jobMarcoIeni-1/+1
2025-05-20Miri CI: test aarch64-apple-darwin in PRs instead of the x86_64 targetRalf Jung-3/+3
2025-05-11checktools.sh: fix bashismRalf Jung-1/+1
2025-05-10test intrinsic fallback bodies with MiriRalf Jung-0/+8
2025-04-23Update browser-ui-test version to 0.20.6Guillaume Gomez-1/+1
2025-04-07enable in-tree std on some runnersonur-ozkan-0/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-04-02Demote i686-pc-windows-gnu to Tier 2Noratrieb-1/+0
In accordance with RFC 3771. I also added a stub doc page for the target and renamed the windows-gnullvm page for consistency.
2025-02-26Auto merge of #136921 - Kobzol:gcc-build, r=onur-ozkanbors-3/+0
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-24Update browser-ui-test version to `0.20.3`Guillaume Gomez-1/+1
2025-02-14Remove `build-gccjit.sh` scriptJakub Beránek-3/+0
2025-02-05Update browser-ui-test version to `0.20.2`Guillaume Gomez-1/+1
2025-01-11ci: Organise shared helper scriptsKajetan Puchalski-2/+2
Move shared helper scripts used by Docker builds under docker/scripts.
2024-12-20Revert "Auto merge of #133809 - mrkajetanp:ci-aarch64-dist, r=Kobzol"Jakub Beránek-2/+2
This reverts commit 023521e6825edfa6df01e392520d7cb120eab158, reversing changes made to c434b4b4b6cd20560c5b32e80b2b22618a4da3dd.
2024-12-18ci: Organise shared helper scriptsKajetan Puchalski-2/+2
Move shared helper scripts used by Docker builds under docker/scripts.
2024-12-05Update browser-ui-test version to 0.18.2Guillaume Gomez-1/+1
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-10-18checktools.sh: add link to issue for more context about disabled Miri testsRalf Jung-0/+2
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-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-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-07-19Improve error when a compiler/library build fails in `checktools.sh`Jakub Beránek-0/+4
2024-06-27Update browser-ui-test version to `0.18.0`Guillaume Gomez-1/+1
2024-04-18CI: add script for installing NodeJS and update it to v20Jakub Beránek-3/+3
2024-04-09Rollup merge of #123624 - GuillaumeGomez:theme-switch-tests, r=notriddleMatthias Krüger-13/+11
[rustdoc] [GUI tests] Make theme switching closer to reality Better to actually perform actions user do rather than only testing the change through local storage. As for `browser-ui-test` update: I updated `puppeteer` version (to `0.19.4`) and fixed a bug when displaying the file if it came from an `include`. r? `@notriddle`
2024-04-08Manually set cache directory path when running GUI testsGuillaume Gomez-12/+10
2024-04-08Update browser-ui-test version to 0.17.2Guillaume Gomez-1/+1
2024-04-05bootstrap: split cargo-miri test into separate StepRalf Jung-4/+4
2024-04-05Auto merge of #123317 - RalfJung:test-in-miri, r=m-ou-se,saethlin,onur-ozkanbors-0/+5
Support running library tests in Miri This adds a new bootstrap subcommand `./x.py miri` which can test libraries in Miri. This is in preparation for eventually doing that as part of bors CI, but this PR only adds the infrastructure, and doesn't enable it yet. `@rust-lang/bootstrap` should this be `x.py test --miri library/core` or `x.py miri library/core`? The flag has the advantage that we don't have to copy all the arguments from `Subcommand::Test`. It has the disadvantage that most test steps just ignore `--miri` and still run tests the regular way. For clippy you went the route of making it a separate subcommand. ~~I went with a flag now as that seemed easier, but I can change this.~~ I made it a new subcommand. Note however that the regular cargo invocation would be `cargo miri test ...`, so `x.py` is still going to be different in that the `test` is omitted. That said, we could also make it `./x.py miri-test` to make that difference smaller -- that's in fact more consistent with the internal name of the command when bootstrap invokes cargo. `@rust-lang/libs` ~~unfortunately this PR does some unholy things to the `lib.rs` files of our library crates.~~ `@m-ou-se` found a way that entirely avoids library-level hacks, except for some new small `lib.miri.rs` files that hopefully you will never have to touch. There's a new hack in cargo-miri but there it is in good company...
2024-04-04Update browser-ui-test version to 0.17.1Guillaume Gomez-1/+1
2024-04-04smoke-test 'x.py test --miri' on CIRalf Jung-0/+5
2024-04-01Update to new browser-ui-test versionGuillaume Gomez-1/+1
2024-03-31checktools: make it easier to trace what is happeningRalf Jung-0/+1
2024-03-15Greatly reduce GCC build logsGuillaume Gomez-1/+2
2024-03-10Use full commit hash and remove `libgccjit.version` fileGuillaume Gomez-1/+0
2024-03-06Build libgccjit in CIGuillaume Gomez-3/+11
2024-02-06Don't use bashism in checktools.shBen Kimock-1/+1
2024-01-06Run Miri and mir-opt tests without a target linkerBen Kimock-2/+0
2023-12-24Update browser-ui-test version to 0.16.11Guillaume Gomez-1/+1
2023-11-20Test with -Zmiri-provenance-gc=1 on LinuxBen Kimock-1/+10
2023-11-02Force mangling version for rustc_codegen_gccGuillaume Gomez-1/+2
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 10:26:39 +0000