Skip to content
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

[SPARK-33662][BUILD] Setting version to 3.2.0-SNAPSHOT #30606

Closed
wants to merge 1 commit into from
Closed

[SPARK-33662][BUILD] Setting version to 3.2.0-SNAPSHOT #30606

wants to merge 1 commit into from

Conversation

dongjoon-hyun
Copy link
Member

@dongjoon-hyun dongjoon-hyun commented Dec 4, 2020

What changes were proposed in this pull request?

This PR aims to update master branch version to 3.2.0-SNAPSHOT.

Why are the changes needed?

Start to prepare Apache Spark 3.2.0.

Does this PR introduce any user-facing change?

N/A.

How was this patch tested?

Pass the CIs.

@dongjoon-hyun
Copy link
Member Author

Thank you, @srowen !

@dongjoon-hyun
Copy link
Member Author

Thank you, @tgravescs !

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36837/

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36837/

@dongjoon-hyun
Copy link
Member Author

Thank you, @gengliangwang !

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Test build #132237 has finished for PR 30606 at commit 4786329.

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

@dongjoon-hyun
Copy link
Member Author

Retest this please

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36845/

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36845/

@dongjoon-hyun
Copy link
Member Author

dongjoon-hyun commented Dec 4, 2020

For one Jenkins UT failure, it's a known flakiness issue, SPARK-33273 .

org.apache.spark.sql.SQLQueryTestSuite.subquery/scalar-subquery/scalar-subquery-predicate.sql

For one Jenkins K8s IT failure, it's also a known flaky one. (cc @ScrapCodes )

- Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties *** FAILED ***

GitHub Action jobs are still on the queue for two hours.

@dongjoon-hyun
Copy link
Member Author

Scala 2.13 seems to be broken by #30575 .

@SparkQA
Copy link

SparkQA commented Dec 4, 2020

Test build #132244 has finished for PR 30606 at commit 4786329.

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

@dongjoon-hyun
Copy link
Member Author

Jenkins passed. Merged to master.

@dongjoon-hyun dongjoon-hyun deleted the SPARK-3.2 branch December 4, 2020 22:11
@dongjoon-hyun
Copy link
Member Author

Thank you all!

@HyukjinKwon
Copy link
Member

Oh thanks Dongjoon :-).

@ScrapCodes
Copy link
Member

For one Jenkins UT failure, it's a known flakiness issue, SPARK-33273 .

org.apache.spark.sql.SQLQueryTestSuite.subquery/scalar-subquery/scalar-subquery-predicate.sql

For one Jenkins K8s IT failure, it's also a known flaky one. (cc @ScrapCodes )

- Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties *** FAILED ***

GitHub Action jobs are still on the queue for two hours.

Thanks @dongjoon-hyun, can you help me spot one more flaked instance of this test. So that I am sure, of the cause. (In my local testing, it never failed so far.)

@dongjoon-hyun
Copy link
Member Author

dongjoon-hyun commented Dec 5, 2020

@ScrapCodes
Copy link
Member

Thanks @dongjoon-hyun, I have opened a pr #30616 to address this.

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

Successfully merging this pull request may close these issues.

7 participants