about summary refs log tree commit diff
path: root/src/ci/docker/x86_64-gnu-tools
AgeCommit message (Collapse)AuthorLines
2020-07-03ci: move all x86_64 runners to the host-x86_64 directoryPietro Albini-51/+0
We need to add runners designed for an aarch64 host system, and it'd be nice to return an error message if someone tries to run an image designed for an host architecture in another one. To start the work on this, this commit moves all the existing builders in the host-x86_64 directory, and changes the run.sh script to look up the image in the correct directory based on the host architecture.
2020-06-26Remove mdbook-linkcheck.Eric Huss-3/+0
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-04-30Turn of rustc-dev-guide toolstate for nowmark-1/+0
2020-04-10Enforce Python 3 as much as possibleGuillaume Gomez-3/+3
2020-03-24Move rustc-guide submodule to rustc-dev-guideSantiago Pastorino-1/+1
2019-12-10Move CI to new builtin check-toolstateMark Rousskov-234/+2
2019-10-30ci: move toolstates.json to /tmp/toolstate/ and docker mount itPietro Albini-3/+4
Before this commit toolstates.json was stored in /tmp and it wasn't mounted outside the build container. That caused uploading the file in the upload-artifacts task to fail, as the file was missing on the host. Mounting /tmp/toolstates.json alone is not the best approach: if the file is missing when the container is started the Docker engine will create a *directory* named /tmp/toolstates.json. The Docker issue could be solved by pre-creating an empty file named /tmp/toolstates.json, but doing that could cause problems if bootstrap fails to generate the file and the toolstate scripts receive an empty JSON. The approach I took in this commit is to instead mount a /tmp/toolstate directory inside Docker, and create the toolstates.json file in it. That also required a small bootstrap change to ensure the directory is created if it's missing.
2019-08-09Check links on all platforms when running locallyMateusz Mikuła-0/+3
2019-08-08remove test-miri flag from bootstrapRalf Jung-1/+0
2019-08-03ci: move .azure-pipelines to src/ci/azure-pipelinesPietro Albini-1/+2
2019-07-28Rollup merge of #62759 - mark-i-m:rustc-guide-toolstate-check, r=kennytmMazdak Farrokhzad-5/+33
Actually add rustc-guide to toolstate, don't fail builds for the guide cc @ehuss r? @kennytm
2019-07-25ci: gate toolstate repo pushes on the TOOLSTATE_PUBLISH envvarPietro Albini-1/+1
Unfortunately due to an Azure quirk the TOOLSTATE_REPO_ACCESS_TOKEN is not suitable to gate whether to push new commits to the repo, as if it's not defined on the Azure side it will actually be set to the literal `$(TOOLSTATE_REPO_ACCESS_TOKEN)`, which screws everything up. This instead adds another, non-secret environment variable to gate publishing: TOOLSTATE_PUBLISH. As non-secret environment variables behave correctly this fixes the issue.
2019-07-23add back check for update prsMark Mansi-0/+1
2019-07-23more commentsRalf Jung-0/+1
2019-07-23more callback docsRalf Jung-4/+7
2019-07-23more comments for toolstate scriptsRalf Jung-3/+14
2019-07-18Update src/ci/docker/x86_64-gnu-tools/checkregression.pyWho? Me?!-1/+1
Co-Authored-By: kennytm <kennytm@gmail.com>
2019-07-18embedded-book failures don't block betaMark Mansi-1/+1
2019-07-18Update src/ci/docker/x86_64-gnu-tools/checkregression.pyWho? Me?!-1/+1
Co-Authored-By: Ralf Jung <post@ralfj.de>
2019-07-18Update src/ci/docker/x86_64-gnu-tools/checktools.shWho? Me?!-1/+1
Co-Authored-By: Ralf Jung <post@ralfj.de>
2019-07-18add a few comments for the toolstate stuffRalf Jung-4/+12
2019-07-18Regressions ok for miri tooWho? Me?!-1/+1
Co-Authored-By: kennytm <kennytm@gmail.com>
2019-07-17don't fail builds for rustc-guideMark Mansi-2/+5
2019-07-17actually test rustc-guide with toolstateMark Mansi-0/+1
2019-07-15ci: Remove Travis/AppVeyor configurationAlex Crichton-23/+3
Now that we've fully moved to Azure Pipelines and bors has been updated to only gate on Azure this commit removes the remaining Travis/AppVeyor support contained in this repository. Most of the deletions here are related to producing better output on Travis by folding certain sections. This isn't supported by Azure so there's no need to keep it around, and if Azure ever adds support we can always add it back!
2019-07-06Track rustc-guide on toolstateAndré Luis Leal Cardoso Junior-0/+1
2019-06-13ci: Enable toolstate tracking on AzureAlex Crichton-1/+1
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-08checktools: unify grepping the TOOLSTATE fileRalf Jung-3/+10
2019-05-23Revert edition-guide toolstate overrideEric Huss-3/+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
2019-05-15Update booksEric Huss-1/+3
2019-03-27Update booksEric Huss-0/+2
2019-03-09Track embedded-book in the toolstatekennytm-0/+1
2019-02-04Add embedded bookJames Munns-0/+1
2018-12-25Remove licensesMark Rousskov-30/+0
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-17Block beta if clippy breaks.kennytm-7/+9
Don't fail master pull request when an unrelated tool is not test-pass.
2018-07-03Fix the tool's path in toolstate verification.kennytm-4/+4
This ensure we do block the tools when they are broken during an update.
2018-06-15Fix checkregression breakage of toolstate builder on AppVeyor.kennytm-1/+1
2018-06-10Do not push a commit if the toolstate is unchanged.kennytm-12/+27
This should greatly reduce the commits on the rust-toolstate repository. `publish_toolstate.py` defaults to keep the old status if a new one is not found, so nothing needs to be changed to that file.
2018-05-14Migrate the toolstate update bot to rust-highfivekennytm-1/+1
2018-05-09Document the checktools scriptOliver Schneider-0/+7
2018-05-09Don't require clippy/miri for betaOliver Schneider-11/+26
2018-04-23Fix the miri toolOliver Schneider-1/+1
2018-02-24Run the external doc tests in tools job.kennytm-12/+27
2018-02-23Disallow toolstate regression at the last week of the 6-week cycle.kennytm-0/+49
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-15 13:04:18 +0000