about summary refs log tree commit diff
path: root/src/ci/docker/x86_64-gnu-tools/checktools.sh
AgeCommit message (Collapse)AuthorLines
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