Uh oh!
There was an error while loading. Please reload this page.
GH-43506: [Java] Fix TestFragmentScanOptions result not match - #43639
Conversation
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format? or In the case of PARQUET issues on JIRA the title also supports: See also: |
vibhatha
commented
Aug 12, 2024
Rename to -> #43506: [Java] Fix TestFragmentScanOptions result not match |
vibhatha
commented
Aug 12, 2024
@github-actions crossbow submit -g java |
Revision: ea541c6b8fdcb0f97f25d52dd07cb893fd2f15de Submitted crossbow builds: ursacomputing/crossbow @ actions-acd4c173ff |
vibhatha
commented
Aug 12, 2024
@jinchengchenghh I think still there is an inaccuracy in the test case. One CI is failing. |
vibhatha
commented
Aug 12, 2024
Still the CI is failing... |
vibhatha
commented
Aug 12, 2024
Still failing right... |
jinchengchenghh
commented
Aug 13, 2024
I will take a look today. |
jinchengchenghh
commented
Aug 13, 2024
Only gandiva failed now. @vibhatha |
vibhatha
commented
Aug 13, 2024
@jinchengchenghh it seems like there is a symbol not found issue again; https://github.com/apache/arrow/actions/runs/10363135011/job/28686234425?pr=43639#step:7:20512 |
jinchengchenghh
commented
Aug 13, 2024
Do I need to disable this test in this PR? Or you will create a new PR to disable it? |
vibhatha
commented
Aug 13, 2024
@kou shall we disable this like the last time but note this as an issue and comment in the code? |
kou
commented
Aug 13, 2024
Yes but why is this happen again? Was #43503 not enough? |
vibhatha
commented
Aug 13, 2024
The tests related to Gandiva passed when we merged that PR, but it failed due to the exact reason in this PR. We might have missed something as it seems. |
jinchengchenghh
commented
Aug 13, 2024
Yes, this test Does it not occur before? |
vibhatha
commented
Aug 13, 2024
We should check that trace. We may have missed it. |
vibhatha
commented
Aug 13, 2024
@jinchengchenghh let's disable this too. |
jinchengchenghh
commented
Aug 14, 2024
Yes, I think we could disable the gandiva test in a separate PR. Can we merge this one first? @vibhatha |
lidavidm
commented
Aug 14, 2024
@github-actions crossbow submit -g java |
Revision: 855a3af Submitted crossbow builds: ursacomputing/crossbow @ actions-7af4649f9c |
jinchengchenghh
commented
Aug 15, 2024
Can you help merge this one? @vibhatha Thanks! |
vibhatha
commented
Aug 16, 2024
@jinchengchenghh I don't have merge rights. @lidavidm will definitely merge this as it is already approved. LGTM as well. |
jinchengchenghh
commented
Aug 16, 2024
Ok. Thanks for your kindly review. @vibhatha |
vibhatha
commented
Aug 16, 2024
@jinchengchenghh did we file a new issue for the Gandiva failure? |
jinchengchenghh
commented
Aug 16, 2024
Maybe we can use the exists issue apache/arrow-java#63 |
vibhatha
commented
Aug 16, 2024
Sure let's do that. |
lidavidm
commented
Aug 18, 2024
@vibhatha do we need to ping any Gandiva maintainers to figure out the failures? |
vibhatha
commented
Aug 18, 2024
lidavidm
commented
Aug 18, 2024
ok, let me dig |
vibhatha
commented
Aug 18, 2024
Thanks @lidavidm, I am not well versed in this part of the project. |
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 5ef7e01. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…pache#43639) ### Rationale for this change JNI test was not tested in CI. So the test failed but passed the CI. The parseChar function should return char but return bool, a typo error. ### What changes are included in this PR? ### Are these changes tested? Yes ### Are there any user-facing changes? No * GitHub Issue: apache#43506 Authored-by: Chengcheng Jin <chengcheng.jin@intel.com> Signed-off-by: David Li <li.davidm96@gmail.com>
Rationale for this change
JNI test was not tested in CI. So the test failed but passed the CI.
The parseChar function should return char but return bool, a typo error.
What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
No