about summary refs log tree commit diff
path: root/src/ci/docker
AgeCommit message (Collapse)AuthorLines
2019-01-03ci: Upgrade Travis to XenialAlex Crichton-3/+5
In theory we shouldn't require trusty so long as docker continues to work!
2018-12-25Remove licensesMark Rousskov-507/+0
2018-12-24Rollup merge of #57010 - phansch:run_compiletest_tests_on_ci, r=kennytmMazdak Farrokhzad-1/+2
Actually run compiletest tests on CI I was assuming that https://github.com/rust-lang/rust/pull/56792 would have resulted in compiletest tests being executed on CI. However, I couldn't find any mentions of the unit test names in any CI logs. This adds the compiletest test execution to the checktools.sh script.
2018-12-23Auto merge of #56892 - alexcrichton:new-llvm, r=michaelwoeristerbors-17/+14
rustc: Update Clang used to build LLVM on Linux This commit updates from LLVM 7.0.0 to git revisions of clang/llvm/lld to build LLVM on our dist builders for Linux. The goal of this is to fix #56849 by picking up a fix [1] in LLD. Closes #56849 [1]: https://github.com/llvm-mirror/lld/commit/3be4e82db78b46a8ca349b2b799dec620a6f159f
2018-12-20Move compiletest test run to mingw-check builderPhilipp Hansch-6/+2
This way, checktools.sh continues to be used only for tools that are published later on.
2018-12-20Run compiletest tests on CIPhilipp Hansch-0/+5
I was assuming that https://github.com/rust-lang/rust/pull/56792 would have resulted in compiletest tests being executed in CI. However, I couldn't find any mentions of the unit test names in any CI logs. This adds the compiletest test execution to the checktools.sh script.
2018-12-19Rollup merge of #56947 - hsivonen:neon, r=alexcrichtonPietro Albini-0/+2
Add targets thumbv7neon-linux-androideabi and thumbv7neon-unknown-linux-gnueabihf These two targets enable both thumb-mode and NEON for ARMv7 CPUs. This another attempt at #49902, which cannot be reopened. Between that PR and this one, some subrepos with C code whose build systems were failing went away.
2018-12-17Auto merge of #56642 - nikic:llvm-6, r=alexcrichtonbors-2/+2
Bump minimum required LLVM version to 6.0 Based on the discussion in #55842, while the overall position of Rust wrt LLVM continues to be contentious, there does seem to be a consensus that there is no need for continued support of LLVM 5. This PR bumps our version requirement to LLVM 6.0 and makes Travis run against that. I hope that this is going to unblock #52694. If I understand correctly, while this issue still exists in LLVM 6, Ubuntu has backported the relevant patch. r? @alexcrichton
2018-12-16rustc: Update Clang used to build LLVM on LInuxAlex Crichton-17/+14
This commit updates from LLVM 7.0.0 to git revisions of clang/llvm/lld to build LLVM on our dist builders for Linux. The goal of this is to fix #56849 by picking up a fix [1] in LLD. Closes #56849 [1]: https://github.com/llvm-mirror/lld/commit/3be4e82db78b46a8ca349b2b799dec620a6f159f
2018-12-13Add targets thumbv7neon-linux-androideabi and ↵Henri Sivonen-0/+2
thumbv7neon-unknown-linux-gnueabihf These two targets enable both thumb-mode and NEON for ARMv7 CPUs.
2018-12-11fix rust-lang/rust issue #50583Piers Finlayson-2/+2
2018-12-10Build manifest tool on mingw-check builderMark Rousskov-1/+2
This builder is not really the correct place to put this, but it definitely has the time budget and checking this tool builds on just one platform is more than sufficient.
2018-12-09Bump minimum required LLVM version to 6.0Nikita Popov-2/+2
2018-11-30ci: Only run compare-mode tests on one builderAlex Crichton-1/+3
The run-pass test suite currently takes 30 minutes on Windows, and that appears to be roughly split between two 15 minute runs of the test suite: one without NLL and one with NLL. In discussion on Discord the platform coverage of the NLL compare mode may not necessarily be worth it, so this commit removes the NLL compare mode from tests by default, and then reenables it on only one builder.
2018-11-14Update CI-clang to 7.0.0 for Linux dists.Michael Woerister-4/+4
2018-11-11std: Delete the `alloc_system` crateAlex Crichton-1/+1
This commit deletes the `alloc_system` crate from the standard distribution. This unstable crate is no longer needed in the modern stable global allocator world, but rather its functionality is folded directly into the standard library. The standard library was already the only stable location to access this crate, and as a result this should not affect any stable code.
2018-11-10Auto merge of #55626 - nikic:update-emscripten, r=alexcrichtonbors-17/+12
Update emscripten This updates emscripten to 1.38.15, which is based on LLVM 6.0.1 and would allow us to drop code for handling LLVM 4. The main issue I ran into is that exporting statics through `EXPORTED_FUNCTIONS` no longer works. As far as I understand exporting non-functions doesn't really make sense under emscripten anyway, so I've modified the symbol export code to not even try. Closes #52323.
2018-11-08Update the disabled wasm32 DockerfileNikita Popov-10/+5
2018-11-06Auto merge of #53996 - sekineh:thumb-run, r=japaricbors-1/+2
[CI] Run a `thumbv7m-none-eabi` binary using `qemu-system-arm` [IRR-2018-embedded] ## What's included? - Run a `thumbv7m-none-eabi` binary using `qemu-system-arm` - We are using `cortex-m-rt = "=0.5.4"` which does not use `proc_macro`. (reason: stage2 build of rustc does not work well with `proc_macro` in `run-make` phase.) - We are using GNU LD for now. ## Blocker All resolved. - ~[Waiting] `#[panic_handler]` is not available in stable.~ - [Merged] https://github.com/rust-lang/rust/pull/53619 - ~[Waiting] https://github.com/japaric/lm3s6965evb: does not compile on stable.~ - [OK] dependent crate ~`panic-abort`~ `panic-halt`: already moved to use `#[panic_handler]`. ## Update `#[panic_handler]` will be stabilized in Rust 1.30. CC @kennytm @jamesmunns @nerdyvaishali
2018-11-06Rollup merge of #55644 - glaubitz:powerpcspe-linux, r=alexcrichtonkennytm-0/+26
ci: Add Dockerfile for dist-powerpcspe-linux This adds the Dockerfile for cross-building Rust for the powerpcspe target. It's currently disabled.
2018-11-06Auto merge of #55106 - petrhosek:fuchsia-lld, r=alexcrichtonbors-1/+12
Use lld directly for Fuchsia target Fuchsia already uses lld as the default linker, so there's no reason to always invoke it through Clang, instead we can simply invoke lld directly and pass the set of flags that matches Clang.
2018-11-05Use lld directly for Fuchsia targetPetr Hosek-1/+12
Fuchsia already uses lld as the default linker, so there's no reason to always invoke it through Clang, instead we can simply invoke lld directly and pass the set of flags that matches Clang.
2018-11-04Update llvm-emscriptenNikita Popov-7/+7
This updates emscripten to version 1.38.15, which is based on LLVM 6.0.1.
2018-11-03ci: Add Dockerfile for dist-powerpcspe-linuxJohn Paul Adrian Glaubitz-0/+26
2018-11-02Use `jemalloc-sys` on Linux and OSX compilersAlex Crichton-2/+4
This commit adds opt-in support to the compiler to link to `jemalloc` in the compiler. When activated the compiler will depend on `jemalloc-sys`, instruct jemalloc to unprefix its symbols, and then link to it. The feature is activated by default on Linux/OSX compilers for x86_64/i686 platforms, and it's not enabled anywhere else for now. We may be able to opt-in other platforms in the future! Also note that the opt-in only happens on CI, it's otherwise unconditionally turned off by default. Closes #36963
2018-10-30Update enum debuginfo testsTom Tromey-1/+1
Bug #52452 notes some debuginfo test regressions when moving to gdb 8.1. This series will also cause versions of gdb before 8.2 to fail when a recent LLVM is used -- DW_TAG_variant_part support was not added until 8.2. This patch updates one of the builders to a later version of Ubuntu, which comes with gdb 8.2. It updates the relevant tests to require both a new-enough LLVM and a new-enough gdb; the subsequent patch arranges to continue testing the fallback mode. The "gdbg" results are removed from these tests because the tests now require a rust-enabled gdb. If you read closely, you'll see that some of the lldb results in this patch still look a bit strange. This will be addressed in a subsequent patch; I believe the fix is to disable the Python pretty-printers when lldb is rust-enabled.
2018-10-21Remove the parse-fail test suiteVadim Petrochenkov-1/+0
2018-10-20Update Cargo, build curl/OpenSSL statically via featuresAlex Crichton-0/+39
In addition to to updating Cargo's submodule and Cargo's dependencies, this also updates Cargo's build to build OpenSSL statically into Cargo as well as libcurl unconditionally. This removes OpenSSL build logic from the bootstrap code, and otherwise requests that even on OSX we build curl statically.
2018-09-30[ci] add qemu-system-arm in docker imageHideki Sekine-1/+2
2018-09-28Add DIST_REQUIRE_ALL_TOOLS to CI scriptsChristian Poveda-0/+4
2018-09-21Update musl to 1.1.20.Adrian Budau-7/+1
2018-08-30[RISCV] Add riscv32imc-unknown-none-elf target.David Craven-0/+1
2018-08-29Auto merge of #53245 - michaelwoerister:thinlto-rust-llvm, r=alexcrichtonbors-1/+10
[experimental]: Build LLVM with ThinLTO enabled (2nd attempt) This is https://github.com/rust-lang/rust/pull/51207 revived. This time, I'd like to run actual performance tests to see if it improves compile times.
2018-08-26remove no longer needed Docker imagesJorge Aparicio-70/+0
2018-08-26fix docker build for the armebv7r-none-eabi targetJorge Aparicio-1/+2
2018-08-26add armebv7r-none-eabi targetJorge Aparicio-0/+1
2018-08-26build rust-std components for the Cortex-R targetsJorge Aparicio-1/+4
2018-08-26Add target for Little-endian ARM Cortex-R4F/R5F MCUsPaolo Teti-0/+34
Similar to `armebv7r-none-eabihf`, but for Little-endian MCUs. As example TI RM4x/RM5x are Little-endian Cortex-R4F/R5F MCUs. CI/Dockerfile is intentionally in the disabled folder.
2018-08-20Compile LLVM with ThinLTO for x86_64 Linux dist builds.Michael Woerister-1/+4
2018-08-20Build LLD in addition to Clang in Linux CIMichael Woerister-0/+6
2018-08-19Fix typos found by codespell.Matthias Krüger-1/+1
2018-08-16Revert "Use public DNS server instead of 169.254.169.254 on CI."kennytm-4/+0
This reverts commit 32e8bda4e35ada92beab7236d62520e6c6df8596.
2018-08-04Rollup merge of #52940 - kennytm:move-checktool-protection-week, r=alexcrichtonkennytm-4/+6
Align 6-week cycle check with beta promotion instead of stable release. The regression check is to make beta promotion easier, so it makes more sense to use the Tuesday of the release week (T-2) as the end point of the regression prevention, instead of Thursday (T-0). But since the beta promotion PR is sent at Tuesday evening at UTC, the protection should include the whole Tuesday as well, meaning the 6-week cycle will start from Wednesdays. This will also move the start of the regression protection week one day earlier.
2018-08-01[RISCV] Enable CI.David Craven-0/+1
2018-08-01Align 6-week cycle check with beta promotion instead of stable release.kennytm-4/+6
The regression check is to make beta promotion easier, so it makes more sense to use the Tuesday of the release week (T-2) as the end point of the regression prevention, instead of Thursday (T-0). But since the beta promotion PR is sent at Tuesday evening at UTC, the protection should include the whole Tuesday as well, meaning the 6-week cycle will start from Wednesdays. This will also move the start of the regression protection week one day earlier.
2018-07-29Test clippy first to workaround the derive-new conflict.kennytm-1/+2
2018-07-26Omit the vendor component in Fuchsia triplePetr Hosek-13/+13
Previously, using unknown as the vendor value would lead to the same result, but with the multiarch runtimes support in Clang, the target is now used to locate the runtime libraries and so the format is important. The denormalized format with omitted vendor component is the format we use with Clang and should be using for Rust as well.
2018-07-25Auto merge of #52561 - ljedrz:fixme_cc_271, r=alexcrichtonbors-7/+1
Remove obsolete armv5te vars from the dist-various-1 Dockerfile The [related cc issue](https://github.com/alexcrichton/cc-rs/issues/271) is closed and its changes are in force.
2018-07-24Rollup merge of #52538 - ljedrz:old_musl_i586_flags, r=kennytmkennytm-3/+1
Remove obsolete flags in the i586_musl Dockerfile Resolves an [outdated FIXME](https://github.com/rust-lang/rust/blob/ab8b961677ac5c74762dcea955aa0ff4d7fe4915/src/ci/docker/dist-i586-gnu-i586-i686-musl/Dockerfile#L45) in the Dockerfile for dist-i586-gnu-i586-i686-musl.
2018-07-22Rollup merge of #52465 - sekineh:add-ci-thumb, r=alexcrichtonkennytm-1/+8
Add CI test harness for `thumb*` targets. [IRR-2018-embedded] This pull request will do the following (rather trivial) changes: - Fix #52163. In other words, we enabled `./x.py test src/test/run-make` for `no_std` targets. - Modify `dist-various-1` Dockerfile. - CI now performs `run-make` test run on the targets below: - `thumbv6m-none-eabi` - `thumbv7m-none-eabi` - `thumbv7em-none-eabi` - `thumbv7em-none-eabihf`. - ~~Add `thumb-none` Dockerfile.~~ - ~~Initially, `thumbv7m-none-eabi`, `thumbv7em-none-eabi` and `thumbv7em-none-eabihf` are included as the tested target. `thumbv6m-none-eabi` is disabled for now because LLVM support is not certain.~~ - ~~Add `thumb-none` to .travis.yml~~ Note: - `run-make` tests are not implemented yet. This PR is test harness only. The amount of change is very small, but I'd like to open the pull request while the change is trivial. Because I'm not very used to pull request process, I want to make a small progress first. This PR will be a foundation for later additions. CC @kennytm @jamesmunns @nerdyvaishali
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 15:16:54 +0000