[Java][Gandiva] Crashed tests: Error occurred in starting fork
- 主要言語
- Java
- スター
- 94
- フォーク
- 152
- 平均マージ
- 3日 16時間
- マージ済み PR(30日)
- 11
説明
There are crashes at running test on Java Gandiva module:
1. Able to build JNI Gandiva without problems at $PWD/arrow/java-dist/lib
1. Run mvn command `mvn -Darrow.cpp.build.dir=$PWD/arrow/java-dist/lib -Parrow-jni clean install`
1. Process finished with message:
3.1.- maven surefire error message:
```java
[ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd '/Users/dsusanibar/arrow/java/gandiva' && '/Library/Java/JavaVirtualMachines/jdk1.8.0_231.jdk/Contents/Home/jre/bin/java' '-jar' '/Users/dsusanibar/arrow/java/gandiva/target/surefire/surefirebooter-20221005232352974_5.jar' '/Users/dsusanibar/arrow/java/gandiva/target/surefire' '2022-10-05T23-23-52_590-jvmRun2' 'surefire-20221005232352974_2tmp' 'surefire_1-20221005232352974_4tmp'
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 134
[ERROR] Crashed tests:
[ERROR] org.apache.arrow.gandiva.evaluator.FilterTest
```
3.2.- hs_err_pid.log message:
{code:java}
#
1. A fatal error has been detected by the Java Runtime Environment:
#
1. SIGBUS (0xa) at pc=0x00000001346ed6b9, pid=41012, tid=0x0000000000000f03
#
1. JRE version: Java(TM) SE Runtime Environment (8.0_231-b11) (build 1.8.0_231-b11)
1. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.231-b11 mixed mode bsd-amd64 compressed oops)
1. Problematic frame:
1. C [libgandiva_jni.dylib03efc768-f328-401f-9228-ab27532eff3e+0xb6b9] ProtoTypeToField(types::Field const&)+0x69
#
#
1. If you would like to submit a bug report, please visit:
1. http://bugreport.java.com/bugreport/crash.jsp
1. The crash happened outside the Java Virtual Machine in native code.
1. See problematic frame for where to report the bug.
1. {code}
**Reporter**: [David Dali Susanibar Arce](https://issues.apache.org/jira/browse/ARROW-17946) / @davisusanibar
**Note**: *This issue was originally created as [ARROW-17946](https://issues.apache.org/jira/browse/ARROW-17946). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
コントリビューションガイド
調査の方向性
まず、報告された arrow.cpp.build.dir を指定して java/gandiva で Maven コマンドを再現し、失敗している org.apache.arrow.gandiva.evaluator.FilterTest を調査します。Surefire の fork 出力と hs_err_pid.log を読み、特に libgandiva_jni.dylib の ProtoTypeToField frame を確認します。完了の条件は、Gandiva test suite が報告された SIGBUS でクラッシュしなくなることです。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- java
- 領域
- testing
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 35/100