Skip to content

[Release][Integration] Integration job fails on macOS conda AMD64 with SIGSEGV #44386

@raulcd

Description

@raulcd

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:

2024-10-11T10:26:10.4002600Z Testing file flight_sql:extension
2024-10-11T10:26:10.4003710Z ======================================================================
2024-10-11T10:26:10.6458290Z WARNING: Unknown module: org.apache.arrow.memory.core specified to --add-opens
2024-10-11T10:26:10.8922820Z #
2024-10-11T10:26:10.8924670Z # A fatal error has been detected by the Java Runtime Environment:
2024-10-11T10:26:10.8925720Z #
2024-10-11T10:26:10.8926820Z #  SIGSEGV (0xb) at pc=0x000000010b043c3e, pid=27510, tid=259
2024-10-11T10:26:10.8928120Z #
2024-10-11T10:26:10.8929920Z # JRE version: OpenJDK Runtime Environment Zulu22.30+13-CA (22.0.1+8) (build 22.0.1+8)
2024-10-11T10:26:10.8933740Z # Java VM: OpenJDK 64-Bit Server VM Zulu22.30+13-CA (22.0.1+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-amd64)
2024-10-11T10:26:10.8935420Z # Problematic frame:
2024-10-11T10:26:10.8936190Z # C  [python3.13+0x2afc3e]  _PyObject_GC_New+0x13e
2024-10-11T10:26:10.8937530Z #
2024-10-11T10:26:10.8940090Z # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
2024-10-11T10:26:10.8942890Z #
2024-10-11T10:26:10.8944600Z # An error report file with more information is saved as:
2024-10-11T10:26:10.8946530Z # /Users/runner/work/crossbow/crossbow/arrow/hs_err_pid27510.log
2024-10-11T10:26:10.9330250Z #
2024-10-11T10:26:10.9333700Z # If you would like to submit a bug report, please visit:
2024-10-11T10:26:10.9334690Z #   http://www.azul.com/support/
2024-10-11T10:26:10.9335900Z # The crash happened outside the Java Virtual Machine in native code.
2024-10-11T10:26:10.9337540Z # See problematic frame for where to report the bug.
2024-10-11T10:26:10.9339040Z #
2024-10-11T10:26:10.9373180Z arrow/dev/release/verify-release-candidate.sh: line 899: 27510 Abort trap: 6           LD_LIBRARY_PATH=$ARROW_CPP_EXE_PATH:$LD_LIBRARY_PATH archery integration --run-ipc --run-flight --run-c-data --with-cpp=${TEST_INTEGRATION_CPP} --with-java=${TEST_INTEGRATION_JAVA} --with-js=${TEST_INTEGRATION_JS} $INTEGRATION_TEST_ARGS
2024-10-11T10:26:10.9381060Z Failed to verify release candidate. See /var/folders/4b/7k50gk0j4f5bjk3799wdt8nw0000gn/T/arrow-HEAD.XXXXX.B1wU5Qbh for details.
2024-10-11T10:26:10.9625520Z ##[error]Process completed with exit code 134.

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

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions