I traced back relevant changes and got a sense of what happened. Yangjie figured out the issue via link <https://github.com/apache/spark/pull/43010#discussion_r1338737506>. It's a tricky issue according to the comments from Yangjie - the test is dependent on ordering of execution for test suites. He said it does not fail in sbt, hence CI build couldn't catch it. He fixed it via link <https://github.com/apache/spark/pull/43155>, but we missed that the offending commit was also ported back to 3.5 as well, hence the fix wasn't ported back to 3.5.
Surprisingly, I can't reproduce locally even with maven. In my attempt to reproduce, SparkConnectProtoSuite was executed at third, SparkConnectStreamingQueryCacheSuite, and ExecuteEventsManagerSuite, and then SparkConnectProtoSuite. Maybe very specific to the environment, not just maven? My env: MBP M1 pro chip, MacOS 14.3.1, Openjdk 17.0.9. I used build/mvn (Maven 3.8.8). I'm not 100% sure this is something we should fail the release as it's a test only and sounds very environment dependent, but I'll respect your call on vote. Btw, looks like Rui also made a relevant fix via link <https://github.com/apache/spark/pull/43594> (not to fix the failing test but to fix other issues), but this also wasn't ported back to 3.5. @Rui Wang <amaliu...@apache.org> Do you think this is a regression issue and warrants a new RC? On Fri, Feb 16, 2024 at 11:38 AM Sean Owen <sro...@gmail.com> wrote: > Is anyone seeing this Spark Connect test failure? then again, I have some > weird issue with this env that always fails 1 or 2 tests that nobody else > can replicate. > > - Test observe *** FAILED *** > == FAIL: Plans do not match === > !CollectMetrics my_metric, [min(id#0) AS min_val#0, max(id#0) AS > max_val#0, sum(id#0) AS sum(id)#0L], 0 CollectMetrics my_metric, > [min(id#0) AS min_val#0, max(id#0) AS max_val#0, sum(id#0) AS sum(id)#0L], > 44 > +- LocalRelation <empty>, [id#0, name#0] > +- LocalRelation <empty>, [id#0, name#0] > (PlanTest.scala:179) > > On Thu, Feb 15, 2024 at 1:34 PM Jungtaek Lim <kabhwan.opensou...@gmail.com> > wrote: > >> DISCLAIMER: RC for Apache Spark 3.5.1 starts with RC2 as I lately figured >> out doc generation issue after tagging RC1. >> >> Please vote on releasing the following candidate as Apache Spark version >> 3.5.1. >> >> The vote is open until February 18th 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.5.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.5.1-rc2 (commit >> fd86f85e181fc2dc0f50a096855acf83a6cc5d9c): >> https://github.com/apache/spark/tree/v3.5.1-rc2 >> >> The release files, including signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.5.1-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-1452/ >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.5.1-rc2-docs/ >> >> The list of bug fixes going into 3.5.1 can be found at the following URL: >> https://issues.apache.org/jira/projects/SPARK/versions/12353495 >> >> 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 via "pip install >> https://dist.apache.org/repos/dist/dev/spark/v3.5.1-rc2-bin/pyspark-3.5.1.tar.gz >> " >> 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.5.1? >> =========================================== >> >> The current list of open tickets targeted at 3.5.1 can be found at: >> https://issues.apache.org/jira/projects/SPARK and search for "Target >> Version/s" = 3.5.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. >> >
