about summary refs log tree commit diff
path: root/src/ci/docker/x86_64-gnu-tools/checktools.sh
AgeCommit message (Collapse)AuthorLines
2020-07-03ci: move all x86_64 runners to the host-x86_64 directoryPietro Albini-26/+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-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-2/+2
2020-03-24Move rustc-guide submodule to rustc-dev-guideSantiago Pastorino-1/+1
2019-12-10Move CI to new builtin check-toolstateMark Rousskov-115/+1
2019-10-30ci: move toolstates.json to /tmp/toolstate/ and docker mount itPietro Albini-1/+2
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-07-28Rollup merge of #62759 - mark-i-m:rustc-guide-toolstate-check, r=kennytmMazdak Farrokhzad-4/+15
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 comments for toolstate scriptsRalf Jung-2/+7
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/+8
2019-07-17don't fail builds for rustc-guideMark Mansi-1/+0
2019-07-17actually test rustc-guide with toolstateMark Mansi-0/+1
2019-07-06Track rustc-guide on toolstateAndré Luis Leal Cardoso Junior-0/+1
2019-06-08checktools: unify grepping the TOOLSTATE fileRalf Jung-3/+10
2019-05-23Revert edition-guide toolstate overrideEric Huss-3/+1
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-10/+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-9/+16
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-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/+8
2018-02-05Update clippy and miri submoduleOliver Schneider-1/+1
2017-12-30Requires tools to test-pass if the corresponding submodule is updated.kennytm-1/+23
If a PR intends to update a tool but its test has failed, abort the merge regardless of current channel. This should help the tool maintainers if the update turns out to be failing due to changes in latest master.
2017-12-27Clarify toolstate names. Move publish.py to a more convenient location.kennytm-1/+1
2017-12-27Upload the toolstate to the remote repository.kennytm-8/+15
2017-12-03Update the tools CI to use --no-fail-fast and --save-toolstates.kennytm-0/+39
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-15 12:13:28 +0000