[CI][Python] Image build failure on test-conda-python-3.12 #38323
Comments
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Oct 18, 2023
gdb on conda-forge frequently conflicts with the newest Python version (example for Python 3.12: conda-forge/gdb-feedstock#66) We needn't install gdb from conda-forge, though, as the Python interpreter used for gdb is entirely independent from the Python interpreter under test.
pitrou
added a commit
that referenced
this issue
Oct 19, 2023
### Rationale for this change gdb on conda-forge frequently conflicts with the newest Python version (example for Python 3.12: conda-forge/gdb-feedstock#66) ### What changes are included in this PR? Use the system-provided gdb instead of trying to install it from conda-forge. This works because the Python interpreter used for gdb is entirely independent from the Python interpreter under test, and gdb itself can debug any binary, regardless of binutils version. However, there is a complication: if the system Python version and the conda-forge Python version are the same, then for some reason `pyarrow/tests/test_gdb.py` would fail with the system gdb. In that case we still install the conda-forge gdb. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: #38323 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
JerAguilon
pushed a commit
to JerAguilon/arrow
that referenced
this issue
Oct 23, 2023
…che#38324) ### Rationale for this change gdb on conda-forge frequently conflicts with the newest Python version (example for Python 3.12: conda-forge/gdb-feedstock#66) ### What changes are included in this PR? Use the system-provided gdb instead of trying to install it from conda-forge. This works because the Python interpreter used for gdb is entirely independent from the Python interpreter under test, and gdb itself can debug any binary, regardless of binutils version. However, there is a complication: if the system Python version and the conda-forge Python version are the same, then for some reason `pyarrow/tests/test_gdb.py` would fail with the system gdb. In that case we still install the conda-forge gdb. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38323 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this issue
Nov 13, 2023
…che#38324) ### Rationale for this change gdb on conda-forge frequently conflicts with the newest Python version (example for Python 3.12: conda-forge/gdb-feedstock#66) ### What changes are included in this PR? Use the system-provided gdb instead of trying to install it from conda-forge. This works because the Python interpreter used for gdb is entirely independent from the Python interpreter under test, and gdb itself can debug any binary, regardless of binutils version. However, there is a complication: if the system Python version and the conda-forge Python version are the same, then for some reason `pyarrow/tests/test_gdb.py` would fail with the system gdb. In that case we still install the conda-forge gdb. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38323 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
…che#38324) ### Rationale for this change gdb on conda-forge frequently conflicts with the newest Python version (example for Python 3.12: conda-forge/gdb-feedstock#66) ### What changes are included in this PR? Use the system-provided gdb instead of trying to install it from conda-forge. This works because the Python interpreter used for gdb is entirely independent from the Python interpreter under test, and gdb itself can debug any binary, regardless of binutils version. However, there is a complication: if the system Python version and the conda-forge Python version are the same, then for some reason `pyarrow/tests/test_gdb.py` would fail with the system gdb. In that case we still install the conda-forge gdb. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38323 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
See example build at https://github.com/ursacomputing/crossbow/actions/runs/6559223743/job/17814395943 : the Docker image fails building because of a conda-forge conflict between gdb and Python 3.12.
Component(s)
Continuous Integration, Python
The text was updated successfully, but these errors were encountered: