Uh oh!
There was an error while loading. Please reload this page.
GH-55: [Gandiva] Re-enable tests - #595
Conversation
lriggs
commented
Feb 8, 2025
How do you specify the arrow version used to build/test with arrow-java (so that I know it has my fix)? Does it always use the latest? |
kou
commented
Feb 8, 2025
We use the latest release for push/pull request: arrow-java/.github/workflows/rc.yml Lines 110 to 113 in a5b8604 We use the main branch for schedule: arrow-java/.github/workflows/rc.yml Lines 114 to 119 in a5b8604 We need to update Line 57 in a5b8604 |
lriggs
commented
Feb 12, 2025
Thanks. I updated vcpkg as well now. |
lidavidm
commented
Feb 12, 2025
Looks like one more minor CI nit: |
lidavidm
commented
Feb 12, 2025
There's others - are you able to run the build locally at all to test? |
lriggs
commented
Feb 13, 2025
Now its failing with "Gandiva Failed to make LLVM module due to Could not create LLJIT instance: Symbols not found: [ llvm_orc_registerEHFrameSectionWrapper ]" which is what should be fixed in my other change in apache/arrow. Seems to be using the 18.2 jars: /home/runner/.m2/repository/org/apache/arrow/arrow-avro/18.2.0/ |
lidavidm
commented
Feb 13, 2025
Ah, the CI here uses the latest released version of the C++ libraries, not the development version... |
lidavidm
commented
Feb 13, 2025
We could either make the skips conditional on the version of the C++ code somehow, or otherwise just always test against the dev release? |
kou
commented
Feb 13, 2025
C++ version must not be related. |
lidavidm
commented
Feb 13, 2025
But we're building 19.0.0, not |
kou
commented
Feb 13, 2025
Ah, I thought that updating arrow-java/ci/docker/vcpkg-jni.dockerfile Line 26 in 34e2b08 The log shows that we use LLVM 17: https://github.com/apache/arrow-java/actions/runs/13298859368/job/37137015507?pr=595#step:10:1663 OK. Let's use main for now: diff --git a/.github/workflows/rc.yml b/.github/workflows/rc.yml
index faad5983..f2666a31 100644
--- a/.github/workflows/rc.yml+++ b/.github/workflows/rc.yml@@ -299,13 +299,13 @@ jobs:
shell: bash
run: |
tar -xf apache-arrow-java-*.tar.gz --strip-components=1
- - name: Download the latest Apache Arrow C++- if: github.event_name != 'schedule'- shell: bash- run: |- ci/scripts/download_cpp.sh+ # - name: Download the latest Apache Arrow C+++ # if: github.event_name != 'schedule'+ # shell: bash+ # run: |+ # ci/scripts/download_cpp.sh
- name: Checkout Apache Arrow C++
- if: github.event_name == 'schedule'+ # if: github.event_name == 'schedule'
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
repository: apache/arrow |
lidavidm
commented
Feb 13, 2025
Ah, I see what you meant by the original comment now... |
lriggs
commented
Feb 13, 2025
I'll try your suggested change @kou |
lriggs
commented
Feb 13, 2025
Latest failures were because I only updated the windows build in rc.yml. Just fixed that for mac and linux. |
kou
commented
Feb 14, 2025
Oh, sorry. It's my fault... |
Strange, it still seems to be using the old vcpkg. Does arrow-java need something like this? https://github.com/apache/arrow/blob/main/ci/scripts/install_vcpkg.sh .... |
kou
commented
Feb 16, 2025
Ah, we need to expire a cache when we change vcpkg version. Could you try this? diff --git a/compose.yaml b/compose.yaml
index 58a19676..b125c3c9 100644
--- a/compose.yaml+++ b/compose.yaml@@ -92,12 +92,12 @@ services:
# Usage:
# docker compose build vcpkg-jni
# docker compose run vcpkg-jni
- image: ${REPO}:${ARCH}-vcpkg-jni+ image: ${REPO}:${ARCH}-vcpkg-jni-${VCPKG}
build:
context: .
dockerfile: ci/docker/vcpkg-jni.dockerfile
cache_from:
- - ${REPO}:${ARCH}-vcpkg-jni+ - ${REPO}:${ARCH}-vcpkg-jni-${VCPKG}
args:
base: ${ARROW_REPO}:${ARCH}-python-${PYTHON}-wheel-manylinux-2014-vcpkg-${VCPKG}
volumes: |
lriggs
commented
Feb 18, 2025
Ok, just pushed a change to expire the cache. Hopefully it works. |
lidavidm
commented
Feb 19, 2025
Looks like that worked! |
FixesGH-55.
Rationale for this change
I fixed the linking error here: apache/arrow#45114
What changes are included in this PR?
Reenabling some disabled tests.
Are these changes tested?
Yes, they are tests.
Are there any user-facing changes?
No.