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

Error verifying wheels for ADBC Libraries 15 #2311

Open
paleolimbot opened this issue Nov 8, 2024 · 2 comments
Open

Error verifying wheels for ADBC Libraries 15 #2311

paleolimbot opened this issue Nov 8, 2024 · 2 comments
Labels
Type: bug Something isn't working

Comments

@paleolimbot
Copy link
Member

What happened?

When verifying the release candidate for 15, I get an error when loading pyarrow 18.0.0 during the wheel verification step.

I'm on Ubuntu 22.04 and I ran USE_CONDA=1 ./verify-release-candidate.sh 15 1 from arrow-adbc/dev/release.

+ echo '=== () Testing wheels ==='
=== () Testing wheels ===
+ test_packages
+ for component in ${COMPONENTS}
+ echo '=== Testing adbc_driver_bigquery ==='
=== Testing adbc_driver_bigquery ===
+ python -c '
import adbc_driver_bigquery
import adbc_driver_bigquery.dbapi
'
Traceback (most recent call last):
  File "/tmp/arrow-adbc-15.azMyr/miniforge/envs/conda-wheel-3.9-x86_64/lib/python3.9/site-packages/adbc_driver_manager/dbapi.py", line 42, in <module>
    import pyarrow
  File "/tmp/arrow-adbc-15.azMyr/miniforge/envs/conda-wheel-3.9-x86_64/lib/python3.9/site-packages/pyarrow/__init__.py", line 65, in <module>
    import pyarrow.lib as _lib
ImportError: /tmp/arrow-adbc-15.azMyr/miniforge/envs/conda-wheel-3.9-x86_64/lib/python3.9/site-packages/pyarrow/libarrow_python.so: undefined symbol: _ZN5arrow16Decimal32BuilderC1ERKSt10shared_ptrINS_8DataTypeEEPNS_10MemoryPoolEl

Stack Trace

No response

How can we reproduce the bug?

No response

Environment/Setup

No response

@paleolimbot paleolimbot added the Type: bug Something isn't working label Nov 8, 2024
@lidavidm
Copy link
Member

I think I saw a similar error in CI once that went away on a retry. Similar to here it was a missing symbol that was actually defined; I wonder if something about the Conda environment activation isn't deterministic...

@lidavidm
Copy link
Member

I wasn't able to replicate :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants