summary refs log tree commit diff
path: root/src/ci
AgeCommit message (Collapse)AuthorLines
2019-08-12Add date debug to CIMark Rousskov-0/+9
2019-08-12Switch to stable channelMark Rousskov-1/+1
2019-08-03ci: move .azure-pipelines to src/ci/azure-pipelinesPietro Albini-0/+841
2019-08-03Require a value for configure --debuginfo-levelJosh Stone-1/+1
In `configure.py`, using the `o` function creates an enable/disable boolean setting, and writes `true` or `false` in `config.toml`. However, rustbuild is expecting to parse a `u32` debuginfo level. We can change to the `v` function to have the options require a value.
2019-07-22ci: pin awscli dependenciesPietro Albini-0/+13
docutils 0.15, a dependency of awscli, broke our CI since it's not compatible with Python 2 due to a bug. This pins all the dependencies of awscli with docutils 0.14, to make sure this kind of regressions doesn't happen again.
2019-07-03Switch to beta channelMark Rousskov-1/+1
2019-06-30Auto merge of #61252 - indygreg:upgrade-musl, r=alexcrichtonbors-1/+1
Update musl to 1.1.22 This is the latest available version. I noticed Rust wasn't using the latest version when I attempted to have Cargo link object files produced outside of Cargo / Rust's toolchain and was getting missing symbol errors. Those missing symbols were added in 1.1.21 and 1.1.22. I'm not fully sure of the implications of this change or how comprehensive the test coverage is. Upstream changes in 1.1.21 and 1.1.22 can be found at https://git.musl-libc.org/cgit/musl/tree/WHATSNEW?h=v1.1.22&id=e97681d6f2c44bf5fa9ecdd30607cb63c780062e#n1989.
2019-06-26ci: Disable assertions in PR buildsAlex Crichton-0/+6
The PR builder on Azure currently takes 2.5h which is a bit long, so this commit disables debug assertions and llvm assertions in an attempt to speed up that builder and have PR builds come back a bit more quickly. Other builders continue to enable debug assertions and test the compiler there.
2019-06-19Rollup merge of #61839 - alexcrichton:pr-and-master-builds, r=pietroalbiniMazdak Farrokhzad-17/+2
ci: Add a script for generating CPU usage graphs This commit checks in a script which generates CPU usage graphs over time, expanding on the previous comment that was include in the collection file. Some example graphs from the [latest build](https://dev.azure.com/rust-lang/rust/_build/results?buildId=717) look like: ![dist-x86_64-apple](https://user-images.githubusercontent.com/64996/59520676-16c5b000-8e90-11e9-9188-27001911f270.png) ![x86_64-msvc-1](https://user-images.githubusercontent.com/64996/59520677-175e4680-8e90-11e9-8568-4b564807324e.png) ![x86_64-mingw-1](https://user-images.githubusercontent.com/64996/59520680-175e4680-8e90-11e9-939d-a73c7224582f.png) ![test-various](https://user-images.githubusercontent.com/64996/59520682-175e4680-8e90-11e9-9980-900ed4eeb8f4.png)
2019-06-18ci: Add a script for generating CPU usage graphsAlex Crichton-17/+2
This commit checks in a script which generates CPU usage graphs over time, expanding on the previous comment that was include in the collection file.
2019-06-15Auto merge of #59752 - Zoxc:dylib-fix, r=alexcrichtonbors-4/+0
Limit dylib symbols This makes `windows-gnu` match the behavior of `windows-msvc`. It probably doesn't make sense to export these symbols on other platforms either.
2019-06-13ci: Enable toolstate tracking on AzureAlex Crichton-1/+2
Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up.
2019-06-12Ignore NVPTX testsJohn Kåre Alsaker-4/+0
2019-06-12Auto merge of #61587 - alexcrichton:distcheck-no-assertions, r=pietroalbinibors-0/+7
ci: Disable LLVM/debug assertions for distcheck The purpose of distcheck is to test `./x.py test` from a tarball, not to test that all assertions pass all the time. These assertions are largely just redundant with other builders, so skip the assertions for now and save a good chunk of time on CI. cc #61185
2019-06-12Rollup merge of #61632 - alexcrichton:azure-pipelines-cpu, r=pietroalbiniMazdak Farrokhzad-0/+175
ci: Collect CPU usage statistics on Azure This commit adds a script which we'll execute on Azure Pipelines which is intended to run in the background and passively collect CPU usage statistics for our builders. The intention here is that we can use this information over time to diagnose issues with builders, see where we can optimize our build, fix parallelism issues, etc. This might not end up being too useful in the long run but it's data we've wanted to collect for quite some time now, so here's a stab at it! Comments about how this is intended to work can be found in the python script used here to collect CPU usage statistics. Closes #48828
2019-06-11ci: Collect CPU usage statistics on AzureAlex Crichton-0/+175
This commit adds a script which we'll execute on Azure Pipelines which is intended to run in the background and passively collect CPU usage statistics for our builders. The intention here is that we can use this information over time to diagnose issues with builders, see where we can optimize our build, fix parallelism issues, etc. This might not end up being too useful in the long run but it's data we've wanted to collect for quite some time now, so here's a stab at it! Comments about how this is intended to work can be found in the python script used here to collect CPU usage statistics. Closes #48828
2019-06-08Auto merge of #61655 - RalfJung:checktools, r=kennytmbors-3/+10
checktools: unify grepping the TOOLSTATE file The file was grepped twice but in a different way. This unifies the code to make sure it is consistent. Or were these deliberately not doing the same thing? That seems strange though. I wouldn't know how to test these changes.
2019-06-08checktools: unify grepping the TOOLSTATE fileRalf Jung-3/+10
2019-06-06ci: Disable LLVM/debug assertions for distcheckAlex Crichton-0/+7
The purpose of distcheck is to test `./x.py test` from a tarball, not to test that all assertions pass all the time. These assertions are largely just redundant with other builders, so skip the assertions for now and save a good chunk of time on CI. cc #61185
2019-06-06ci: Disable LLVM/debug assertions for asmjs builderAlex Crichton-0/+8
This shaves of 50 minutes of cycle time on Azure and will likely also save a significant chunk of time on Travis. The assertions here aren't really buying us much over other builders with assertions already enabled, so let's disable them for this builder. cc #61185
2019-06-03ci: Reenable step timings on AppVeyorAlex Crichton-0/+2
This was accidentally regressed in #60777 by accident, and we've stopped printing out step timings on AppVeyor recently reducing the ability for us to track build times over time!
2019-05-31Auto merge of #61300 - indygreg:upgrade-cross-make, r=sanxiynbors-2/+2
Update musl-cross-make to 0.9.8 This version uses musl 1.1.22 and GCC 6.4.0 by default. It also contains support for newer binutils and GCC versions, should we want to bump those as well. But I'm purposefully limiting this patch in order to reduce the surface area for controversy.
2019-05-30Auto merge of #61353 - alexcrichton:less-tools, r=pietroalbinibors-5/+3
ci: Favor SCRIPT instead of RUST_CHECK_TARGET Since #61212 we've been timing out on OSX, and this looks to be because we're building tools like Cargo and the RLS twice instead of once. This turns out to be a slight bug in our configuration. CI builders using the `RUST_CHECK_TARGET` directive actually execute `make all` just before their acual target. In `make all` we're building a stage2 cargo, and then in `make dist` we're building a stage1 cargo. Other builders use `SCRIPT` which provides explicit control over what `x.py` script, for example, is used to execute the build. This moves almost all targets to using `SCRIPT` to ensure that we're explicitly specifying what's being built where. Additionally this updates the logic of `RUST_CHECK_TARGET` to remove the pre-flight tidy as well as the pre-flight `make all`. The system LLVM builder (run on PRs) now explicitly runs tidy first and then runs the rest of the test suite.
2019-05-30ci: Favor SCRIPT instead of RUST_CHECK_TARGETAlex Crichton-5/+3
Since #61212 we've been timing out on OSX, and this looks to be because we're building tools like Cargo and the RLS twice instead of once. This turns out to be a slight bug in our configuration. CI builders using the `RUST_CHECK_TARGET` directive actually execute `make all` just before their acual target. In `make all` we're building a stage2 cargo, and then in `make dist` we're building a stage1 cargo. Other builders use `SCRIPT` which provides explicit control over what `x.py` script, for example, is used to execute the build. This moves almost all targets to using `SCRIPT` to ensure that we're explicitly specifying what's being built where. Additionally this updates the logic of `RUST_CHECK_TARGET` to remove the pre-flight tidy as well as the pre-flight `make all`. The system LLVM builder (run on PRs) now explicitly runs tidy first and then runs the rest of the test suite.
2019-05-30Rollup merge of #61322 - pietroalbini:debug-windows-submodule-cloning, ↵Mazdak Farrokhzad-0/+4
r=alexcrichton ci: display more debug information in the init_repo script I'm *really* confused about the error message [while cloning submodules on Windows on Azure](https://dev.azure.com/rust-lang/e71b0ddf-dd27-435a-873c-e30f86eea377/_apis/build/builds/295/logs/506): ``` /usr/bin/tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options Try '/usr/bin/tar --help' or '/usr/bin/tar --usage' for more information. ``` It doesn't make sense for it to execute a command without any of those flags since they're clearly added: https://github.com/rust-lang/rust/blob/81970852e172c04322cbf8ba23effabeb491c83c/src/ci/init_repo.sh#L45 So this adds `set -x` to the script to hopefully catch what command it's executing. r? @alexcrichton cc https://github.com/rust-lang/rust/issues/61301
2019-05-30Rollup merge of #61284 - alexcrichton:less-s3, r=pietroalbiniMazdak Farrokhzad-9/+9
Update all s3 URLs used on CI with subdomains Ensure that they're all forwards-compatible with AWS updates happening next year by ensuring the bucket name shows up in the domain name. Closes #61168
2019-05-29ci: display more debug information in the init_repo scriptPietro Albini-0/+4
2019-05-29Update all s3 URLs used on CI with subdomainsAlex Crichton-9/+9
Ensure that they're all forwards-compatible with AWS updates happening next year by ensuring the bucket name shows up in the domain name. Closes #61168
2019-05-28Update musl-cross-make to 0.9.8Gregory Szorc-2/+2
This version uses musl 1.1.22 and GCC 6.4.0 by default. It also contains support for newer binutils and GCC versions, should we want to bump those as well. But I'm purposefully limiting this patch in order to reduce the surface area for controversy.
2019-05-28Revert "Disable solaris target since toolchain no longer builds"Bastian Germann-7/+5
This reverts commit e764f475ca7fffd6167ea991afc7d1b2b3f642dc. Fixes #61174.
2019-05-28Update musl to 1.1.22.Gregory Szorc-1/+1
This is the latest available version. I noticed Rust wasn't using the latest version when I attempted to have Cargo link object files produced outside of Cargo / Rust's toolchain and was getting missing symbol errors. Those missing symbols were added in 1.1.21 and 1.1.22. I'm not fully sure of the implications of this change or how comprehensive the test coverage is. Upstream changes in 1.1.21 and 1.1.22 can be found at https://git.musl-libc.org/cgit/musl/tree/WHATSNEW?h=v1.1.22&id=e97681d6f2c44bf5fa9ecdd30607cb63c780062e#n1989.
2019-05-26Docker: remove environment variable `CC_armebv7r_none_eabi`Paolo Teti-1/+0
`cc-rs` take care of selecting the tool-chain, so this ENV variable can be safely removed.
2019-05-25Rollup merge of #61110 - ehuss:revert-edition-override, r=Mark-SimulacrumMazdak Farrokhzad-3/+1
Revert edition-guide toolstate override Closes #60929
2019-05-24Auto merge of #60777 - pietroalbini:azure-pipelines, r=alexcrichtonbors-15/+43
Add Azure Pipelines configuration Huge thanks to ＠johnterickson and ＠willsmythe for writing the initial config! :heart: I applied some changes to the initial config and disabled most of the builders since we're not going to run all of them during the initial step for the evaluation. [More details about our plans for the Azure Pipelines evaluation.](https://internals.rust-lang.org/t/update-on-the-ci-investigation/10056) r? ＠alexcrichton ＠kennytm cc ＠rust-lang/infra ＠ethomson ＠rylev
2019-05-24ci: Enable debuginfo for std only if release channel is setVadim Petrochenkov-1/+1
2019-05-24rustbuild: Simplify debuginfo configurationVadim Petrochenkov-0/+1
2019-05-23Revert edition-guide toolstate overrideEric Huss-3/+1
2019-05-23Rollup merge of #61055 - bgermann:master, r=sanxiynMazdak Farrokhzad-1/+1
Solaris CI: Build with dilos2 stable dilos2-testing has problems since the last repository update, so get the packages from dilos2 stable. Fixes #61022.
2019-05-22Solaris CI: Build with dilos2 stablebgermann-1/+1
dilos2-testing has problems since the last repository update, so get the packages from dilos2 stable. Fixes #61022.
2019-05-22Disable LLVM/debug assertions in gnu-full-bootstrapAlex Crichton-0/+6
This builder already is very close to the 2 hour mark and the debug assertions aren't really buying us anything over what all the other containers are enabling, so let's disable them for this slow builder.
2019-05-22Final cleanupsAlex Crichton-1/+0
* Clean up the `install-windows-build-deps.yml` file and add some more comments where appropriate. * Add some comments to `run.yml` * Don't fast path the `rustfmt` submodule, but we'll take care of that later if necessary.
2019-05-21Merge remote-tracking branch 'origin/master' into azure-pipelinesAlex Crichton-9/+18
2019-05-21Disable solaris target since toolchain no longer buildsAlex Crichton-5/+7
2019-05-21Use new-style s3 urls in docker download scriptAlex Crichton-1/+1
2019-05-21ci: fix tidyPietro Albini-1/+2
2019-05-20Check out rustfmt submodule through tarballsAlex Crichton-1/+1
This takes 30+ seconds to check out on Windows, so let's speed it up through a tarball like we do other big git repositories.
2019-05-20Make sure sccache not present doesn't kill the buildAlex Crichton-1/+1
2019-05-19Reverse RLS toolstate check overrideIgor Matuszewski-6/+1
As per https://github.com/rust-lang/rust/pull/60946#issuecomment-493707005
2019-05-17Rollup merge of #60791 - ehuss:update-books, r=Mark-SimulacrumManish Goregaokar-1/+3
Update books ## nomicon 1 commits in fb29b147be4d9a1f8e24aba753a7e1de537abf61..c656171b749b7307f21371dd0d3278efee5573b8 2019-04-22 19:10:29 -0400 to 2019-04-25 15:31:26 -0400 - Lifetimes: Updates to incorporate NLL (rust-lang-nursery/nomicon#101) ## reference 5 commits in 2a2de9ce095979978ad7b582daecf94e4070b916..862b669c395822bb0938781d74f860e5762ad4fb 2019-04-22 10:25:52 -0700 to 2019-05-04 23:41:35 -0700 - Typo (rust-lang-nursery/reference#606) - Added missing ? to Generics from InherentImpl and TraitImpl (rust-lang-nursery/reference#604) - Add missing ( to ExternalFunctionItem (rust-lang-nursery/reference#603) - Remove unneeded | from AssignmentExpression (rust-lang-nursery/reference#601) - Remove unneeded ( from TypePathSegment (rust-lang-nursery/reference#602) ## book 6 commits in db919bc6bb9071566e9c4f05053672133eaac33e..29fe982990e43b9367be0ff47abc82fb2123fd03 2019-04-15 20:11:03 -0400 to 2019-05-15 17:48:40 -0400 - Ignore a non-compiling test listing and add code to fix a test listing - Remove nostarch snapshots I've checked in layout - Reword error messages to maybe not need to wrap lines in print - This example doesn't compile but wasn't marked as such - Update install instructions for VS 2019 (rust-lang/book#1923) - Switch IRC to Discord ## rust-by-example 9 commits in 1ff0f8e018838a710ebc0cc1a7bf74ebe73ad9f1..811c697b232c611ed754d279ed20643a0c4096f6 2019-04-15 08:15:32 -0300 to 2019-04-28 18:56:42 -0300 - Fix typo in dsl.md (rust-lang/rust-by-example#1187) - File read lines (rust-lang/rust-by-example#1186) - For https://github.com/rust-lang/rust-by-example/issues/1184 closes rust-lang/rust-by-example#1184 (rust-lang/rust-by-example#1185) - Link to Reference for macro_rules designators (rust-lang/rust-by-example#1182) - Improve section Meta/Docs (rust-lang/rust-by-example#1183) - Small improvements to various files (rust-lang/rust-by-example#1173) - 19.2 Vectors Error in Code Example (rust-lang/rust-by-example#1178) - For https://github.com/rust-lang/rust-by-example/issues/1175 (rust-lang/rust-by-example#1176) - For https://github.com/rust-lang/rust-by-example/issues/1179 (rust-lang/rust-by-example#1180) ## rustc-guide 12 commits in 99e1b1d53656be08654df399fc200584aebb50e4..3cb727b62b953d59b4360d39aa68b6dc8f157655 2019-04-20 09:57:54 -0500 to 2019-05-07 09:53:32 -0500 - Fix typo, 'which' repeated twice - [canonicalization] fix result canonicalization example (rust-lang/rustc-guide#304) - Rename to RUSTC_LOG - Added mention of universal ctags - Fix link in walkthrough - Remove IRC from discussion chats - Bring the updating LLVM guide up to date - use nightly rust for ci - Fixed broken chalk links - Add documentation for two-phase borrows - Explain new powers of the `treat-err-as-bug` flag - Update lowering-module test case ## edition-guide 3 commits in c413d42a207bd082f801ec0137c31b71e4bfed4c..581c6cccfaf995394ea9dcac362dc8e731c18558 2019-04-22 01:14:56 +0200 to 2019-05-06 12:47:44 -0700 - Fix typo in controlling-panics-with-std-panic.md (rust-lang-nursery/edition-guide#158) - Fix links for book editions. (rust-lang-nursery/edition-guide#149) - Update now that NLL is enabled in 2015. (rust-lang-nursery/edition-guide#157) ## embedded-book 3 commits in de3d55f521e657863df45260ebbca1b10527f662..9858872bd1b7dbba5ec27dc30d34eba00acd7ef9 2019-04-22 12:58:28 +0000 to 2019-05-02 18:56:54 +0000 - Update linux.md (rust-embedded/book#167) - Clarify list of available targets for installation (rust-embedded/book#165) - minor grammar fix (rust-embedded/book#188)
2019-05-16Update cargoEric Huss-1/+6
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 10:26:27 +0000