Describe the bug, including details regarding any error messages, version, and platform.
> [5/5] RUN /arrow/ci/scripts/install_gcs_testbench.sh default:
441.7 note: This error originates from a subprocess, and is likely not a problem with pip.
441.7 ERROR: Failed building wheel for grpcio
441.7 Running setup.py clean for grpcio
442.8 Building wheel for MarkupSafe (setup.py): started
443.6 Building wheel for MarkupSafe (setup.py): finished with status 'done'
443.6 Created wheel for MarkupSafe: filename=MarkupSafe-2.1.5-py3-none-any.whl size=9887 sha256=3e8d7ae11ba676a23e13b4efd471cc234b1d092881a171980eb2b72ecad2535f
443.6 Stored in directory: /root/.cache/pip/wheels/39/87/45/5b4e1bc0eeda469ebeb98b9fef379d4b16b43d4370b7823514
443.6 Successfully built googleapis-storage-testbench MarkupSafe
443.6 Failed to build grpcio
443.6 ERROR: Could not build wheels for grpcio, which is required to install pyproject.toml-based projects
------
conda-python.dockerfile:38
--------------------
36 | # but we changed the installed Python version above, so we need to reinstall it.
37 | COPY ci/scripts/install_gcs_testbench.sh /arrow/ci/scripts
38 | >>> RUN /arrow/ci/scripts/install_gcs_testbench.sh default
39 | 40 | ENV ARROW_ACERO=ON \
--------------------
ERROR: failed to solve: process "/bin/bash -c -l /arrow/ci/scripts/install_gcs_testbench.sh default" did not complete successfully: exit code: 1
Service 'conda-python' failed to build : Build failed
Error: `docker-compose --file /home/runner/work/arrow/arrow/docker-compose.yml build --build-arg BUILDKIT_INLINE_CACHE=1 conda-python` exited with a non-zero exit code 1, see the process log above.
Example failure: https://github.com/apache/arrow/actions/runs/7943013070/job/21686899595?pr=40080
This is on a branch but the failure is reproducible on main with
docker-compose build conda && docker-compose build conda-cpp && PYTHON=3.9 docker-compose build conda-python
(I'm sure there is an archery command that is equivalent to this but I don't know what it is)
This failure is during the docker build step, so if it is completed successfully once I believe CI will cache it and keep returning that result. Without a cache to rely on I can reproduce this locally from main (91bf1c9c170c1917ad47bb0dbb38aa5c9fbbbfb2).
To be precise the error actually comes from pip install grpcio==1.59.0 which is a dependency of GCS testbench https://github.com/googleapis/storage-testbench/blob/43a1a82c39f6349598ec2b77f19cc336eca4ae58/setup.py#L46C10-L46C24
Component(s)
Continuous Integration
Describe the bug, including details regarding any error messages, version, and platform.
Example failure: https://github.com/apache/arrow/actions/runs/7943013070/job/21686899595?pr=40080
This is on a branch but the failure is reproducible on
mainwith(I'm sure there is an
archerycommand that is equivalent to this but I don't know what it is)This failure is during the docker build step, so if it is completed successfully once I believe CI will cache it and keep returning that result. Without a cache to rely on I can reproduce this locally from
main(91bf1c9c170c1917ad47bb0dbb38aa5c9fbbbfb2).To be precise the error actually comes from
pip install grpcio==1.59.0which is a dependency of GCS testbench https://github.com/googleapis/storage-testbench/blob/43a1a82c39f6349598ec2b77f19cc336eca4ae58/setup.py#L46C10-L46C24Component(s)
Continuous Integration