about summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
2020-06-20ci: Enable sanitizers on dist-aarch64-linuxTomasz Miąsko-0/+1
2020-06-15Avoid prematurely recording toolstatesMark Rousskov-1/+3
When we're running with dry_run enabled (i.e. all builds do this initially), we're guaranteed to save of a toolstate of TestFail for tools that aren't tested. In practice, we do test tools as well, so for those tools we would initially record them as being TestPass, and then later on re-record the correct state after actually testing them. However, this would not work well if the build failed for whatever reason (e.g. panicking in bootstrap, or as was the case in 73097, clippy failing to test successfully), we would just go on believing that things passed when they in practice did not. This commit also adjusts saving toolstate to never record clippy explicitly (otherwise, it would be recorded when building it); eventually that'll likely move to other tools as well but not yet. This is deemed simpler than checking everywhere we generically save toolstate. We also move clippy out of the "toolstate" no-fail-fast build into a separate x.py invocation; this should no longer be technically required but provides the nice state of letting us check toolstate for all tools and only then check clippy (giving full results on every build).
2020-06-14Auto merge of #73089 - tmiasko:musl-1.1.24, r=kennytmbors-5/+7
Update musl to 1.1.24 Release notes since previous version 1.1.22: ## 1.1.23 release notes ### new features: - riscv64 port - configure now allows customizing AR and RANLIB vars - header-level support for new linux features in 5.1 ### major internal changes: - removed extern __syscall; syscall header code is now fully self-contained ### performance: - new math library implementation for log/exp/pow - aarch64 dynamic tlsdesc function is streamlined ### compatibility & conformance: - O_TTY_INIT is now defined - sys/types.h no longer pollutes namespace with sys/sysmacros.h in any profile - powerpc asm is now compatible with clang internal assembler ### changes for new POSIX interpretations: - fgetwc now sets stream error indicator on encoding errors - fmemopen no longer rejects 0 size ### bugs fixed: - static TLS for shared libraries was allocated wrong on "Variant I" archs - crash in dladdr reading through uninitialized pointer on non-match - sigaltstack wrongly errored out on invalid ss_size when doing SS_DISABLE - getdents function misbehaved with buffer length larger than INT_MAX - set*id could deadlock after fork from multithreaded process ### arch-specfic bugs fixed: - s390x SO_PEERSEC definition was wrong - passing of 64-bit syscall arguments was broken on microblaze - posix_fadvise was broken on mips due to missing 7-arg syscall support - vrregset_t layout and member naming was wrong on powerpc64 ## 1.1.24 release notes ### new features: - GLOB_TILDE extension to glob - non-stub catgets localization API, using netbsd binary catalog format - posix_spawn file actions for [f]chdir (extension, pending future standard) - secure_getenv function (extension) - copy_file_range syscall wrapper (Linux extension) - header-level support for new linux features in 5.2 ### performance: - new fast path for lrint (generic C version) on 32-bit archs ### major internal changes: - functions involving time are overhauled to be time64-ready in 32-bit archs - x32 uses the new time64 code paths to replace nasty hacks in syscall glue ### compatibility & conformance: - support for powerpc[64] unaligned relocation types - powerpc[64] and sh sys/user.h no longer clash with kernel asm/ptrace.h - select no longer modifies timeout on failure (or at all) - mips64 stat results are no longer limited to 32-bit time range - optreset (BSD extension) now has a public declaration - support for clang inconsistencies in wchar_t type vs some 32-bit archs - mips r6 syscall asm no longer has invalid lo/hi register clobbers - vestigial asm declarations of __tls_get_new are removed (broke some tooling) - riscv64 mcontext_t mismatch glibc's member naming is corrected ### bugs fixed: - glob failed to match broken symlinks consistently - invalid use of interposed calloc to allocate initial TLS - various dlsym symbol resolution logic errors - semctl with SEM_STAT_ANY didn't work - pthread_create with explicit scheduling was subject to priority inversion - pthread_create failure path had data race for thread count - timer_create with SIGEV_THREAD notification had data race getting timer id - wide printf family failed to support l modifier for float formats ### arch-specific bugs fixed: - x87 floating point stack imbalance in math asm (i386-only CVE-2019-14697) - x32 clock_adjtime, getrusage, wait3, wait4 produced junk (struct mismatches) - lseek broken on x32 and mipsn32 with large file offsets - riscv64 atomics weren't compiler barriers - riscv64 atomics had broken asm constraints (missing earlyclobber flag) - arm clone() was broken when compiled as thumb if start function returned - mipsr6 setjmp/longjmp did not preserve fpu register state correctly Fixes #71099.
2020-06-10Fix emcc failure for wasm32.Eric Huss-0/+3
2020-06-09Add a disabled builder for riscv64 emulated testsTom Eccles-0/+249
This will run all tests for `riscv64gc-unknown-linux-gnu` in a QEMU instance. This is based upon the armhf QEMU test image.
2020-06-07Update musl to 1.1.24Tomasz Miąsko-5/+7
2020-06-07Enable LVI hardening for x86_64-fortanix-unknown-sgxJethro Beekman-20/+51
2020-05-08Use CDN for ci-caches on downloadMark Rousskov-4/+6
This will reduce costs, as well as lays the groundwork for developers to be able to locally pull the published docker images without needing AWS credentials.
2020-05-07Auto merge of #71649 - ecstatic-morse:ci-stage0-doc, r=Mark-Simulacrumbors-0/+1
Ensure that `./x.py doc --stage 0 src/libstd` works via CI This was split off from #71645, which recommends that users first try building `libstd` docs with the bootstrap `rustdoc`. This should work in most cases, but will fail if we start using a very recent `rustdoc` feature outside a `#[cfg(not(bootstrap))]`. It would be very nice to guarantee that `./x.py doc --stage 0 src/libstd` works, since it allows documentation changes to be rendered locally without needing to build the compiler. However, it may put too big a burden on `rustdoc` developers who presumably want to dogfood new features.
2020-04-30Turn of rustc-dev-guide toolstate for nowmark-1/+0
2020-04-28Ensure that `./x.py doc --stage 0 src/libstd` works via CIDylan MacKenzie-0/+1
2020-04-23Enable "full tools" option on ARM dist buildersAlex Crichton-4/+4
This commit switches the `--enable-extended` option on the arm-related dist builders to `--enable-full-tools`. This alias in `config.py` corresponds to enabling a few more options: * `rust.lld = true` - this is the main purpose of this PR, to enable LLD on ARM-related platforms. This means it will effectively unlock compilation of wasm programs from an arm host. * `rust.llvm-tools = true` - it turns out that this option is largely ignored in rustbuild today. This is only read in one location to set some flags for the `llvm-tools` package, but the `llvm-tools` package is already produced on all of these builders. It's predicted that this will have no effect on build times. * `rust.codegen-backends = ['llvm']` - historically this also enabled the emscripten backend, but that has long since been removed. This brings the ARM dist builders in line with the x86_64 dist builders using this flag. The hope is that the extra time spent on CI building LLD will acceptable because it's cached by `sccache`, LLD is a relatively small C++ project, and the dist builders are all clocking well under 3 hours (the slowest of all builders) around 2 hours. There's likely some possible cleanup that can happen with these configure options since it doesn't look like they've aged too too well, but I'm hopeful that possible refactorings, if necessary, could be deferred to future PRs.
2020-04-14Update the minimum external LLVM to 8Josh Stone-2/+2
LLVM 8 was released on March 20, 2019, over a year ago.
2020-04-13Auto merge of #70989 - eddyb:mir-opt-32-pr-ci, r=Mark-Simulacrumbors-1/+18
ci: run mir-opt tests on PR CI also as 32-bit (for `EMIT_MIR_FOR_EACH_BIT_WIDTH`). Background: #69916 and [`src/test/mir-opt/README.md`](https://github.com/rust-lang/rust/blob/master/src/test/mir-opt/README.md): > By default 32 bit and 64 bit targets use the same dump files, which can be problematic in the presence of pointers in constants or other bit width dependent things. In that case you can add > > ``` > // EMIT_MIR_FOR_EACH_BIT_WIDTH > ``` > > to your test, causing separate files to be generated for 32bit and 64bit systems. However, if you change the output of such a test (intentionally or not), or if you add a test and it varies between 32-bit and 64-bit platforms, you have to run this command (for a x64 linux host): `./x.py test --stage 1 --target x86_64-unknown-linux-gnu --target i686-unknown-linux-gnu --bless src/test/mir-opt` Otherwise, bors trying to merge the PR will fail, since we test 32-bit targets there. But we don't on PR CI, which means there's no way the PR author would know (unless they were burnt by this already and know what to look for). This PR resolves that by running `mir-opt` tests for ~~`i686-unknown-linux-gnu`~~, on PR CI. **EDIT**: switched to `armv5te-unknown-linux-gnueabi` to work around LLVM 7 crashes (see https://github.com/rust-lang/compiler-builtins/pull/311#issuecomment-612270089), found during testing. cc @rust-lang/wg-mir-opt @rust-lang/infra
2020-04-11ci: run mir-opt tests on PR CI also as 32-bit (for ↵Eduard-Mihai Burtescu-1/+18
`EMIT_MIR_FOR_EACH_BIT_WIDTH`).
2020-04-10Auto merge of #66605 - GuillaumeGomez:drop-python2, r=Mark-Simulacrumbors-91/+93
Stop explicitly depending on python 2 This PR revises our previous policy of officially only supporting and testing with python 2 in the CI environment to instead test with python 3. It also changes the defaults to python 3 in our various scripts (usually, by way of `python` rather than `python3` to preserve compatibility with systems that do not have a python 3 available). The effect of this is that we expect all new patches to support python 3 (and will test as such). We explicitly also expect that patches support python 2.7 as well -- and test as such, though only on one builder. This is intended as a temporary, though likely long-lived, measure to preserve compatibility while looking towards the future which is likely to be a python 3 only world. We do not at this point set a timeline for when we'll drop support for python 2.7; it's plausible that this is months or years into the future, depending on how quickly the ecosystem drops support and how painful it is for us to maintain that support over time. Closes #65063 (as far as I can tell; please file explicit and separate issues or PRs if not).
2020-04-10Enforce Python 3 as much as possibleGuillaume Gomez-91/+93
2020-04-10Auto merge of #70619 - etherealist:musl_lld, r=Mark-Simulacrumbors-0/+1
Enable rust-lld on dist-x86_64-musl Add rust-lld to rustup llvm-tools-preview on nightly for musl I am using a musl distro on my workstation, with `RUSTFLAGS="-C target-feature=-crt-static"` this works fine. I know that `x86_64-unknown-linux-musl` was originally only meant as a target and not as a host. But most problems have been fixed, and I have fewer problems with `unknown` (rustup) than when I am using `x86_64-alpine-linux-musl` (rust installed by the distro). The only thing I am missing is rust-lld in llvm-tools-preview on nightly. I needed rust-lld for a wasm tutorial. I built rust-lld and tested it with that tutorial, and it worked well. I asked [here](https://users.rust-lang.org/t/enable-rust-lld-on-x86-64-unknown-linux-musl/39851) where to request to enable lld and ended up doing this PR. I compared llvm-tools-preview `nightly-x86_64-unknown-linux-musl` and `nightly-x86_64-unknown-linux-gnu`: only rust-lld is missing in musl. I tested the change using: ```bash ./src/ci/docker/run.sh dist-x86_64-musl ``` And I checked that the resulting rust-lld binary runs.
2020-04-04Auto merge of #69898 - spastorino:rename-rustc-guide2, r=Xanewokbors-1/+1
Move rustc-guide submodule to rustc-dev-guide r? @pietroalbini
2020-04-03Rollup merge of #68334 - andre-richter:master, r=japaricMazdak Farrokhzad-0/+15
AArch64 bare-metal targets: Build rust-std This PR complements https://github.com/rust-lang/rust/pull/68253
2020-03-31Enable rust-lld on dist-x86_64-muslDavid Sonder-0/+1
Add rust-lld to llvm-tools-preview on nightly for musl
2020-03-30Deduplicate crosstool-ng.shBen Wolsieffer-30/+6
2020-03-25Upgrade GCC to 8.3.0, glibc to 2.17.0 and crosstool-ng to 1.24.0 for ↵Ben Wolsieffer-739/+1055
dist-arm-linux and dist-armhf-linux
2020-03-24Move rustc-guide submodule to rustc-dev-guideSantiago Pastorino-1/+1
2020-03-24ci: add github actions configurationPietro Albini-1/+2
2020-03-23Rollup merge of #70159 - alexcrichton:update-wasi, r=pietroalbiniMazdak Farrokhzad-1/+1
Update the bundled wasi-libc with libstd Brings in WebAssembly/wasi-libc#184 which can help standalone programs with environment variables!
2020-03-21Rollup merge of #70054 - rojamd:android-pgo, r=michaelwoeristerMazdak Farrokhzad-0/+1
Build dist-android with --enable-profiler This will make the runtime available to enable PGO for Rust code in Firefox on Android. r? @michaelwoerister
2020-03-19Update the bundled wasi-libc with libstdAlex Crichton-1/+1
Brings in WebAssembly/wasi-libc#184 which can help standalone programs with environment variables!
2020-03-17Rollup merge of #69688 - JohnTitor:move-tidy, r=Mark-SimulacrumMazdak Farrokhzad-1/+2
Move tidy check to mingw-check Fixes #69613
2020-03-16Build dist-android with --enable-profilerrojamd-0/+1
2020-03-12Add Node.js to PR CI imageOliver Middleton-1/+2
This should allow the `rustdoc-js` and `rustdoc-js-std` test suites to run automatically on PRs.
2020-03-05Move tidy check to mingw-checkYuki Okushi-1/+2
2020-02-28AArch64 bare-metal targets: Build rust-stdAndre Richter-0/+15
This patch enables building of rust-std for the aarch64 bare-metal targets. For the compiler intrinsics, it fetches the AArch64 bare-metal target (aarch64-none-elf) GCC for the A-profile provided by ARM itself from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads
2020-02-10Fix SGX RWLock representation for UnsafeCell niche fixJethro Beekman-1/+1
2020-01-21for now, do not build rust-std for the armv7a-none-eabihf targetJorge Aparicio-1/+2
it needs some upstream changes in the build script of the compiler-builtins crate
2020-01-20Merge branch 'master' into bare-metal-cortex-aJorge Aparicio-1/+978
2020-01-18Auto merge of #68037 - msizanoen1:riscv-ci, r=alexcrichtonbors-0/+977
Distribution CI for riscv64gc-unknown-linux-gnu This modifies `dist-various-1` to build the standard library for RISC-V GNU/Linux. r? @alexcrichton
2020-01-15add bare metal ARM Cortex-A targets to rustcJorge Aparicio-0/+4
-> `rustc --target armv7-none-eabi` will work also build rust-std (rustup) components for them -> `rustup target add armv7-none-eabi` will work
2020-01-14Update the wasi-libc bundled with libstdAlex Crichton-1/+1
2020-01-12Auto merge of #67831 - mati865:ci-images-upgrade, r=pietroalbinibors-2/+2
ci: bump ubuntu 19.04 images to 19.10 Ubuntu 19.04 goes EOL this month.
2020-01-11Distribution CI for RISC-V GNU/Linuxmsizanoen1-0/+977
2020-01-03ci: bump ubuntu 19.04 images to 19.10Mateusz Mikuła-2/+2
Ubuntu 19.04 goes EOL this month.
2020-01-02Set a lower ThinLTO import limit for PR CI image.Michael Woerister-1/+3
2019-12-10Move CI to new builtin check-toolstateMark Rousskov-234/+2
2019-12-06Add note to src/ci/docker/README.md about multiple docker imagesAaron Hill-0/+7
I spent a while debugging a strage linker error about an outdated `glibc` version, only to discover that it was caused by a stale `obj` directory. It wasn't obviously to be that using the same obj dir with multiple Docker images (for the same target triple) could be a problem. This commit adds a note to the README, which should hopefully be helpful to anyone else who runs into this issue.
2019-12-05Update the revision of wasi-libc used in wasm32-wasiAlex Crichton-1/+1
This commit updates the `wasi-libc` repository used to build the wasm32-wasi target's libstd to ensure that both libstd and libc are using the same wasi snapshot version.
2019-12-02Update the minimum external LLVM to 7Josh Stone-3/+3
LLVM 7 is over a year old, which should be plenty for compatibility. The last LLVM 6 holdout was llvm-emscripten, which went away in #65501. I've also included a fix for LLVM 8 lacking `MemorySanitizerOptions`, which was broken by #66522.
2019-11-22ci: add support for GitHub Actions in the CI scriptsPietro Albini-0/+2
2019-11-19Rollup merge of #66090 - pietroalbini:ci-improvements, r=alexcrichtonMazdak Farrokhzad-9/+38
Misc CI improvements This PR contains some misc improvements to our CI configuration: * The environment variables for MinGW builders were greatly simplified, with just `CUSTOM_MINGW=1` to tell the install scripts to install the vendored copy. All the others (`MINGW_URL`, `MINGW_DIR`, `MINGW_ARCHIVE` and `MSYS_BITS`) are detected either from the builder name or the environment. * Collecting CPU stats and running the build were moved into scripts. * Toolstate scripts validation was previously a separate step, ran just when `IMAGE=mingw-check`. This moves the validation code inside the actual image. * Vendored copies are now fetched from https://ci-mirrors.rust-lang.org instead of directly from the bucket. r? @alexcrichton
2019-11-12ci: download curl and openssl from s3 for dist-x86_64-linuxPietro Albini-2/+9
CentOS 5 only supports SSLv3 without SNI, and to get newer protocols working we need to download and compile OpenSSL and cURL from our mirror. Because of that, we can't use the CDN, as CloudFront requires TLSv1 with SNI. This commit changes the dist-x86_64-linux image to bypass the CDN for OpenSSL and cURL.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-14 13:04:27 +0000