Hi, I saw a couple of test failures I have not observed before:
a) FsHistoryProviderSuite - "SPARK-33146: don't let one bad rolling log folder prevent loading other applications" b) MesosClusterSchedulerSuite - "accept/decline offers with driver constraints" I ended up 'ignore''ing them to make the build pass, but did anything change to cause them to fail/be flakey ? Rest of the validation and build went fine. Regards, Mridul On Tue, Oct 18, 2022 at 10:28 PM Cheng Pan <pan3...@gmail.com> wrote: > +1 (non-binding) > > - Passed Apache Kyuubi (Incubating) integration tests[1] > - Run some jobs on our internal K8s cluster > > [1] https://github.com/apache/incubator-kyuubi/pull/3507 > > Thanks, > Cheng Pan > > On Wed, Oct 19, 2022 at 9:13 AM Yikun Jiang <yikunk...@gmail.com> wrote: > > > > +1, also test passed with spark-docker workflow (downloading rc4 tgz, > extract, build image, run K8s IT) > > > > [1] https://github.com/Yikun/spark-docker/pull/9 > > > > Regards, > > Yikun > > > > On Wed, Oct 19, 2022 at 8:59 AM Wenchen Fan <cloud0...@gmail.com> wrote: > >> > >> +1 > >> > >> On Wed, Oct 19, 2022 at 4:59 AM Chao Sun <sunc...@apache.org> wrote: > >>> > >>> +1. Thanks Yuming! > >>> > >>> Chao > >>> > >>> On Tue, Oct 18, 2022 at 1:18 PM Thomas graves <tgra...@apache.org> > wrote: > >>> > > >>> > +1. Ran internal test suite. > >>> > > >>> > Tom > >>> > > >>> > On Sun, Oct 16, 2022 at 9:14 PM Yuming Wang <wgy...@gmail.com> > wrote: > >>> > > > >>> > > Please vote on releasing the following candidate as Apache Spark > version 3.3.1. > >>> > > > >>> > > The vote is open until 11:59pm Pacific time October 21th 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.3.1 > >>> > > [ ] -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.3.1-rc4 (commit > fbbcf9434ac070dd4ced4fb9efe32899c6db12a9): > >>> > > https://github.com/apache/spark/tree/v3.3.1-rc4 > >>> > > > >>> > > The release files, including signatures, digests, etc. can be > found at: > >>> > > https://dist.apache.org/repos/dist/dev/spark/v3.3.1-rc4-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-1430 > >>> > > > >>> > > The documentation corresponding to this release can be found at: > >>> > > https://dist.apache.org/repos/dist/dev/spark/v3.3.1-rc4-docs > >>> > > > >>> > > The list of bug fixes going into 3.3.1 can be found at the > following URL: > >>> > > https://s.apache.org/ttgz6 > >>> > > > >>> > > This release is using the release script of the tag v3.3.1-rc4. > >>> > > > >>> > > > >>> > > FAQ > >>> > > > >>> > > ================== > >>> > > What happened to v3.3.1-rc3? > >>> > > ================== > >>> > > A performance regression(SPARK-40703) was found after tagging > v3.3.1-rc3, which the Iceberg community hopes Spark 3.3.1 could fix. > >>> > > So we skipped the vote on v3.3.1-rc3. > >>> > > > >>> > > ========================= > >>> > > 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.3.1? > >>> > > =========================================== > >>> > > The current list of open tickets targeted at 3.3.1 can be found at: > >>> > > https://issues.apache.org/jira/projects/SPARK and search for > "Target Version/s" = 3.3.1 > >>> > > > >>> > > 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. > >>> > > > >>> > > > >>> > > >>> > --------------------------------------------------------------------- > >>> > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >>> > > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >>> > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
