mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update the "Testing infrastructure" section 

The testing infrastructure was migrated from Travis and AppVeyor to
Azure Pipelines some time ago. This commit updates the documentation to
reflect this change.

Fixes #500.
This commit is contained in:
PotHix 2019-11-07 22:26:47 -03:00 committed by Who? Me?!
parent 0f2d015241
commit ac9c6dc99d
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
src/tests/intro.md
View File

@ -103,27 +103,27 @@ including:
## Testing infrastructure ## Testing infrastructure
When a Pull Request is opened on Github, [Travis] will automatically launch a When a Pull Request is opened on Github, [Azure Pipelines] will automatically
build that will run all tests on a single configuration (x86-64 linux). In launch a build that will run all tests on some configurations
essence, it runs `./x.py test` after building. (x86_64-gnu-llvm-6.0 linux. x86_64-gnu-tools linux, mingw-check linux). In
essence, it runs `./x.py test` after building for each of them.
The integration bot [bors] is used for coordinating merges to the master The integration bot [bors] is used for coordinating merges to the master
branch. When a PR is approved, it goes into a [queue] where merges are tested branch. When a PR is approved, it goes into a [queue] where merges are tested
one at a time on a wide set of platforms using Travis and [Appveyor] one at a time on a wide set of platforms using Azure Pipelines (currently over
(currently over 50 different configurations). Most platforms only run the 50 different configurations). Most platforms only run the build steps, some run
build steps, some run a restricted set of tests, only a subset run the full a restricted set of tests, only a subset run the full suite of tests (see
suite of tests (see Rust's [platform tiers]). Rust's [platform tiers]).
[Travis]: https://travis-ci.org/rust-lang/rust [Azure Pipelines]: https://dev.azure.com/rust-lang/rust/
[bors]: https://github.com/servo/homu [bors]: https://github.com/servo/homu
[queue]: https://buildbot2.rust-lang.org/homu/queue/rust [queue]: https://buildbot2.rust-lang.org/homu/queue/rust
[Appveyor]: https://ci.appveyor.com/project/rust-lang/rust
[platform tiers]: https://forge.rust-lang.org/platform-support.html [platform tiers]: https://forge.rust-lang.org/platform-support.html
## Testing with Docker images ## Testing with Docker images
The Rust tree includes [Docker] image definitions for the platforms used on The Rust tree includes [Docker] image definitions for the platforms used on
Travis in [src/ci/docker]. The script [src/ci/docker/run.sh] is used to build Azure Pipelines in [src/ci/docker]. The script [src/ci/docker/run.sh] is used to build
the Docker image, run it, build Rust within the image, and run the tests. the Docker image, run it, build Rust within the image, and run the tests.
> TODO: What is a typical workflow for testing/debugging on a platform that > TODO: What is a typical workflow for testing/debugging on a platform that