GH-50242: [CI][Release] Fix flaky libLLVM load failure in macOS verify-rc build#50243
GH-50242: [CI][Release] Fix flaky libLLVM load failure in macOS verify-rc build#50243tadeja wants to merge 6 commits into
Conversation
|
|
|
@github-actions crossbow submit verify-rc-source-integration-macos-conda-amd64 |
|
Revision: 08323e7 Submitted crossbow builds: ursacomputing/crossbow @ actions-b28c2cbbb2
|
|
@github-actions crossbow submit verify-rc-source-cpp-macos-conda-amd64 |
|
Revision: 08323e7 Submitted crossbow builds: ursacomputing/crossbow @ actions-d35059f004
|
|
@github-actions crossbow submit -g verify-rc-source-macos |
|
Revision: 0bc831e Submitted crossbow builds: ursacomputing/crossbow @ actions-7b92c7f5ce |
|
@github-actions crossbow submit -g verify-rc-source-macos |
|
Revision: 6a8426d Submitted crossbow builds: ursacomputing/crossbow @ actions-aa38f94d3b |
|
@github-actions crossbow submit verify-rc-source-integration-macos-conda-amd64 verify-rc-source-cpp-macos-conda-amd64 verify-rc-source-python-macos-conda-amd64 |
|
Revision: 8f573bb Submitted crossbow builds: ursacomputing/crossbow @ actions-c854bae6e3
|
Rationale for this change
The nightly job Verify release candidate on macOS intermittently aborts the C++ build with
Library not loaded: @rpath/libLLVM.22.1.dylib).Conda's LLVM tools resolve
libLLVMvia@loader_path/../liband can point at the package cache which has nolibLLVM. The conda env lib dir is not on the loader path.Not caused by LLVM 22.1.8 (initial incorrect assessment). The same packages 22.1.8 pass in other runs.
What changes are included in this PR?
Add
$CONDA_PREFIX/libtoDYLD_FALLBACK_LIBRARY_PATHfor the stepcmake --build.(Fallback is searched last, so it resolves the
@rpathmiss without shadowing system libraries.)Also drop unneeded empty element from DYLD_LIBRARY_PATH/LD_LIBRARY_PATH assignment (trailing
:when the variable was unset).Are these changes tested?
Tested by nightly jobs verify-rc-source--macos-conda- : cpp, integration and python tasks pass.
Are there any user-facing changes?
No.