diff options
| author | Philipp Hansch <dev@phansch.net> | 2019-02-01 07:34:36 +0100 |
|---|---|---|
| committer | Philipp Hansch <dev@phansch.net> | 2019-02-01 07:34:36 +0100 |
| commit | 4e39e65ad8ecb6419f52a2928c159660af4f611f (patch) | |
| tree | 738675dcc5119a050d973ee6e3e60ba5669728f5 /tests/mir-opt/lower_array_len.array_len_raw.NormalizeArrayLen.diff | |
| parent | 84dca9af66da7e49eda8005509c8dffebefe96a0 (diff) | |
| download | rust-4e39e65ad8ecb6419f52a2928c159660af4f611f.tar.gz rust-4e39e65ad8ecb6419f52a2928c159660af4f611f.zip | |
Travis: Don't run integration tests on every PR commit
This does not save Clippy any time but it makes sure that the concurrent build limit is not reached as quickly for the `rust-lang` Travis account. I can't create a permalink to the discussion somehow, so here's an excerpt from the Infra channel: ``` [11:57 PM] pietroalbini: there is a clippy build (20 jobs) and a packed_simd one (42 builders) and a rustc one which isn't scheduling atm [11:58 PM] pietroalbini: I don't think there is a way to prioritize rustc builds in the queue on travis, right? [12:22 AM] alexcrichton: pietro: I don't think so no [12:22 AM] alexcrichton: If it's a problem we should cull builds on other projects [12:22 AM] alexcrichton: The rust repo is the #1 priority ``` Since the integration tests are rarely failing these days, I think it's fine to not run them on every commit. If needed, it's also still possible to do a `try` build with `@bors try`.
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_len_raw.NormalizeArrayLen.diff')
0 files changed, 0 insertions, 0 deletions