Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upDon't even try to build branches other than auto and try #43797
Conversation
rust-highfive
assigned
alexcrichton
Aug 10, 2017
aidanhs
force-pushed the
aidanhs:aphs-only-auto-and-try
branch
3 times, most recently
from
919e9c7
to
551296d
Aug 10, 2017
aidanhs
force-pushed the
aidanhs:aphs-only-auto-and-try
branch
from
551296d
to
5426ced
Aug 10, 2017
This comment has been minimized.
This comment has been minimized.
|
Nope, doesn't work. And I feel like I've tried this before and gone away disappointed... |
aidanhs
closed this
Aug 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
aidanhs commentedAug 10, 2017
Although we have an environment variable which quickly exits the builders, I'm pretty sure that even putting master into the queue after every merge (https://travis-ci.org/rust-lang/rust/builds) causes a bit of a delay because the VMs have to be spun up.
Not sure if limiting to try and auto will exclude PRs, let's find out.
r? @alexcrichton