Skip to content
Tests and builds on PR

Fix segfault on join with None #492

Sign in to view logs

Fix segfault on join with None

Fix segfault on join with None #492

Triggered via pull request April 9, 2026 11:24
@evertlammertsevertlammerts
opened #422
evertlammerts:triage_353
Status Failure
Total duration 59m 10s
Artifacts 1

on_pr.yml

on: pull_request
Make sure submodule is in a sane state  /  Make sure submodule is in a sane state
32s
Make sure submodule is in a sane state / Make sure submodule is in a sane state
Code-quality checks  /  Run linting, formatting and static type checker
48s
Code-quality checks / Run linting, formatting and static type checker
Run coverage tests  /  Generate code coverage reports for both Python and C++ code
Run coverage tests / Generate code coverage reports for both Python and C++ code
Build a minimal set of packages and run all tests on them  /  ...  /  Build sdist
22m 23s
Build a minimal set of packages and run all tests on them / Build an sdist and determine versions / Build sdist
Matrix: Build a minimal set of packages and run all tests on them / Build and test releases / build_wheels
Run coverage tests  /  Coverage Summary
Run coverage tests / Coverage Summary
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 14 warnings
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_aarch64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_aarch64
cibuildwheel: Command ['sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /project/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build an sdist and determine versions / Build sdist
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_arm64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_arm64
cibuildwheel: Command ['/bin/sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /Users/runner/work/duckdb-python/duckdb-python/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_x86_64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_x86_64
cibuildwheel: Command ['sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /project/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_x86_64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_x86_64
cibuildwheel: Command ['sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /project/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_aarch64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_aarch64
cibuildwheel: Command ['sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /project/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_arm64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_arm64
cibuildwheel: Command ['/bin/sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /Users/runner/work/duckdb-python/duckdb-python/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_x86_64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_x86_64
cibuildwheel: Command ['/bin/sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /Users/runner/work/duckdb-python/duckdb-python/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-win_amd64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-win_amd64
cibuildwheel: Command uv run -v pytest --confcutdir=. --rootdir . -c D:\a\duckdb-python\duckdb-python/pyproject.toml ./tests
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_x86_64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_x86_64
cibuildwheel: Command ['/bin/sh', '-c', 'uv run -v pytest --confcutdir=. --rootdir . -c /Users/runner/work/duckdb-python/duckdb-python/pyproject.toml ./tests\n'] failed with code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-win_amd64
Process completed with exit code 1.
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-win_amd64
cibuildwheel: Command uv run -v pytest --confcutdir=. --rootdir . -c D:\a\duckdb-python\duckdb-python/pyproject.toml ./tests
Make sure submodule is in a sane state / Make sure submodule is in a sane state
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Code-quality checks / Run linting, formatting and static type checker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build an sdist and determine versions / Build sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-manylinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-manylinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-macosx_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-win_ARM64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp314-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-macosx_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build a minimal set of packages and run all tests on them / Build and test releases / Wheel: cp310-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
wheel-cp314-win_ARM64
13.7 MB
sha256:93620244d87d6defef9e124cc37a07a67e5875790e5748de837bab74e59ed6c2