-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GH-35056: [Python][CI] Don't install gdb on Windows #35057
Conversation
Because it's not available on Windows.
|
Do we want to add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @westonpace but I think the solution is easier :)
ci/docker/conda-python.dockerfile
Outdated
ci/conda_env_sphinx.txt \ | ||
/arrow/ci/ | ||
RUN mamba install -q -y \ | ||
--file arrow/ci/conda_env_python.txt \ | ||
--file arrow/ci/conda_env_python_unix.txt \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just add gdb directly here as it is not used anywhere else? Should we add more packages/use them in multiple location we can always refactor into a new file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this approach is better. See also: #35024 (comment)
But it's not a strong opinion because I'm not a conda user. I follow opinions from developers who use conda.
But I don't have strong opinion for this. Should I use |
It's all not too important to bikeshed over, but I agree with Jacob and Weston that I find it not really worth it to create a new file for this (also as a user of those files for my local development, that makes the command to create your conda environment quite a bit longer). |
OK. I've moved |
@github-actions crossbow submit test-conda-python-3.10 |
Revision: d1fb68a Submitted crossbow builds: ursacomputing/crossbow @ actions-d86b248eae
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Appveyor is still failing, but now it's an issue in the tests (not in setting up the env). Seems to be hanging / taking too much time. |
Benchmark runs are scheduled for baseline = b8427d3 and contender = 6120345. 6120345 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
['Python', 'R'] benchmarks have high level of regressions. |
### Rationale for this change Similar to the issue with windows in #35057 gdb is also not available for arm64, causing benchmarks to fail. This moves gdb into the dockerfile that actually needs it to prevent further changes. An alternative would be to use multi-arch-gdb but that is only available in `-c memfault` and adding on an entire new channel will only increase solve times and potentially cause problems. * Closes: #35346 Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Because it's not available on Windows. ### Rationale for this change The gdb conda package isn't available on Windows: https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/46748401#L266 ```text C:\projects\arrow>mamba create -n arrow -y -c conda-forge --file=ci\conda_env_python.txt --file=ci\conda_env_gandiva_win.txt --file=ci\conda_env_cpp.txt "ccache" "cmake" "ninja" "nomkl" "pandas" "fsspec" "python=3.10" || exit /B conda-forge/win-64 Using cache conda-forge/noarch Using cache Looking for: ['boto3', 'cffi', 'cython', 'cloudpickle', 'fsspec', 'gdb', 'hypothesis', "numpy[version='>=1.16.6']", 'pytest', 'pytest-faulthandler', 'pytest-lazy-fixture', "s3fs[version='>=2021.8.0']", 'setuptools', 'setuptools_scm', "clangdev[version='<15']", "llvmdev[version='<15']", 'aws-sdk-cpp==1.10.13', "benchmark[version='>=1.6.0']", "boost-cpp[version='>=1.68.0']", 'brotli', 'bzip2', 'c-ares', 'cmake', 'flatbuffers', 'gflags', 'glog', "gmock[version='>=1.10.0']", "google-cloud-cpp[version='>=1.34.0']", 'grpc-cpp', "gtest[version='>=1.10.0']", 'libprotobuf', 'libutf8proc', 'lz4-c', 'make', 'ninja', 'orc', 'pkg-config', 'python', 'rapidjson', 're2', 'snappy', "thrift-cpp[version='>=0.11.0']", 'xsimd', 'zlib', 'zstd', 'ccache', 'cmake', 'ninja', 'nomkl', 'pandas', 'fsspec', 'python=3.10'] Could not solve for environment specs The following package could not be installed └─ gdb does not exist (perhaps a typo or a missing channel). C:\projects\arrow>set lastexitcode=1 ``` ### What changes are included in this PR? Don't install gdb on Windows. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#35056 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
…ache#35348) ### Rationale for this change Similar to the issue with windows in apache#35057 gdb is also not available for arm64, causing benchmarks to fail. This moves gdb into the dockerfile that actually needs it to prevent further changes. An alternative would be to use multi-arch-gdb but that is only available in `-c memfault` and adding on an entire new channel will only increase solve times and potentially cause problems. * Closes: apache#35346 Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Because it's not available on Windows. ### Rationale for this change The gdb conda package isn't available on Windows: https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/46748401#L266 ```text C:\projects\arrow>mamba create -n arrow -y -c conda-forge --file=ci\conda_env_python.txt --file=ci\conda_env_gandiva_win.txt --file=ci\conda_env_cpp.txt "ccache" "cmake" "ninja" "nomkl" "pandas" "fsspec" "python=3.10" || exit /B conda-forge/win-64 Using cache conda-forge/noarch Using cache Looking for: ['boto3', 'cffi', 'cython', 'cloudpickle', 'fsspec', 'gdb', 'hypothesis', "numpy[version='>=1.16.6']", 'pytest', 'pytest-faulthandler', 'pytest-lazy-fixture', "s3fs[version='>=2021.8.0']", 'setuptools', 'setuptools_scm', "clangdev[version='<15']", "llvmdev[version='<15']", 'aws-sdk-cpp==1.10.13', "benchmark[version='>=1.6.0']", "boost-cpp[version='>=1.68.0']", 'brotli', 'bzip2', 'c-ares', 'cmake', 'flatbuffers', 'gflags', 'glog', "gmock[version='>=1.10.0']", "google-cloud-cpp[version='>=1.34.0']", 'grpc-cpp', "gtest[version='>=1.10.0']", 'libprotobuf', 'libutf8proc', 'lz4-c', 'make', 'ninja', 'orc', 'pkg-config', 'python', 'rapidjson', 're2', 'snappy', "thrift-cpp[version='>=0.11.0']", 'xsimd', 'zlib', 'zstd', 'ccache', 'cmake', 'ninja', 'nomkl', 'pandas', 'fsspec', 'python=3.10'] Could not solve for environment specs The following package could not be installed └─ gdb does not exist (perhaps a typo or a missing channel). C:\projects\arrow>set lastexitcode=1 ``` ### What changes are included in this PR? Don't install gdb on Windows. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#35056 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
…ache#35348) ### Rationale for this change Similar to the issue with windows in apache#35057 gdb is also not available for arm64, causing benchmarks to fail. This moves gdb into the dockerfile that actually needs it to prevent further changes. An alternative would be to use multi-arch-gdb but that is only available in `-c memfault` and adding on an entire new channel will only increase solve times and potentially cause problems. * Closes: apache#35346 Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Because it's not available on Windows. ### Rationale for this change The gdb conda package isn't available on Windows: https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/46748401#L266 ```text C:\projects\arrow>mamba create -n arrow -y -c conda-forge --file=ci\conda_env_python.txt --file=ci\conda_env_gandiva_win.txt --file=ci\conda_env_cpp.txt "ccache" "cmake" "ninja" "nomkl" "pandas" "fsspec" "python=3.10" || exit /B conda-forge/win-64 Using cache conda-forge/noarch Using cache Looking for: ['boto3', 'cffi', 'cython', 'cloudpickle', 'fsspec', 'gdb', 'hypothesis', "numpy[version='>=1.16.6']", 'pytest', 'pytest-faulthandler', 'pytest-lazy-fixture', "s3fs[version='>=2021.8.0']", 'setuptools', 'setuptools_scm', "clangdev[version='<15']", "llvmdev[version='<15']", 'aws-sdk-cpp==1.10.13', "benchmark[version='>=1.6.0']", "boost-cpp[version='>=1.68.0']", 'brotli', 'bzip2', 'c-ares', 'cmake', 'flatbuffers', 'gflags', 'glog', "gmock[version='>=1.10.0']", "google-cloud-cpp[version='>=1.34.0']", 'grpc-cpp', "gtest[version='>=1.10.0']", 'libprotobuf', 'libutf8proc', 'lz4-c', 'make', 'ninja', 'orc', 'pkg-config', 'python', 'rapidjson', 're2', 'snappy', "thrift-cpp[version='>=0.11.0']", 'xsimd', 'zlib', 'zstd', 'ccache', 'cmake', 'ninja', 'nomkl', 'pandas', 'fsspec', 'python=3.10'] Could not solve for environment specs The following package could not be installed └─ gdb does not exist (perhaps a typo or a missing channel). C:\projects\arrow>set lastexitcode=1 ``` ### What changes are included in this PR? Don't install gdb on Windows. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#35056 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
…ache#35348) ### Rationale for this change Similar to the issue with windows in apache#35057 gdb is also not available for arm64, causing benchmarks to fail. This moves gdb into the dockerfile that actually needs it to prevent further changes. An alternative would be to use multi-arch-gdb but that is only available in `-c memfault` and adding on an entire new channel will only increase solve times and potentially cause problems. * Closes: apache#35346 Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Because it's not available on Windows.
Rationale for this change
The gdb conda package isn't available on Windows:
https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/46748401#L266
What changes are included in this PR?
Don't install gdb on Windows.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.