| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-04-30 | Turn of rustc-dev-guide toolstate for now | mark | -1/+0 | |
| 2020-04-10 | Enforce Python 3 as much as possible | Guillaume Gomez | -2/+2 | |
| 2020-03-24 | Move rustc-guide submodule to rustc-dev-guide | Santiago Pastorino | -1/+1 | |
| 2019-12-10 | Move CI to new builtin check-toolstate | Mark Rousskov | -115/+1 | |
| 2019-10-30 | ci: move toolstates.json to /tmp/toolstate/ and docker mount it | Pietro 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-28 | Rollup merge of #62759 - mark-i-m:rustc-guide-toolstate-check, r=kennytm | Mazdak Farrokhzad | -4/+15 | |
| Actually add rustc-guide to toolstate, don't fail builds for the guide cc @ehuss r? @kennytm | ||||
| 2019-07-25 | ci: gate toolstate repo pushes on the TOOLSTATE_PUBLISH envvar | Pietro 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-23 | add back check for update prs | Mark Mansi | -0/+1 | |
| 2019-07-23 | more comments | Ralf Jung | -0/+1 | |
| 2019-07-23 | more comments for toolstate scripts | Ralf Jung | -2/+7 | |
| 2019-07-18 | Update src/ci/docker/x86_64-gnu-tools/checktools.sh | Who? Me?! | -1/+1 | |
| Co-Authored-By: Ralf Jung <post@ralfj.de> | ||||
| 2019-07-18 | add a few comments for the toolstate stuff | Ralf Jung | -4/+8 | |
| 2019-07-17 | don't fail builds for rustc-guide | Mark Mansi | -1/+0 | |
| 2019-07-17 | actually test rustc-guide with toolstate | Mark Mansi | -0/+1 | |
| 2019-07-06 | Track rustc-guide on toolstate | André Luis Leal Cardoso Junior | -0/+1 | |
| 2019-06-08 | checktools: unify grepping the TOOLSTATE file | Ralf Jung | -3/+10 | |
| 2019-05-23 | Revert edition-guide toolstate override | Eric Huss | -3/+1 | |
| 2019-05-15 | Update books | Eric Huss | -1/+3 | |
| 2019-03-27 | Update books | Eric Huss | -0/+2 | |
| 2019-03-09 | Track embedded-book in the toolstate | kennytm | -0/+1 | |
| 2019-02-04 | Add embedded book | James Munns | -0/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-08-01 | Align 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-29 | Test clippy first to workaround the derive-new conflict. | kennytm | -1/+2 | |
| 2018-07-17 | Block beta if clippy breaks. | kennytm | -7/+9 | |
| Don't fail master pull request when an unrelated tool is not test-pass. | ||||
| 2018-07-03 | Fix 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-15 | Fix checkregression breakage of toolstate builder on AppVeyor. | kennytm | -1/+1 | |
| 2018-06-10 | Do 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-09 | Document the checktools script | Oliver Schneider | -0/+7 | |
| 2018-05-09 | Don't require clippy/miri for beta | Oliver Schneider | -11/+26 | |
| 2018-04-23 | Fix the miri tool | Oliver Schneider | -1/+1 | |
| 2018-02-24 | Run the external doc tests in tools job. | kennytm | -12/+27 | |
| 2018-02-23 | Disallow toolstate regression at the last week of the 6-week cycle. | kennytm | -0/+8 | |
| 2018-02-05 | Update clippy and miri submodule | Oliver Schneider | -1/+1 | |
| 2017-12-30 | Requires 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-27 | Clarify toolstate names. Move publish.py to a more convenient location. | kennytm | -1/+1 | |
| 2017-12-27 | Upload the toolstate to the remote repository. | kennytm | -8/+15 | |
| 2017-12-03 | Update the tools CI to use --no-fail-fast and --save-toolstates. | kennytm | -0/+39 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| summary refs log tree commit diff |