Not me. I am running zulu8, maven, and hadoop-2.7. On Sat, Feb 9, 2019 at 5:42 PM Felix Cheung <felixcheun...@hotmail.com> wrote:
> One test in SparkSubmitSuite is consistently failing for me. Anyone seeing > that? > > > ------------------------------ > *From:* Takeshi Yamamuro <linguin....@gmail.com> > *Sent:* Saturday, February 9, 2019 5:25 AM > *To:* Spark dev list > *Subject:* Re: [VOTE] Release Apache Spark 2.3.3 (RC2) > > Sorry, but I forgot to check ` -Pdocker-integration-tests` for the JDBC > integration tests. > I run these tests, and then I checked if they are passed. > > On Sat, Feb 9, 2019 at 5:26 PM Herman van Hovell <her...@databricks.com> > wrote: > >> I count 2 binding votes :)... >> >> Op vr 8 feb. 2019 om 22:36 schreef Felix Cheung < >> felixcheun...@hotmail.com> >> >>> Nope, still only 1 binding vote ;) >>> >>> >>> ------------------------------ >>> *From:* Mark Hamstra <m...@clearstorydata.com> >>> *Sent:* Friday, February 8, 2019 7:30 PM >>> *To:* Marcelo Vanzin >>> *Cc:* Takeshi Yamamuro; Spark dev list >>> *Subject:* Re: [VOTE] Release Apache Spark 2.3.3 (RC2) >>> >>> There are 2. C'mon Marcelo, you can make it 3! >>> >>> On Fri, Feb 8, 2019 at 5:03 PM Marcelo Vanzin >>> <van...@cloudera.com.invalid> wrote: >>> >>>> Hi Takeshi, >>>> >>>> Since we only really have one +1 binding vote, do you want to extend >>>> this vote a bit? >>>> >>>> I've been stuck on a few things but plan to test this (setting things >>>> up now), but it probably won't happen before the deadline. >>>> >>>> On Tue, Feb 5, 2019 at 5:07 PM Takeshi Yamamuro <linguin....@gmail.com> >>>> wrote: >>>> > >>>> > Please vote on releasing the following candidate as Apache Spark >>>> version 2.3.3. >>>> > >>>> > The vote is open until February 8 6:00PM (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 2.3.3 >>>> > [ ] -1 Do not release this package because ... >>>> > >>>> > To learn more about Apache Spark, please see http://spark.apache.org/ >>>> > >>>> > The tag to be voted on is v2.3.3-rc2 (commit >>>> 66fd9c34bf406a4b5f86605d06c9607752bd637a): >>>> > https://github.com/apache/spark/tree/v2.3.3-rc2 >>>> > >>>> > The release files, including signatures, digests, etc. can be found >>>> at: >>>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc2-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-1298/ >>>> > >>>> > The documentation corresponding to this release can be found at: >>>> > https://dist.apache.org/repos/dist/dev/spark/v2.3.3-rc2-docs/ >>>> > >>>> > The list of bug fixes going into 2.3.3 can be found at the following >>>> URL: >>>> > https://issues.apache.org/jira/projects/SPARK/versions/12343759 >>>> > >>>> > 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 2.3.3? >>>> > =========================================== >>>> > >>>> > The current list of open tickets targeted at 2.3.3 can be found at: >>>> > https://issues.apache.org/jira/projects/SPARK and search for "Target >>>> Version/s" = 2.3.3 >>>> > >>>> > 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. >>>> > >>>> > P.S. >>>> > I checked all the tests passed in the Amazon Linux 2 AMI; >>>> > $ java -version >>>> > openjdk version "1.8.0_191" >>>> > OpenJDK Runtime Environment (build 1.8.0_191-b12) >>>> > OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) >>>> > $ ./build/mvn -Pyarn -Phadoop-2.7 -Phive -Phive-thriftserver -Pmesos >>>> -Psparkr test >>>> > >>>> > -- >>>> > --- >>>> > Takeshi Yamamuro >>>> >>>> >>>> >>>> -- >>>> Marcelo >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>>> >>>> > > -- > --- > Takeshi Yamamuro > -- John Zhuge
