@@ -103,21 +103,21 @@ including:
103
103
104
104
## Testing infrastructure
105
105
106
- When a Pull Request is opened on Github, [ Travis] will automatically launch a
107
- build that will run all tests on a single configuration (x86-64 linux). In
108
- essence, it runs ` ./x.py test ` after building.
106
+ When a Pull Request is opened on Github, [ Azure Pipelines] will automatically
107
+ launch a build that will run all tests on some configurations
108
+ (x86_64-gnu-llvm-6.0 linux. x86_64-gnu-tools linux, mingw-check linux). In
109
+ essence, it runs ` ./x.py test ` after building for each of them.
109
110
110
111
The integration bot [ bors] is used for coordinating merges to the master
111
112
branch. When a PR is approved, it goes into a [ queue] where merges are tested
112
- one at a time on a wide set of platforms using Travis and [ Appveyor ]
113
- (currently over 50 different configurations). Most platforms only run the
114
- build steps, some run a restricted set of tests, only a subset run the full
115
- suite of tests (see Rust's [ platform tiers] ).
113
+ one at a time on a wide set of platforms using Azure Pipelines (currently over
114
+ 50 different configurations). Most platforms only run the build steps, some run
115
+ a restricted set of tests, only a subset run the full suite of tests (see
116
+ Rust's [ platform tiers] ).
116
117
117
- [ Travis ] : https://travis-ci.org /rust-lang/rust
118
+ [ Azure Pipelines ] : https://dev.azure.com /rust-lang/rust/
118
119
[ bors ] : https://github.com/servo/homu
119
120
[ queue ] : https://buildbot2.rust-lang.org/homu/queue/rust
120
- [ Appveyor ] : https://ci.appveyor.com/project/rust-lang/rust
121
121
[ platform tiers ] : https://forge.rust-lang.org/platform-support.html
122
122
123
123
## Testing with Docker images
0 commit comments