Does this happen when running all UTs? I ran this suite several times alone using OpenJDK(zulu) 8u322-b06 on my Mac, but no similar error occurred
发件人: Sean Owen <sro...@gmail.com> 日期: 2022年7月12日 星期二 10:45 收件人: Dongjoon Hyun <dongjoon.h...@gmail.com> 抄送: dev <dev@spark.apache.org> 主题: Re: [VOTE] Release Spark 3.2.2 (RC1) Is anyone seeing this error? I'm on OpenJDK 8 on a Mac: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000000101ca8ace, pid=11962, tid=0x0000000000001603 # # JRE version: OpenJDK Runtime Environment (8.0_322) (build 1.8.0_322-bre_2022_02_28_15_01-b00) # Java VM: OpenJDK 64-Bit Server VM (25.322-b00 mixed mode bsd-amd64 compressed oops) # Problematic frame: # V [libjvm.dylib+0x549ace] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /private/tmp/spark-3.2.2/sql/core/hs_err_pid11962.log ColumnVectorSuite: - boolean - byte Compiled method (nm) 885897 75403 n 0 sun.misc.Unsafe::putShort (native) total in heap [0x0000000102fdaa10,0x0000000102fdad48] = 824 relocation [0x0000000102fdab38,0x0000000102fdab78] = 64 main code [0x0000000102fdab80,0x0000000102fdad48] = 456 Compiled method (nm) 885897 75403 n 0 sun.misc.Unsafe::putShort (native) total in heap [0x0000000102fdaa10,0x0000000102fdad48] = 824 relocation [0x0000000102fdab38,0x0000000102fdab78] = 64 main code [0x0000000102fdab80,0x0000000102fdad48] = 456 On Mon, Jul 11, 2022 at 4:58 PM Dongjoon Hyun <dongjoon.h...@gmail.com<mailto:dongjoon.h...@gmail.com>> wrote: Please vote on releasing the following candidate as Apache Spark version 3.2.2. The vote is open until July 15th 1AM (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.2.2 [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see https://spark.apache.org/<https://mailshield.baidu.com/check?q=iR6md5rYrz%2bpTPJlEXXlR6NN3aGjunZT0DADO3Pcgs0%3d> The tag to be voted on is v3.2.2-rc1 (commit 78a5825fe266c0884d2dd18cbca9625fa258d7f7): https://github.com/apache/spark/tree/v3.2.2-rc1<https://mailshield.baidu.com/check?q=OPpTJN30W6csasZsQLXYMz8wfTlJ5%2bnnfXlDjC2R5gWSaBjEUJ676hoO3EDYrtmu4bXg%2bA%3d%3d> The release files, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/spark/v3.2.2-rc1-bin/<https://mailshield.baidu.com/check?q=7THGMp87%2fmTNaemtH6JB%2bybJqCLb%2fveO2dtcLu9p2HPsnf1RVQGyT40xy%2bMHCQGAFnTgIkwFZNZWe3IPpkkp9w%3d%3d> Signatures used for Spark RCs can be found in this file: https://dist.apache.org/repos/dist/dev/spark/KEYS<https://mailshield.baidu.com/check?q=E6fHbSXEWw02TTJBpc3bfA9mi7ea0YiWcNHkm%2fDJxwlaWinGnMdaoO1PahHhgj00vKwcbElpuHA%3d> The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-1409/<https://mailshield.baidu.com/check?q=e%2bM47bS5NGsG58Ou4yPktxmBrNc30lZeeAJoW55%2bwS5h8wbAq%2b60jNYPaoljh7dFcTEPFkV4q3p7TXoIDnbkVqwGsDSEuCDOG5yoyQ%3d%3d> The documentation corresponding to this release can be found at: https://dist.apache.org/repos/dist/dev/spark/v3.2.2-rc1-docs/<https://mailshield.baidu.com/check?q=%2bkgNM0UeXb%2fnKpJNJc%2f4tUYbmUQYZvOZtJxpyTBJNHjRWl1TKNnBQVg1PKnxScg14fmW8rcziXt4unYy4dBdye405us%3d> The list of bug fixes going into 3.2.2 can be found at the following URL: https://issues.apache.org/jira/projects/SPARK/versions/12351232<https://mailshield.baidu.com/check?q=8a5luT7J9KShVCNhj3Yr7XaoCuFqEmzbRDNOxnYupRy6bJ1JrvgNJMhgjCNcpQ5%2bWAK85n5wB4YbKJTbiCYPhj7PixU%3d> This release is using the release script of the tag v3.2.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.2.2? =========================================== The current list of open tickets targeted at 3.2.2 can be found at: https://issues.apache.org/jira/projects/SPARK<https://mailshield.baidu.com/check?q=4UUpJqq41y71Gnuj0qTUYo6hTjqzT7oytN6x%2fvgC5XUtQUC8MfJ77tj7K70O%2f1QMmNoa1A%3d%3d> and search for "Target Version/s" = 3.2.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. Dongjoon