PARQUET-1351: Travis builds fail for parquet-format #100
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
…nt in the travis VM, and are not needed for Parquet)
|
@nandorKollar, can you fix the summary and description? I don't think it is accurate any more. In the description, please include some description of what this is intended to fix and how. Thanks! |
nandorKollar
changed the title
|
@rdblue sure! Indeed, the description of the PR and Jira is not accurate any more, rewrote to make it more accurate. |
|
+1 Thanks @nandorKollar! |
|
Once merging this, unfortunately we have to retrigger builds for PRs which failed because of this reason. @rdblue do you happen to know how to do it? |
|
Committers can restart builds in Travis CI. |
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.
Use default (latest) distribution for Travis (as of now Trusty) to make tests pass. Looks like for Precise JDK 1.7 is the default Java version, where TLSv1 is the default, and it is not supported by Maven Central anymore. With Trusty, the build runs with JDK 1.8, and tests pass.