Skip to content

Conversation

@dondrake
Copy link

This is the same fix applied on branch-1.2 now applied on branch-1.3.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Feb 11, 2015

ok to test

@rxin
Copy link
Contributor

rxin commented Feb 11, 2015

Is this PR needed? https://github.com/apache/spark/pull/4521/files

We can just merge #4521 into branch-1.3.

@SparkQA
Copy link

SparkQA commented Feb 11, 2015

Test build #27302 has started for PR 4538 at commit 6bbd769.

  • This patch merges cleanly.

@dondrake
Copy link
Author

It wasn't entirely clear to me if #4521 contained commits for both branches. If it does, then this is not needed.

@rxin
Copy link
Contributor

rxin commented Feb 11, 2015

Yea don't worry about this PR. Our merge script can just merge it into both master and branch-1.3. You can close this one now. Thanks!

@dondrake
Copy link
Author

Closing per @rxin suggestion.

@dondrake dondrake closed this Feb 11, 2015
@SparkQA
Copy link

SparkQA commented Feb 11, 2015

Test build #27302 has finished for PR 4538 at commit 6bbd769.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27302/
Test FAILed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants