diff options
| author | bors <bors@rust-lang.org> | 2019-04-25 06:38:38 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-04-25 06:38:38 +0000 |
| commit | dbaa6f0a4739f6aacc40822e91d2c2197e0fb86b (patch) | |
| tree | 820df51f70ccaae96924a266dc9b3bc2cd1317d3 /src/test/incremental/thinlto | |
| parent | d84d3f8c6668396b1d2f28d5de55fb14484b493f (diff) | |
| parent | 8d7a5fe126983e82caaf20be47841329131f15fa (diff) | |
| download | rust-dbaa6f0a4739f6aacc40822e91d2c2197e0fb86b.tar.gz rust-dbaa6f0a4739f6aacc40822e91d2c2197e0fb86b.zip | |
Auto merge of #4028 - phansch:skip_appveyor_on_pr_pushes, r=phansch
Only run AppVeyor on r+, try and the master branch As it is right now, there is only one worker available in the `rust-lang-libs` AppVeyor project and there are other repos as well that we share this worker with. This has been a problem for us because we sometimes hit a bors timeout if there are too many builds queued up. To improve the situation, I think we could try to use AppVeyor a bit less often. The average PR is not going to break windows related things anyway, so it should be fine to run it on r+/try/master only. changelog: none
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions