vibhatha opened a new issue, #42197:
URL: https://github.com/apache/arrow/issues/42197

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   On a few crossbows [1][2[[3], CIs on macOS x86_64 have been failing due to a 
homebrew issue. 
   
   ```bash
    Error: No such keg: /usr/local/Cellar/llvm
   Error: No such keg: /usr/local/Cellar/llvm
   Installing aws-sdk-cpp
   Installing bash
   Installing boost
   Using brotli
   Installing bzip2
   Upgrading c-ares
   Using curl
   Installing ccache
   Using cmake
   Installing flatbuffers
   Using git
   Installing glog
   Installing googletest
   Installing grpc
   Installing llvm@14
   Using lz4
   Installing mimalloc
   Installing ninja
   Installing node
   Using openssl@3
   Using pkg-config
   Installing protobuf
   Upgrading python
   ==> Upgrading 1 outdated package:
   python 3.12.3 -> 3.12.4
   ==> Downloading https://ghcr.io/v2/homebrew/core/python/3.12/manifests/3.12.4
   ==> Fetching [email protected]
   ==> Downloading 
https://ghcr.io/v2/homebrew/core/python/3.12/blobs/sha256:93d81dfa181e6890b6a2baa4fbb4df71b6c061a2dc7823fe0ae12b2ec4b59cc1
   ==> Upgrading python
     3.12.3 -> 3.12.4 
   ==> Pouring [email protected]
   Error: The `brew link` step did not complete successfully
   Error: The `brew link` step did not complete successfully
   The formula built, but is not symlinked into /usr/local
   Could not symlink bin/2to3
   ```
   
   [1] 
https://github.com/ursacomputing/crossbow/actions/runs/9554716898/job/26336385763#step:5:78
   [2] 
https://github.com/ursacomputing/crossbow/actions/runs/9554720405/job/26336397852#step:5:78
   [3] 
https://github.com/ursacomputing/crossbow/actions/runs/9554711612/job/26336369061#step:5:78
   
   ### Component(s)
   
   Integration


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to