Allow custom runners in extension's CI jobs #757
Triggered via pull request
March 24, 2026 13:28
smvv
Status
Cancelled
Total duration
1h 12m 51s
Artifacts
3
TestCITools.yml
on: pull_request
Extension template (C API)
/
Generate matrix
6s
Extension template (custom runners)
/
Generate matrix
10s
Code Quality
/
Format Check
46s
Code Quality
/
Tidy Check
1m 1s
Matrix: Extension template (C API) / linux
Matrix: Extension template (custom runners) / linux
Matrix: Extension template (C API) / macos
Matrix: Extension template (C API) / wasm
Matrix: Extension template (C API) / windows
Matrix: Extension template (custom runners) / macos
Matrix: Extension template (custom runners) / wasm
Matrix: Extension template (custom runners) / windows
Rust builds (using Delta extension)
/
Generate matrix
0s
Matrix: Rust builds (using Delta extension) / linux
Matrix: Extension template / linux
Matrix: Extension template (Rust) / linux
Matrix: Rust builds (using Delta extension) / macos
Matrix: Rust builds (using Delta extension) / wasm
Matrix: Rust builds (using Delta extension) / windows
Matrix: Extension template / macos
Matrix: Extension template / wasm
Matrix: Extension template / windows
Matrix: Extension template (Rust) / macos
Matrix: Extension template (Rust) / wasm
Matrix: Extension template (Rust) / windows
Matrix: Deploy workflow dry run / deploy
Waiting for pending jobs
Annotations
8 errors and 11 warnings
|
Extension template (custom runners) / linux_amd64
No files were found with the provided path: build/release/extension/custom-quack/custom-quack.duckdb_extension. No artifacts will be uploaded.
|
|
Extension template (Rust) / Generate matrix
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Extension template / Generate matrix
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Rust builds (using Delta extension) / Generate matrix
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Test CI Tools
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Test CI Tools
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Test CI Tools
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Test CI Tools
Canceling since a higher priority waiting request for Test CI Tools-refs/pull/346/merge-allow-custom-runners-main-true exists
|
|
Code Quality / Format Check
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. 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 / Tidy Check
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. 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/
|
|
Extension template (C API) / Generate matrix
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/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (custom runners) / Generate matrix
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/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (C API) / linux_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (C API) / linux_amd64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Extension template (C API) / wasm_eh
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, mymindstorm/setup-emsdk@v13. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (custom runners) / linux_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (custom runners) / linux_amd64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Extension template (C API) / windows_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/setup-python@v5, actions/upload-artifact@v4, lukka/run-vcpkg@v11.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Extension template (C API) / windows_amd64
The file vcpkg.json was found multiple times with glob expression '**/vcpkg.json'.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
capi_quack-v1.4.4-extension-linux_amd64
Expired
|
2.42 KB |
sha256:7b33ad97e5ab1db310b62a87902839de6ca399cc8b3ddc27dc54f197e7f09ce7
|
|
|
capi_quack-v1.4.4-extension-wasm_eh
Expired
|
951 Bytes |
sha256:44118ca9d0f1af5c9af00f8c4985b1bf49aa5ae0cd4c52ae7b3e891c293ebb2b
|
|
|
capi_quack-v1.4.4-extension-windows_amd64
Expired
|
5.32 KB |
sha256:c31da039638c48910bcc29f26c41969a12d6fd730722c81bc946af394b829494
|
|