summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
2021-10-14Get rid of broken `ct-ng oldconfig` everywhere and directly provide a ↵Hans Kratz-20/+8
suitable .config file.
2021-10-14Switch to our own mirror of libislMark Rousskov-4/+4
2021-10-14CI: Use mirror for downloads.Hans Kratz-4/+8
Crosstool-ng 1.22 used by those docker dist builds only allows one mirror for all downloads.
2021-10-04Auto merge of #89486 - rusticstuff:docker_letsencrypt_ca_update, ↵bors-0/+41
r=Mark-Simulacrum Update Let's Encrypt ROOT CA certificate in dist-(i686|x86_64)-linux docker images The DST Root CA X3 used by Let's Encrypt has expired ([Let's Encrypt announcement](https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/)). This patch installs the new root certificate (ISRG Root X1) and disables the old one. Disabling the old one is necessary because otherwise curl still fails to download from servers with Let's Encrypt certs even though they are cross-signed. Fixes #89484.
2021-08-25Bump sccache used in CI to v0.2.15Mark Rousskov-2/+5
This skips bumping Windows sccache because we run into compilation failures when doing so (-m32 not supported by clang-cl?). Not clear on cause, but seems easiest to just hold back. This should avoid PGO-related failures encountered on Linux, and more broadly seems like a good idea on other platforms as well (though it is likely not necessary right this moment).
2021-08-24PGO for LLVM builds on x86_64-unknown-linux-gnu in CIMark Rousskov-1/+11
This shows up to 5% less instruction counts on multiple benchmarks, and up to 19% wins on the -j1 wall times for rustc self-compilation. We can afford to spend the extra cycles building LLVM essentially once more for the x86_64-unknown-linux-gnu CI build today. The builder finishes in around 50 minutes on average, and this adds just 10 more minutes. Given the sizeable improvements in compiler performance, this is definitely worth it.
2021-08-15Auto merge of #87792 - GuillaumeGomez:ci-fetch, r=pietroalbinibors-4/+6
Remove git fetch from CI https://github.com/rust-lang/rust/pull/86623 added a call to `git fetch`, which is problematic for releases. r? `@pietroalbini`
2021-08-13Update browser-ui-test package versionGuillaume Gomez-1/+1
2021-08-05Remove git fetch command callGuillaume Gomez-4/+6
2021-07-14Rollup merge of #87130 - GuillaumeGomez:update-browser-ui-test, ↵Guillaume Gomez-1/+1
r=Mark-Simulacrum Update browser-ui-test package version It adds a check to prevent to have empty CSS values in `assert-css` command. r? `@Mark-Simulacrum`
2021-07-14Update browser-ui-test package versionGuillaume Gomez-1/+1
2021-07-10Use nproc instead of hardcoded 10 for build parallelismNikita Popov-7/+7
2021-07-10Update binutils versionNikita Popov-3/+5
This is needed to handle R_X86_64_REX_GOTPCRELX relocations.
2021-07-10Use clang 12.0.1 on dist-x86_64/i686-linuxNikita Popov-7/+3
The LLD + ThinLTO __morestack bug has been fixed in 12.0.1, so we can now update our clang version. This also means that we no longer need to build Python 2.
2021-07-07Clean up rustdoc static filesGuillaume Gomez-2/+2
2021-07-03Only run error code explanation removal check if on CIGuillaume Gomez-4/+13
2021-07-02Add check to ensure error code explanations are not removed anymore even if ↵Guillaume Gomez-0/+22
not emitted
2021-07-01Update container browser-ui-test@0.4.1Stefan Schindler-1/+1
2021-06-28Install tidy on x86_64-gnu-aux target to run html checkGuillaume Gomez-1/+2
2021-06-28Add new tool to check HTML:Guillaume Gomez-1/+2
* Make html-checker run by default on rust compiler docs as well * Ensure html-checker is run on CI * Lazify tidy binary presence check
2021-06-26Auto merge of #86586 - Smittyvb:https-everywhere, r=petrochenkovbors-4/+5
Use HTTPS links where possible While looking at #86583, I wondered how many other (insecure) HTTP links were in `rustc`. This changes most other `http` links to `https`. While most of the links are in comments or documentation, there are a few other HTTP links that are used by CI that are changed to HTTPS. Notes: - I didn't change any to or in licences - Some links don't support HTTPS :( - Some `http` links were dead, in those cases I upgraded them to their new places (all of which used HTTPS)
2021-06-25Download the GCC sources insecurelySmitty-1/+2
This is needed as they are built on a long-outdated Debian version. :(
2021-06-25Fetch expat from github because the project switchedStefan Schindler-1/+2
2021-06-25Use https for sourceforge during CIStefan Schindler-6/+6
2021-06-23Use HTTPS links where possibleSmitty-5/+5
2021-06-23Bump expat to 2.4.1Mark Rousskov-1/+1
2021-06-22Update browser-ui-test versionGuillaume Gomez-1/+1
2021-06-19Update browser-ui-test versionGuillaume Gomez-1/+1
2021-06-13Update browser-ui-test versionGuillaume Gomez-1/+1
2021-06-07add the x86_64-gnu-stable job to test with stable channelPietro Albini-0/+1
During the 1.52 release process we had to deal with some commits that passed the test suite on the nightly branch but failed on the beta or stable branch. In that case it was due to some UI tests including the channel name in the output, but other changes might also be dependent on the channel. This commit adds a new CI job that runs the Linux x86_64 test suite with the stable branch, ensuring nightly changes also work as stable.
2021-05-31Auto merge of #85395 - 12101111:build-crt, r=petrochenkovbors-1/+5
Build crtbegin.o/crtend.o from source code Build crtbengin.o/crtend.o from source code instead of copying from gcc. The crtbegin and crtend implementation from llvm don't need `crtbeginS.o` for PIC. `crtbegin{,S,T}.o` is unified into one generic `crtbegin.o`. See the comments in https://reviews.llvm.org/D28791#1419436 and https://reviews.llvm.org/D28791#1420914 fix: https://github.com/rust-lang/rust/issues/85310 , fix: https://github.com/rust-lang/rust/issues/47551 , fix: https://github.com/rust-lang/rust/issues/84033
2021-05-31Build crtbengin.o/crtend.o from source code12101111-1/+5
2021-05-30Rollup merge of #85285 - GuillaumeGomez:eslint-check, r=jsha,Mark-SimulacrumGuillaume Gomez-1/+3
Add eslint checks to CI It also allowed me to fix some potential issues that went unnoticed. Having this process automated will hopefully prevent us to add more errors. :) cc `@Mark-Simulacrum` (for the add in the CI). r? `@jsha`
2021-05-30Add eslint checks in CIGuillaume Gomez-1/+3
2021-05-30Auto merge of #84586 - GuillaumeGomez:enforce-rustdoc-gui-test-suite-run, ↵bors-25/+57
r=Mark-Simulacrum Enforce rustdoc-gui test-suite run Part of https://github.com/rust-lang/rust/issues/84550
2021-05-26Update install of browser-ui-test package in CIGuillaume Gomez-5/+7
2021-05-26Enforce rustdoc-gui test-suite runGuillaume Gomez-25/+55
2021-05-26Auto merge of #85252 - kulikjak:fix-solaris-CI, r=Mark-Simulacrumbors-14/+10
Bring back `x86_64-sun-solaris` target to rustup Change #82216 removed now deprecated target `x86_64-sun-solaris` from CI, thus making it no longer possible to use `$ rustup target add x86_64-sun-solaris` to install given target (see #85098 for details). Since there should be a period of time between the deprecation and removal, this PR brings it back (while keeping the new one as well). Please, correct me if I am wrong; my assumption that these Docker scripts are being used to build artifacts later used by `rustup` might be incorrect. Closes #85098.
2021-05-15Auto merge of #85335 - GuillaumeGomez:rollup-0tvc14g, r=GuillaumeGomezbors-1/+1
Rollup of 4 pull requests Successful merges: - #84751 (str::is_char_boundary - slight optimization) - #85185 (Generate not more docs than necessary) - #85324 (Warn about unused `pub` fields in non-`pub` structs) - #85329 (fix version_str comment) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2021-05-15Don't generate more docs than necessaryGuillaume Gomez-1/+1
2021-05-14Update bootstrap for in-tree rustfmtJoshua Nelson-1/+1
- Add rustfmt to `x.py check` - Update Cargo.lock - Remove rustfmt from the toolstate list - Make rustfmt an in-tree tool - Give an error on `x.py test rustfmt` if rustfmt fails to build or if tests fail - Don't call `save_toolstate` when testing rustfmt
2021-05-13Improve commentJakub Kulik-1/+1
2021-05-13Update Docker to build the deprecated target alongside the new oneJakub Kulik-14/+10
2021-04-25Build sanitizers for x86_64-unknown-linux-musl12101111-0/+1
2021-04-21Upgrade `expat` dependency in riscv64 to newer version.Mara Bos-1/+1
The old version was renamed to `expat-2.2.6-RENAMED-VULNERABLE-PLEASE-USE-2.3.0-INSTEAD`. :)
2021-04-08rustc: Add a new `wasm` ABIAlex Crichton-2/+2
This commit implements the idea of a new ABI for the WebAssembly target, one called `"wasm"`. This ABI is entirely of my own invention and has no current precedent, but I think that the addition of this ABI might help solve a number of issues with the WebAssembly targets. When `wasm32-unknown-unknown` was first added to Rust I naively "implemented an abi" for the target. I then went to write `wasm-bindgen` which accidentally relied on details of this ABI. Turns out the ABI definition didn't match C, which is causing issues for C/Rust interop. Currently the compiler has a "wasm32 bindgen compat" ABI which is the original implementation I added, and it's purely there for, well, `wasm-bindgen`. Another issue with the WebAssembly target is that it's not clear to me when and if the default C ABI will change to account for WebAssembly's multi-value feature (a feature that allows functions to return multiple values). Even if this does happen, though, it seems like the C ABI will be guided based on the performance of WebAssembly code and will likely not match even what the current wasm-bindgen-compat ABI is today. This leaves a hole in Rust's expressivity in binding WebAssembly where given a particular import type, Rust may not be able to import that signature with an updated C ABI for multi-value. To fix these issues I had the idea of a new ABI for WebAssembly, one called `wasm`. The definition of this ABI is "what you write maps straight to wasm". The goal here is that whatever you write down in the parameter list or in the return values goes straight into the function's signature in the WebAssembly file. This special ABI is for intentionally matching the ABI of an imported function from the environment or exporting a function with the right signature. With the addition of a new ABI, this enables rustc to: * Eventually remove the "wasm-bindgen compat hack". Once this ABI is stable wasm-bindgen can switch to using it everywhere. Afterwards the wasm32-unknown-unknown target can have its default ABI updated to match C. * Expose the ability to precisely match an ABI signature for a WebAssembly function, regardless of what the C ABI that clang chooses turns out to be. * Continue to evolve the definition of the default C ABI to match what clang does on all targets, since the purpose of that ABI will be explicitly matching C rather than generating particular function imports/exports. Naturally this is implemented as an unstable feature initially, but it would be nice for this to get stabilized (if it works) in the near-ish future to remove the wasm32-unknown-unknown incompatibility with the C ABI. Doing this, however, requires the feature to be on stable because wasm-bindgen works with stable Rust.
2021-03-28ci: docker: x86_64: specify host explicitlyTom Eccles-1/+2
2021-03-28ci: docker: riscv64gc: specify host explicitlyTom Eccles-1/+1
2021-03-22Update the minimum external LLVM to 10Josh Stone-3/+3
2021-03-18Rollup merge of #83204 - jethrogb:jb/sgx-c-build, r=joshtriplett,raoulstrackxDylan DPC-20/+4
Simplify C compilation for Fortanix-SGX target cc ``@raoulstrackx``
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 14:13:27 +0000