Fix line endings in the Nuget packages descriptions #811
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
|
Thanks, but how can this change have possibly failed the build? It's only textual... |
|
The Travis build failing on master as well. No idea why. |
|
A quick look shows it fails on Linux and Mac. It seems to have trouble with locating
It seems NuGet can't find a path:
|
|
@abelbraaksma I replaced the slashed to the linux ones in #812, waiting for results... |
|
@abelbraaksma how did you manage to see the Travis build logs? |
@vasily-kirichenko, by clicking on Details:
And in the next window, clicking on whatever failing build row I thought interesting, this gave me a screen with colored log lines:
|
dsyme
approved these changes
Oct 3, 2017
|
16.0.2 released |
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.
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.
No description provided.