about summary refs log tree commit diff
path: root/src/ci/docker/host-x86_64
AgeCommit message (Collapse)AuthorLines
2023-07-16CI: build CMake 3.20 to support LLVM 17Jakub Beránek-0/+45
2023-07-09Rollup merge of #113247 - mirkootter:test-wasm-exceptions-nostd, ↵Matthias Krüger-2/+4
r=Mark-Simulacrum Add Tests for native wasm exceptions ### Motivation In PR #111322, I added support for native WASM exceptions. I was asked by ``@davidtwco`` to add some tests for it in a follow up PR, which seems like a very good idea. This PR adds three tests for this feature: * codegen: ensure the correct LLVM instructions are used * assembly: ensure the correct WASM instructions are used * run-make: ensure the exception handling works; the WASM code is run using a small nodejs script which demonstrates the exception handling ### Complications There are a few changes beside adding the tests, which were necessary * Tests for the wasm32-unknown-unknown target are (as far as I know) only run on `test-various`. Its docker image uses nodejs-15, which is very old. Experimental support for wasm-exceptions was added in nodejs16. In nodejs 18.12 (LTS), they are stable. - --> increase nodejs to 18.12 in `test-various` * codegen/assembly tests are not performed for the wasm32-unknown-unknown target yet - --> add those to `test-various` as well Due to the last point, some tests are run which have not run before (assembly+codegen tests for wasm32-unknown-unknown). I added `// ignore wasm32-bare` for those which failed ### Local testing I run all tests locally using both `test-various` and `wasm32`. As far as I know, none of the other systems run any test for wasm32 targets.
2023-07-09Port PGO/LTO/BOLT optimized build pipeline to RustJakub Beránek-2/+5
2023-07-06Auto merge of #112779 - Kobzol:ci-merge-llvm-14, r=pietroalbinibors-71/+37
CI: merge x86_64-gnu-llvm-14 and x86_64-gnu-llvm-14-stage1 CI jobs Another attempt to shorten CI job times. Suggested by `@the8472` [here](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/CI.20usage/near/367172221).
2023-07-02test-various: run codegen and assembly testsJan-Mirko Otter-0/+2
2023-07-01test-various: update nodejs to 18.12 (LTS)Jan-Mirko Otter-2/+2
2023-06-30Update browser-ui-test version to 0.16.8Guillaume Gomez-1/+1
2023-06-23Update wasi-libcChristopher Serr-1/+1
This updates wasi-libc to the latest master. Resolves #112749
2023-06-19Rollup merge of #112499 - tgross35:py-ruff-fixes, r=Mark-SimulacrumMichael Goulet-0/+0
Fix python linting errors These were flagged by `ruff`, run using the config in https://github.com/rust-lang/rust/pull/112482
2023-06-19Print what is being executed on CIJakub Beránek-1/+1
This makes it easier to grep for executed commands in CI logs
2023-06-19CI: merge x86_64-gnu-llvm-14 and x86_64-gnu-llvm-14-stage1 CI jobsJakub Beránek-71/+37
2023-06-17Auto merge of #112407 - tgross35:ci-docs-publish, r=Mark-Simulacrumbors-0/+3
Publish docs as github artifacts during CI Discussed here: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI The goal is to make docs available for download after CI runs on PRs, for easy review of API changes. Notes: - Currently this only captures library documentation (`core`, `alloc`, `std`, `test`, `proc_macro`) - You can't see artifacts until the entire workflow run has completed https://github.com/actions/upload-artifact/issues/53 - There is currently a generic file name `ci-artifacts`. No way to customize this based on contained files unfortunately https://github.com/actions/upload-artifact/issues/349 You can find the results at the bottom of the CI "summary" page: <img width="379" alt="image" src="https://github.com/rust-lang/rust/assets/13724985/d3748e59-242c-40f8-9f54-82177b9b481b">
2023-06-16Apply changes to fix python linting errorsTrevor Gross-0/+0
2023-06-14Update browser-ui-test version to 0.16.7Guillaume Gomez-1/+1
2023-06-12Publish docs as github artifacts during CITrevor Gross-0/+3
This PR saves library docs as github artifacts so they can be easily viewed for review. Discussed in <https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Building.20docs.20for.20PR.20CI>
2023-06-04Update browser-ui-test versionGuillaume Gomez-1/+1
2023-06-01Auto merge of #103877 - oli-obk:const_eval_step_limit, r=fee1-deadbors-1/+1
Replace const eval limit by a lint and add an exponential backoff warning The lint triggers at the first power of 2 that comes after 1 million function calls or traversed back-edges (takes less than a second on usual programs). After the first emission, an unsilenceable warning is repeated at every following power of 2 terminators, causing it to get reported less and less the longer the evaluation runs. cc `@rust-lang/wg-const-eval` fixes #93481 closes #67217
2023-05-31Remove const eval limit and implement an exponential backoff lint insteadOli Scherer-1/+1
2023-05-31Explicit set `workspace.resolver = "1"`Weihang Lo-0/+1
rust-lang/cargo#10910 starts emitting warning if resolver is not set for 2021 edition package. We want to surpress the warning for now.
2023-05-30Rollup merge of #112064 - GuillaumeGomez:migrate-gui-test-color-9, r=notriddleNilstrieb-1/+1
Migrate GUI colors test to original CSS color format Follow-up of https://github.com/rust-lang/rust/pull/111459. The `browser-ui-test` update is a fix when converting the alpha value to hex format. More information [here](https://github.com/GuillaumeGomez/browser-UI-test/pull/511). r? ````@notriddle````
2023-05-29Update browser-ui-test version to 0.16.5Guillaume Gomez-1/+1
2023-05-25Auto merge of #111575 - alex:patch-1, r=pietroalbinibors-2/+7
Enable sanitizers and profiler for aarch64-unknown-linux-musl This is pretty heavily cargo-culted, hopefully I didn't screw it up too badly.
2023-05-23Auto merge of #110519 - loongarch-rs:ci, r=Mark-Simulacrumbors-0/+44
ci: Add support for dist-loongarch64-linux We are preparing to promote loongarch64-unknown-linux-gnu to Tier 2, and one of the tasks is to add CI support. We are currently in the process of upgrading the dependencies for the build tools, and before this is completed, we would like to request comments. Thanks #### Progress - [x] Update linux-raw-sys to 0.3.2 (rust-lang/cargo#11998) - [x] Update openssl-src to 111.25.3+1.1.1t (rust-lang/cargo#12005) - [x] bootstrap: Update linux-raw-sys to 0.3.2 (rust-lang/rust#110516) - [x] Update linux-raw-sys to 0.3.4 (rust-lang/rust#110518) - [x] Update cargo (rust-lang/rust#110834) - [x] linux_like: Add missing constants for loongarch64 (rust-lang/libc#3237) - [x] Release 0.2.143 (rust-lang/libc#3236) - [x] Update libc to 0.2.144 (rust-lang/cargo#12098) - [x] Update cargo (rust-lang/rust#111456) Tier 2 with host tools MCP: https://github.com/rust-lang/compiler-team/issues/518
2023-05-22Enable sanitizers and profiler for aarch64-unknown-linux-muslAlex Gaynor-2/+7
2023-05-22Update browser-ui-test to 0.16.4Guillaume Gomez-1/+1
2023-05-14Update browser-ui-test version to 0.16.3Guillaume Gomez-1/+1
2023-05-12ci: Add support for dist-loongarch64-linuxWANG Rui-0/+44
Co-Authored-By: YANG Xiaojuan <yangxiaojuan@loongson.cn>
2023-05-11Update browser-ui-test version to 0.16.0Guillaume Gomez-1/+1
2023-05-06Auto merge of #107129 - wesleywiser:musl_1.2_upgrade, r=petrochenkovbors-3/+0
Update the version of musl used on `*-linux-musl` targets to 1.2.3 Update the version of musl used on our Linux musl targets from 1.1.24 to 1.2.3 as proposed in rust-lang/compiler-team#572. musl 1.2.3 is the latest version of musl and supports the same range of Linux kernels as the 1.1 series. As such, it does not affect the minimum supported version of Linux for any of the musl targets. One of the major musl 1.2 features is support for [time64](https://musl.libc.org/time64.html). This support is both source and ABI compatible with programs built against musl 1.1 and so updating the musl version for these targets should not cause Rust programs to fail to run or compile (a [crater run](https://github.com/rust-lang/rust/pull/107129#issuecomment-1407196104) has been completed which demonstrates this for the `i686-unknown-linux-musl` target). Once this change reaches stable, the `libc` crate will then be able to [update their definitions to support 64-bit time](https://github.com/rust-lang/libc/pull/3068), matching the default musl 1.2 APIs exactly. Fixes #91178
2023-04-26ci: refactor crosstool-ng to use mini-defconfigJosh Stone-10900/+230
2023-04-26ci: upgrade to crosstool-ng 1.25.0Josh Stone-881/+1583
2023-04-26Auto merge of #110784 - cuviper:build-gcc-https, r=jyn514bors-2/+1
Revert "Download the GCC sources insecurely" This reverts commit 3da037f82988b8b3aca2ce13c5c81ba975923cab. This workaround was added after TLS problems with Debian 6 were noted in <https://github.com/rust-lang/rust/pull/86586#issuecomment-868355356>, but we should be well past that since #95026, where our oldest images are now based on CentOS 7.
2023-04-25Auto merge of #110232 - Amanieu:old-llvm-components, r=petrochenkovbors-0/+12
Allow older LLVM versions to have missing components This check was introduced by #77280 to ensure that all tests that are filtered by LLVM component are actually tested in CI. However this causes issues for new targets (e.g. #101069) where support is only available on the latest LLVM version. This PR restricts the tests to only CI jobs that use the latest LLVM version.
2023-04-24Revert "Download the GCC sources insecurely"Josh Stone-2/+1
This reverts commit 3da037f82988b8b3aca2ce13c5c81ba975923cab.
2023-04-19Rollup merge of #110430 - jsoref:spelling-src-ci, r=albertlarsan68Matthias Krüger-6/+6
Spelling src ci The various src/* items seem slightly disparate, so I'm doing src/* individually. split from https://github.com/rust-lang/rust/pull/110392
2023-04-17Spelling src/ciJosh Soref-6/+6
* architecture * configures * preparation * toolstate * unknown Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
2023-04-16Test python2.7 in dist-x86_64-illumosJosh Stone-2/+3
2023-04-16ci: add a runner for vanilla LLVM 16Josh Stone-5/+65
Like #107044, this will let us track compatibility with LLVM 16 going forward, especially after we eventually upgrade our own to the next. This also drops `tidy` here and in `x86_64-gnu-llvm-15`, syncing with that change in #106085.
2023-04-12Allow older LLVM versions to have missing componentsAmanieu d'Antras-0/+12
This check was introduced by #77280 to ensure that all tests that are filtered by LLVM component are actually tested in CI. However this causes issues for new targets (e.g. #101069) where support is only available on the latest LLVM version. This PR restricts the tests to only CI jobs that use the latest LLVM version.
2023-04-11Update browser-ui-test version to 0.15.0Guillaume Gomez-1/+1
2023-04-08s/ignore_git/omit_git_hashGimbles-1/+1
2023-04-04Move comment about python2 closer to the place it's usedjyn-2/+2
2023-03-31Update browser-ui-test version to 0.14.6Guillaume Gomez-1/+1
2023-03-28Auto merge of #109561 - raphamorim:master, r=cuviperbors-1/+1
Use llvm 16.0.0 instead of 16.0.0-rc4 for build-clang.sh Ref: https://github.com/rust-lang/rust/pull/107224 This PR doesn't make any update on LLVM submodule used by Rust repo, but would be super keen to update it, if necessary (https://rustc-dev-guide.rust-lang.org/backend/updating-llvm.html). LLVM 16.0.0 has been [released](https://discourse.llvm.org/t/llvm-16-0-0-release/69326) on March 18, while Rust 1.70 will become stable on June 1. - https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html
2023-03-25Auto merge of #109474 - nikic:llvm-16-again, r=cuviperbors-1/+1
Upgrade to LLVM 16, again Relative to the previous attempt in https://github.com/rust-lang/rust/pull/107224: * Update to GCC 8.5 on dist-x86_64-linux, to avoid std::optional ABI-incompatibility between libstdc++ 7 and 8. * Cherry-pick https://github.com/llvm/llvm-project/commit/96df79af029b85616ab90e73143e0e8ae89c7b46. * Cherry-pick https://github.com/llvm/llvm-project/commit/6fc670e5e370e90759b5adecd9980b63609dc2f8. r? `@cuviper`
2023-03-24use llvm 16.0.0 instead of 16.0.0-rc4Raphael Amorim-1/+1
2023-03-23Auto merge of #108355 - dpaoliello:dlltoolm, r=michaelwoeristerbors-0/+5
Fix cross-compiling with dlltool for raw-dylib Fix for #103939 Issue Details: When attempting to cross-compile using the `raw-dylib` feature and the GNU toolchain, rustc would attempt to find a cross-compiling version of dlltool (e.g., `i686-w64-mingw32-dlltool`). The has two issues 1) on Windows dlltool is always `dlltool` (no cross-compiling named versions exist) and 2) it only supported compiling to i686 and x86_64 resulting in ARM 32 and 64 compiling as x86_64. Fix Details: * On Windows always use the normal `dlltool` binary. * Add the ARM64 cross-compiling dlltool name (support for this is coming: https://sourceware.org/bugzilla/show_bug.cgi?id=29964) * Provide the `-m` argument to dlltool to indicate the target machine type. (This is the first of two PRs to fix the remaining issues for the `raw-dylib` feature (#58713) that is blocking stabilization (#104218))
2023-03-22Use -m option instead of looking for a cross-compiling version of dlltoolDaniel Paoliello-0/+5
2023-03-22Rollup merge of #109412 - GuillaumeGomez:add-gui-test, r=notriddleMatthias Krüger-1/+1
rustdoc: Add GUI test for "Auto-hide item contents for large items" setting Part of https://github.com/rust-lang/rust/issues/66181. The `browser-ui-test` version update is because there wasn't `null` check for attributes so I added it (PR is [here](https://github.com/GuillaumeGomez/browser-UI-test/pull/440)). r? ``@notriddle``
2023-03-22Auto merge of #109163 - hi-rustin:rustin-patch-dockerfile, r=Mark-Simulacrumbors-4/+5
Add RANLIB_x86_64_unknown_illumos env for dist-x86_64-illumos dockerfile close https://github.com/rust-lang/cc-rs/issues/798 We already set `AR_x86_64_unknown_illumos` in the dockerfile. So it is reasonable to set the `RANLIB_x86_64_unknown_illumos`.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 10:07:59 +0000