+1 The tests and all results were the same as ever for me (Java 11, Scala 2.13, Ubuntu 22.04) I also didn't see that issue ... maybe somehow locale related? which could still be a bug.
On Sat, Feb 11, 2023 at 8:49 PM L. C. Hsieh <vii...@gmail.com> wrote: > Thank you for testing it. > > I was going to run it again but still didn't see any errors. > > I also checked CI (and looked again now) on branch-3.3 before cutting RC. > > BTW, I didn't find an actual test failure (i.e. "- test_name *** > FAILED ***") in the log file. > > Maybe it is due to the dev env? What dev env you're using to run the test? > > > On Sat, Feb 11, 2023 at 8:58 AM Bjørn Jørgensen > <bjornjorgen...@gmail.com> wrote: > > > > > > ./build/mvn clean package > > > > Run completed in 1 hour, 18 minutes, 29 seconds. > > Total number of tests run: 11652 > > Suites: completed 516, aborted 0 > > Tests: succeeded 11609, failed 43, canceled 8, ignored 57, pending 0 > > *** 43 TESTS FAILED *** > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Reactor Summary for Spark Project Parent POM 3.3.2: > > [INFO] > > [INFO] Spark Project Parent POM ........................... SUCCESS [ > 3.418 s] > > [INFO] Spark Project Tags ................................. SUCCESS [ > 17.845 s] > > [INFO] Spark Project Sketch ............................... SUCCESS [ > 20.791 s] > > [INFO] Spark Project Local DB ............................. SUCCESS [ > 16.527 s] > > [INFO] Spark Project Networking ........................... SUCCESS > [01:03 min] > > [INFO] Spark Project Shuffle Streaming Service ............ SUCCESS [ > 9.914 s] > > [INFO] Spark Project Unsafe ............................... SUCCESS [ > 12.007 s] > > [INFO] Spark Project Launcher ............................. SUCCESS [ > 7.620 s] > > [INFO] Spark Project Core ................................. SUCCESS > [40:04 min] > > [INFO] Spark Project ML Local Library ..................... SUCCESS [ > 29.997 s] > > [INFO] Spark Project GraphX ............................... SUCCESS > [02:33 min] > > [INFO] Spark Project Streaming ............................ SUCCESS > [05:51 min] > > [INFO] Spark Project Catalyst ............................. SUCCESS > [13:29 min] > > [INFO] Spark Project SQL .................................. FAILURE [ > 01:25 h] > > [INFO] Spark Project ML Library ........................... SKIPPED > > [INFO] Spark Project Tools ................................ SKIPPED > > [INFO] Spark Project Hive ................................. SKIPPED > > [INFO] Spark Project REPL ................................. SKIPPED > > [INFO] Spark Project Assembly ............................. SKIPPED > > [INFO] Kafka 0.10+ Token Provider for Streaming ........... SKIPPED > > [INFO] Spark Integration for Kafka 0.10 ................... SKIPPED > > [INFO] Kafka 0.10+ Source for Structured Streaming ........ SKIPPED > > [INFO] Spark Project Examples ............................. SKIPPED > > [INFO] Spark Integration for Kafka 0.10 Assembly .......... SKIPPED > > [INFO] Spark Avro ......................................... SKIPPED > > [INFO] > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Total time: 02:30 h > > [INFO] Finished at: 2023-02-11T17:32:45+01:00 > > > > lør. 11. feb. 2023 kl. 06:01 skrev L. C. Hsieh <vii...@gmail.com>: > >> > >> Please vote on releasing the following candidate as Apache Spark > version 3.3.2. > >> > >> The vote is open until Feb 15th 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.3.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.3.2-rc1 (commit > >> 5103e00c4ce5fcc4264ca9c4df12295d42557af6): > >> https://github.com/apache/spark/tree/v3.3.2-rc1 > >> > >> The release files, including signatures, digests, etc. can be found at: > >> https://dist.apache.org/repos/dist/dev/spark/v3.3.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-1433/ > >> > >> The documentation corresponding to this release can be found at: > >> https://dist.apache.org/repos/dist/dev/spark/v3.3.2-rc1-docs/ > >> > >> The list of bug fixes going into 3.3.2 can be found at the following > URL: > >> https://issues.apache.org/jira/projects/SPARK/versions/12352299 > >> > >> This release is using the release script of the tag v3.3.2-rc1. > >> > >> 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.3.2? > >> =========================================== > >> > >> The current list of open tickets targeted at 3.3.2 can be found at: > >> https://issues.apache.org/jira/projects/SPARK and search for "Target > >> Version/s" = 3.3.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. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >> > > > > > > -- > > Bjørn Jørgensen > > Vestre Aspehaug 4, 6010 Ålesund > > Norge > > > > +47 480 94 297 > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
