[Release][Integration] Integration job fails on macOS conda AMD64 with SIGSEGV #44386
Assignees
Labels
Component: Integration
Component: Release
Priority: Blocker
Marks a blocker for the release
Type: bug
Milestone
Comments
raulcd
added a commit
to raulcd/arrow
that referenced
this issue
Oct 12, 2024
…n verification when using Conda
raulcd
changed the title
|
I don't know why the Java integration test runner uses Python. |
|
Hmm, that's odd. The Python bit should only be to spawn processes, so why is Java seemingly calling into Python? And this is macOS amd64, so it'll be hard to reproduce... |
|
Yeah, that's odd. It's almost as if the fork+exec in |
|
I was able to reproduce this on my own crossbow repo after splicing in a tmate step and running the verification manually. Patch below. I'm poking around now. github.macos.yml.patchdiff --git a/dev/tasks/verify-rc/github.macos.yml b/dev/tasks/verify-rc/github.macos.yml
index 4bc3fff71..82af4a02a 100644
--- a/dev/tasks/verify-rc/github.macos.yml
+++ b/dev/tasks/verify-rc/github.macos.yml
@@ -59,6 +59,9 @@ jobs:
with:
node-version: '20'
+ - name: Setup tmate session
+ uses: mxschmitt/action-tmate@v3
+
- name: Run verification
shell: bash
env: |
|
Here's the output of hs_err_pid49681.logThe above makes it look like JPype is involved after all? |
|
Ok, so it's the
|
|
I'll start a new run with PYTHONFAULTHANDLER=1 on. The failure I reproduced crashed in the |
|
Here's what I get with PYTHONFAULTHANDLER=1: Edit: PS I'll be offline until later my time. |
kou
added a commit
that referenced
this issue
Oct 12, 2024
…fication when using Conda (#44388) ### Rationale for this change Conda Python 3.13 fails when running verification tasks for Java. It's related to JPype. See also: * GH-44389 * https://discuss.python.org/t/api-for-python-3-13-prevents-use-of-3rd-party-gc-allocators/62709/5 ### What changes are included in this PR? Pin Python 3.12 on Conda integration jobs because JPype doesn't work with Python 3.13. We can use Python 3.13 again once JPype supports Python 3.13. ### Are these changes tested? Yes via CI ### Are there any user-facing changes? No * GitHub Issue: #44386 Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
|
Issue resolved by pull request 44388 |
raulcd
added a commit
that referenced
this issue
Oct 13, 2024
…fication when using Conda (#44388) ### Rationale for this change Conda Python 3.13 fails when running verification tasks for Java. It's related to JPype. See also: * GH-44389 * https://discuss.python.org/t/api-for-python-3-13-prevents-use-of-3rd-party-gc-allocators/62709/5 ### What changes are included in this PR? Pin Python 3.12 on Conda integration jobs because JPype doesn't work with Python 3.13. We can use Python 3.13 again once JPype supports Python 3.13. ### Are these changes tested? Yes via CI ### Are there any user-facing changes? No * GitHub Issue: #44386 Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
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.
The verify-rc-source-integration-macos-conda-amd64 job has been failing since the 9th of October with a
SIGSEGV:This is also failing on the maintenance branch.
The commits introduced are not related 64891d1...1c601a5
It seems to have to do with Python 3.13. The last successful job used Python 3.12.
Component(s)
Integration, Release
The text was updated successfully, but these errors were encountered: