Skip to content

Conversation

@HyukjinKwon
Copy link
Member

What changes were proposed in this pull request?

This PR is to trigger the tests against branch-2.4 to make sure #28005 makes the tests pass

Why are the changes needed?

N/A

Does this PR introduce any user-facing change?

N/A

How was this patch tested?

N/A

@SparkQA
Copy link

SparkQA commented Mar 25, 2020

Test build #120290 has finished for PR 28006 at commit a439977.

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

@SparkQA
Copy link

SparkQA commented Mar 25, 2020

Test build #120299 has finished for PR 28006 at commit e5879d2.

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

@dongjoon-hyun
Copy link
Member

Thank you for working on this.

@SparkQA
Copy link

SparkQA commented Mar 25, 2020

Test build #120301 has finished for PR 28006 at commit 384d1e3.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@dongjoon-hyun
Copy link
Member

Hi, @HyukjinKwon . This seems to be ready. Is this still [DO-NOT-MERGE]?

@HyukjinKwon
Copy link
Member Author

Oh, I was thinking about backporting when I merge #28005. Let me merge it appropriately. Thanks for checking!

@HyukjinKwon HyukjinKwon deleted the investigate-pip-packaging-followup-branch-2.4 branch July 27, 2020 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants