Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-43502: [Java] Fix Java JNI / AMD64 manylinux2014 Java JNI test not test dataset module #43503

Merged
merged 3 commits into from
Aug 9, 2024

Conversation

vibhatha
Copy link
Collaborator

@vibhatha vibhatha commented Aug 1, 2024

Rationale for this change

JNI tests had a typo in the script where we have included gandiva instead of dataset.

What changes are included in this PR?

This PR fixes that typo in the current version.

Are these changes tested?

Yes, by existing tests and CIs.

Are there any user-facing changes?

No

@vibhatha vibhatha marked this pull request as ready for review August 1, 2024 01:23
@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

@github-actions crossbow submit -g java

Copy link

github-actions bot commented Aug 1, 2024

⚠️ GitHub issue #43502 has been automatically assigned in GitHub to PR creator.

@github-actions github-actions bot added the awaiting review Awaiting review label Aug 1, 2024
@kou kou changed the title GH-43502: [JAVA] Fix Java JNI / AMD64 manylinux2014 Java JNI test not test dataset module GH-43502: [Java] Fix Java JNI / AMD64 manylinux2014 Java JNI test not test dataset module Aug 1, 2024
Copy link

github-actions bot commented Aug 1, 2024

Revision: a394350

Submitted crossbow builds: ursacomputing/crossbow @ actions-a30ce59033

Task Status
java-jars GitHub Actions
test-conda-python-3.11-spark-master GitHub Actions
verify-rc-source-java-linux-almalinux-8-amd64 GitHub Actions
verify-rc-source-java-linux-conda-latest-amd64 GitHub Actions
verify-rc-source-java-linux-ubuntu-20.04-amd64 GitHub Actions
verify-rc-source-java-linux-ubuntu-22.04-amd64 GitHub Actions
verify-rc-source-java-macos-amd64 GitHub Actions

@jinchengchenghh
Copy link
Contributor

jinchengchenghh commented Aug 1, 2024

And it still has a problem , https://github.com/apache/arrow/blob/main/ci/docker/java-jni-manylinux-201x.dockerfile#L53, ARROW_JAVA_JNI set, so jni build exists, but jni test detect ARROW_DATASET

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

And it still has a problem , https://github.com/apache/arrow/blob/main/ci/docker/java-jni-manylinux-201x.dockerfile#L53, ARROW_JAVA_JNI set, so jni build exists, but jni test detect ARROW_DATASET

I didn't get it clearly, could you please elaborate a bit?

@jinchengchenghh
Copy link
Contributor

It check the ARROW_DATASET, but it is OFF now, so as ARROW_GANDIVA https://github.com/apache/arrow/blob/main/ci/scripts/java_test.sh#L41

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

It check the ARROW_DATASET, but it is OFF now, so as ARROW_GANDIVA https://github.com/apache/arrow/blob/main/ci/scripts/java_test.sh#L41

Let me check, though if this is true, we have had the CIs running without any of these checks 🤔

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

@jinchengchenghh on top of that there is already a CI failure for dataset.

@jinchengchenghh
Copy link
Contributor

It check the ARROW_DATASET, but it is OFF now, so as ARROW_GANDIVA https://github.com/apache/arrow/blob/main/ci/scripts/java_test.sh#L41

Let me check, though if this is true, we have had the CIs running without any of these checks 🤔

I think you are right, not sure where to set the environment, but the test really triggers.

I will try to fix the exception, my IDE sync cause some problems

@jinchengchenghh
Copy link
Contributor

Can you mark it as ignore? I will draft a new PR to solve it.

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

It check the ARROW_DATASET, but it is OFF now, so as ARROW_GANDIVA https://github.com/apache/arrow/blob/main/ci/scripts/java_test.sh#L41

Let me check, though if this is true, we have had the CIs running without any of these checks 🤔

I think you are right, not sure where to set the environment, but the test really triggers.

I will take a look at that.

I will try to fix the exception, my IDE sync cause some problems

