-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix rustbuild --color conflict when building on Travis outside of Docker #45304
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
kennytm
added
the
S-waiting-on-author
Status: This is awaiting some action (such as code changes or more information) from the author.
label
Oct 15, 2017
kennytm
force-pushed
the
travis-color-color-conflict
branch
3 times, most recently
from
October 15, 2017 13:28
2967b4a
to
46b3803
Compare
kennytm
changed the title
[WIP] Fix rustbuild --color conflict when building on Travis outside of Docker
Fix rustbuild --color conflict when building on Travis outside of Docker
Oct 15, 2017
kennytm
added
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
and removed
S-waiting-on-author
Status: This is awaiting some action (such as code changes or more information) from the author.
labels
Oct 19, 2017
☔ The latest upstream changes (presumably #44792) made this pull request unmergeable. Please resolve the merge conflicts. |
kennytm
force-pushed
the
travis-color-color-conflict
branch
from
October 20, 2017 20:55
46b3803
to
ebbcad9
Compare
@bors: r+ rollup |
📌 Commit ebbcad9 has been approved by |
kennytm
added
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
Oct 21, 2017
bors
added a commit
that referenced
this pull request
Oct 22, 2017
Fix rustbuild --color conflict when building on Travis outside of Docker When trying to build rust on Travis without using `stamp` or `docker`, both `RUSTC_COLOR=1` and `TRAVIS=true` will separately pass `--color always` to the command line. This causes the build to fail due to "*Option 'color' given more than once*". In this PR, the `RUSTC_COLOR=1` will not be passed in the CI environment.
☀️ Test successful - status-appveyor, status-travis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
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.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to build rust on Travis without using
stamp
ordocker
, bothRUSTC_COLOR=1
andTRAVIS=true
will separately pass--color always
to the command line. This causes the build to fail due to "Option 'color' given more than once".In this PR, the
RUSTC_COLOR=1
will not be passed in the CI environment.