You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Python 3.8 CI job on macOS here is failing like this:
___________ ERROR collecting tests/python_package_test/test_arrow.py ___________
ImportError while importing test module '/Users/runner/work/LightGBM/LightGBM/tests/python_package_test/test_arrow.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
../../../miniforge/envs/test-env/lib/python3.8/importlib/init.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/python_package_test/test_arrow.py:21: in
import pyarrow as pa # type: ignore
../../../miniforge/envs/test-env/lib/python3.8/site-packages/pyarrow/init.py:65: in
import pyarrow.lib as _lib
E ImportError: dlopen(/Users/runner/miniforge/envs/test-env/lib/python3.8/site-packages/pyarrow/lib.cpython-38-darwin.so, 0x0002): Symbol not found: _ZN4absl12lts_2024072212log_internal10LogMessagelsIiLi0EEERS2_RKT
E Referenced from: /Users/runner/miniforge/envs/test-env/lib/libprotobuf.28.2.0.dylib
E Expected in: /Users/runner/miniforge/envs/test-env/lib/libabsl_log_internal_message.2407.0.0.dylib
=========================== short test summary info ============================
ERROR tests/python_package_test/test_arrow.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
========================= 1 skipped, 1 error in 5.85s ==========================
Description
The Python 3.8 CI job on macOS here is failing like this:
(build link)
Reproducible example
Example build: https://github.com/microsoft/LightGBM/actions/runs/12585086008/job/35076093860?pr=6765
Environment info
LightGBM version or commit hash: f3bd64a
Additional Comments
I pulled the logs from a failed build (build link) and the last successful one, from a few days ago (build link).
There were just 3 changes in the conda environment:
Looks like maybe this PR was the root cause:
And that that led to these other discussions:
The text was updated successfully, but these errors were encountered: