I think I'm +1 on this, in that I don't see any more test failures than I usually do, and I think they're due to my local env, but is anyone seeing these failures? - includes jars passed in through --jars *** FAILED *** Process returned with exit code 1. See the log4j logs for more detail. (SparkSubmitSuite.scala:1517) - includes jars passed in through --packages *** FAILED *** Process returned with exit code 1. See the log4j logs for more detail. (SparkSubmitSuite.scala:1517) - includes jars passed through spark.jars.packages and spark.jars.repositories *** FAILED *** Process returned with exit code 1. See the log4j logs for more detail. (SparkSubmitSuite.scala:1517) - correctly builds R packages included in a jar with --packages !!! IGNORED !!! - include an external JAR in SparkR *** FAILED *** Process returned with exit code 1. See the log4j logs for more detail. (SparkSubmitSuite.scala:1517)
- SPARK-8368: includes jars passed in through --jars *** FAILED *** spark-submit returned with exit code 1. Command line: './bin/spark-submit' '--class' 'org.apache.spark.sql.hive.SparkSubmitClassLoaderTest' '--name' 'SparkSubmitClassLoaderTest' '--master' 'local-cluster[2,1,1024]' '--conf' 'spark.ui.enabled=false' '--conf' 'spark.master.rest.enabled=false' '--driver-java-options' '-Dderby.system.durability=test' '--jars' 'file:/mnt/data/testing/spark-3.0.2/sql/hive/target/tmp/spark-d5238bae-f0c8-4e26-8e0d-e7fc3a830de4/testJar-1613607380770.jar,file:/mnt/data/testing/spark-3.0.2/sql/hive/target/tmp/spark-5007fa06-28c3-4816-afe0-09f5885a201c/testJar-1613607380989.jar,/mnt/data/testing/spark-3.0.2/sql/hive/target/tmp/spark-59b75d08-8ea5-4fe9-a97b-84866093ad3a/hive-contrib-2.3.7.jar,/mnt/data/testing/spark-3.0.2/sql/hive/target/tmp/spark-59b75d08-8ea5-4fe9-a97b-84866093ad3a/hive-hcatalog-core-2.3.7.jar' 'file:/mnt/data/testing/spark-3.0.2/sql/hive/target/tmp/spark-27131c51-8387-455a-a23d-e5c41e5448a3/testJar-1613607380546.jar' 'SparkSubmitClassA' 'SparkSubmitClassB' external shuffle service *** FAILED *** FAILED did not equal FINISHED (stdout/stderr was not captured) (BaseYarnClusterSuite.scala:199) On Tue, Feb 16, 2021 at 1:52 AM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > Please vote on releasing the following candidate as Apache Spark version > 3.0.2. > > The vote is open until February 19th 9AM (PST) and passes if a majority +1 > PMC votes are cast, with a minimum of 3 +1 votes. > > [ ] +1 Release this package as Apache Spark 3.0.2 > [ ] -1 Do not release this package because ... > > To learn more about Apache Spark, please see https://spark.apache.org/ > > The tag to be voted on is v3.0.2-rc1 (commit > 648457905c4ea7d00e3d88048c63f360045f0714): > https://github.com/apache/spark/tree/v3.0.2-rc1 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/spark/v3.0.2-rc1-bin/ > > Signatures used for Spark RCs can be found in this file: > https://dist.apache.org/repos/dist/dev/spark/KEYS > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachespark-1366/ > > The documentation corresponding to this release can be found at: > https://dist.apache.org/repos/dist/dev/spark/v3.0.2-rc1-docs/ > > The list of bug fixes going into 3.0.2 can be found at the following URL: > https://issues.apache.org/jira/projects/SPARK/versions/12348739 > > FAQ > > ========================= > How can I help test this release? > ========================= > > If you are a Spark user, you can help us test this release by taking > an existing Spark workload and running on this release candidate, then > reporting any regressions. > > If you're working in PySpark you can set up a virtual env and install > the current RC and see if anything important breaks, in the Java/Scala > you can add the staging repository to your projects resolvers and test > with the RC (make sure to clean up the artifact cache before/after so > you don't end up building with a out of date RC going forward). > > =========================================== > What should happen to JIRA tickets still targeting 3.0.2? > =========================================== > > The current list of open tickets targeted at 3.0.2 can be found at: > https://issues.apache.org/jira/projects/SPARK and search for "Target > Version/s" = 3.0.2 > > Committers should look at those and triage. Extremely important bug > fixes, documentation, and API tweaks that impact compatibility should > be worked on immediately. Everything else please retarget to an > appropriate release. > > ================== > But my bug isn't fixed? > ================== > > In order to make timely releases, we will typically not hold the > release unless the bug in question is a regression from the previous > release. That being said, if there is something which is a regression > that has not been correctly targeted please ping me or a committer to > help target the issue. >
