Skip to content

feat: Add executor pool size to S3 configs #40166

feat: Add executor pool size to S3 configs

feat: Add executor pool size to S3 configs #40166

Re-run triggered March 23, 2026 14:14
Status Failure
Total duration 50m 10s
Artifacts 3

linux-build.yml

on: pull_request
Build with GCC  /  get-changes
24s
Build with GCC / get-changes
Build with GCC  /  Ubuntu debug with system dependencies
50m 2s
Build with GCC / Ubuntu debug with system dependencies
Build with GCC  /  Fedora debug
32m 29s
Build with GCC / Fedora debug
Build with GCC  /  Linux release with adapters
17m 15s
Build with GCC / Linux release with adapters
Build with GCC  /  cudf-tests
0s
Build with GCC / cudf-tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Build with GCC / Linux release with adapters
Process completed with exit code 1.
Build with GCC / Linux release with adapters
Process completed with exit code 2.
Build with GCC / Linux release with adapters
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
Build with GCC / Fedora debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
Build with GCC / Ubuntu debug with system dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

Artifacts

Produced during runtime
Name Size Digest
ccache-fedora-debug-default-gcc-16879_merge Expired
28.5 MB
sha256:523df640632e9d0cfaaefafb48a0c0376c6e1085eb578a6eddc21ddb002346e6
ccache-ubuntu-debug-default-gcc-16879_merge Expired
4.24 GB
sha256:cad92260c4d94bb6a1f1dfaa3f99c631538e32eb312d79b6058333b6cdc787a7
cudftestbinaries
3.32 KB
sha256:c313b6f1817d3a460ab008b21f1795499637230bbc974f7bb72023375da3c55a