Thanks, that would be wonderful, but I am not sure if this is related to the recent PRs (didn't check yet).

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

Can you mark it as ignore? I will draft a new PR to solve it.

would you like to push the patch to this branch?

@jinchengchenghh
Copy link
Contributor

#43506

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

Btw, does that failing test in the CI work locally?

@jinchengchenghh
Copy link
Contributor

Do you know how to push to this branch? I don't think I have write access to vibhatha:gh-43502

@jinchengchenghh
Copy link
Contributor

#41646 skip tests java-jars, maybe we still need environment ARROW_DATASET to trigger it in Java JNI / AMD64 manylinux2014 Java JNI test

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

Do you know how to push to this branch? I don't think I have write access to vibhatha:gh-43502

I will add the rights.

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

@jinchengchenghh I have added you and you should have commit rights, please check.

@jinchengchenghh
Copy link
Contributor

ok thanks! I will draft a PR as soon as possible

@jinchengchenghh
Copy link
Contributor

I investigate the question again, the exception should not occur, looks like the linked library is not right.

TestFragmentScanOptions.testCsvConvertOptions:80 expected: <[Id: Int(32, true), Name: Utf8, Language: Utf8]> but was: <[Id;Name;Language: Utf8]>

Can anyone help to check it?

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

I investigate the question again, the exception should not occur, looks like the linked library is not right.

TestFragmentScanOptions.testCsvConvertOptions:80 expected: <[Id: Int(32, true), Name: Utf8, Language: Utf8]> but was: <[Id;Name;Language: Utf8]>

Can anyone help to check it?

let me check this locally.

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

@github-actions crossbow submit java-jars

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 6, 2024

@github-actions crossbow submit -g java

Copy link

github-actions bot commented Aug 6, 2024

Revision: cb36191

Submitted crossbow builds: ursacomputing/crossbow @ actions-92c9a56dee

Task Status
java-jars GitHub Actions
test-conda-python-3.11-spark-master GitHub Actions
verify-rc-source-java-linux-almalinux-8-amd64 GitHub Actions
verify-rc-source-java-linux-conda-latest-amd64 GitHub Actions
verify-rc-source-java-linux-ubuntu-20.04-amd64 GitHub Actions
verify-rc-source-java-linux-ubuntu-22.04-amd64 GitHub Actions
verify-rc-source-java-macos-amd64 GitHub Actions

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting change review Awaiting change review labels Aug 6, 2024
@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 6, 2024

@kou I updated as you suggested, also created an issue to track and update once the LLVM issue is resolved.

@danepitkin
Copy link
Member

@github-actions crossbow submit java-jars

Copy link

github-actions bot commented Aug 6, 2024

Revision: cb36191

Submitted crossbow builds: ursacomputing/crossbow @ actions-67f1c3bfef

Task Status
java-jars GitHub Actions

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 7, 2024

@danepitkin shall we re-run the java-jars? I am not sure what that failure is.

@kou
Copy link
Member

kou commented Aug 7, 2024

Hmm. self-hosted arm64 Linux runner may have a problem:

- runs_on: ["self-hosted", "Linux", "arm64"]

Disk size?

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 7, 2024

@kou honestly not sure...

@danepitkin
Copy link
Member

I think the previous java-jars successful run proves its fine. However the Java JNI CI job is failing. Did we want to fix the TestCsvFragment options in this PR?

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 8, 2024

I think the previous java-jars successful run proves its fine. However the Java JNI CI job is failing. Did we want to fix the TestCsvFragment options in this PR?

Wasn't the objective in this PR though.

@danepitkin
Copy link
Member

@github-actions crossbow submit java-jars

Copy link

github-actions bot commented Aug 9, 2024

Revision: cb36191

Submitted crossbow builds: ursacomputing/crossbow @ actions-f25c638877

Task Status
java-jars GitHub Actions

Copy link
Member

@danepitkin danepitkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gandiva builds, java-jars now failing on #43506

@danepitkin danepitkin merged commit cdfdfb8 into apache:main Aug 9, 2024
20 of 22 checks passed
@danepitkin danepitkin removed the awaiting merge Awaiting merge label Aug 9, 2024
@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 9, 2024

Thanks @danepitkin

Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit cdfdfb8.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants