updating a missing packages.yml (#629) #386
sgn4sangarslc_ci.yml
on: push
prepare-test-container
/
prepare-test-container
1m 14s
Matrix: ci
SLC Allow Merge
3s
Annotations
82 warnings
|
prepare-test-container / prepare-test-container
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/setup-python@v5. 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/
|
|
get-flavors
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / check_for_build / check_for_build
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / build / detect-runner
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / build / build (ubuntu-22.04)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / build / build (ubuntu-22.04-arm)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / build / build (ubuntu-24.04-arm)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / build / build (ubuntu-22.04-arm)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / build / build (ubuntu-24.04)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / build / build (ubuntu-24.04-arm)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (linker_namespace, ubuntu-22.04, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (python, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / build / build (ubuntu-24.04)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / build / build (ubuntu-22.04)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (linker_namespace, ubuntu-24.04, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (pandas, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (generic, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (python, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (pandas, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / build / build (int-linux-arm-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (generic, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / build / build (int-linux-arm-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (linker_namespace, ubuntu-24.04, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (python, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (python, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (linker_namespace, ubuntu-22.04, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (pandas, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (generic, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (generic, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (pandas_mem_leak_dtype, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10) / test / run-tests (pandas_mem_leak_dframe, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (pandas, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (pandas_mem_leak_dtype, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / build / build (int-linux-x64-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (pandas_mem_leak_dframe, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / build / build (int-linux-arm-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.10-conda) / test / run-tests (pandas_mem_leak_dframe, ubuntu-22.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / build / build (int-linux-x64-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (pandas_mem_leak_dframe, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12) / test / run-tests (pandas_mem_leak_dtype, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-all-python-3.12-conda) / test / run-tests (pandas_mem_leak_dtype, ubuntu-24.04, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (gpu, int-linux-x64-4core-gpu-t4-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (gpu, int-linux-x64-4core-gpu-t4-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (linker_namespace, int-linux-x64-2core-ubuntu24.04-1, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (linker_namespace, int-linux-x64-2core-ubuntu24.04-1, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / build / build (int-linux-x64-4core-ubuntu24.04-1)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / detect-test-matrix
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (python, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (python, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (pandas, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (generic, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (pandas, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (generic, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (linker_namespace, int-linux-x64-2core-ubuntu24.04-1, base_test_build_run)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (pandas_mem_leak_dtype, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (gpu, int-linux-x64-4core-gpu-t4-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (python, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.10-cuda-conda) / test / run-tests (pandas_mem_leak_dframe, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (pandas_mem_leak_dframe, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (generic, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (pandas, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (template-Exasol-8-python-3.12-cuda-conda) / test / run-tests (pandas_mem_leak_dtype, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (pandas_mem_leak_dframe, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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/
|
|
ci (test-Exasol-8-cuda-ml) / test / run-tests (pandas_mem_leak_dtype, int-linux-x64-2core-ubuntu24.04-1, release)
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/setup-python@v5. 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 | |
|---|---|---|---|
|
logs_build_template-Exasol-8-python-3.10-cuda-conda_int-linux-arm-4core-ubuntu24.04-1
|
991 KB |
sha256:758f7f4009e3cf4024688eb1c426b7f65b8447114cb41431f498462d3cde7817
|
|
|
logs_build_template-Exasol-8-python-3.10-cuda-conda_int-linux-x64-4core-ubuntu24.04-1
|
1.15 MB |
sha256:79dc7011003314c070b5fc8b408703771ecbba13430bdc4af24023431596f5fe
|
|
|
logs_build_template-Exasol-8-python-3.12-cuda-conda_int-linux-arm-4core-ubuntu24.04-1
|
987 KB |
sha256:7f677b92ee375f87786089a592e7fd9616bee0d74fe6fd837084427835958180
|
|
|
logs_build_template-Exasol-8-python-3.12-cuda-conda_int-linux-x64-4core-ubuntu24.04-1
|
1.15 MB |
sha256:1affebad6af6997814b8cf56d41b6cc5318642ac6e05439699ba30d18ddf5f59
|
|
|
logs_build_template-Exasol-all-python-3.10-conda_ubuntu-22.04
|
949 KB |
sha256:7ebc908f47e9135201a421aa53e0eacba30f034946304f8b05028657afa15e1b
|
|
|
logs_build_template-Exasol-all-python-3.10-conda_ubuntu-22.04-arm
|
883 KB |
sha256:091137878b8d112ee8448b55e022c45b4c34f6f8e3918e45ec5a2481526d5f42
|
|
|
logs_build_template-Exasol-all-python-3.10_ubuntu-22.04
|
974 KB |
sha256:c22619cfd4c7c33b00559502feff6a2bc7c0a7aca9e5a38829f6c771c3971495
|
|
|
logs_build_template-Exasol-all-python-3.10_ubuntu-22.04-arm
|
972 KB |
sha256:df648606cc6ef78ce37b0e07be99af1ba45a542e497631234f6602d87642304a
|
|
|
logs_build_template-Exasol-all-python-3.12-conda_ubuntu-24.04
|
925 KB |
sha256:2541cbb7c341c5c94807885c180ce67299dba3413d2730521cfcbe0f65068b95
|
|
|
logs_build_template-Exasol-all-python-3.12-conda_ubuntu-24.04-arm
|
871 KB |
sha256:9beacfdab6830e4225238958da73c2130225963650082e158adcde2609c3212c
|
|
|
logs_build_template-Exasol-all-python-3.12_ubuntu-24.04
|
978 KB |
sha256:4c51d8c64ebd0dc7accc01116e9a933d3ad364d62460628d5641bb7384f92aba
|
|
|
logs_build_template-Exasol-all-python-3.12_ubuntu-24.04-arm
|
968 KB |
sha256:b5d003cac08056cdf42f651cb2ebd7313499b2c64fcbc6b0b19db881c014f274
|
|
|
logs_build_test-Exasol-8-cuda-ml_int-linux-arm-4core-ubuntu24.04-1
|
1.12 MB |
sha256:a9743224ac56aad12850ead9c2ad112ba149346002e06a62172680fbb6346d58
|
|
|
logs_build_test-Exasol-8-cuda-ml_int-linux-x64-4core-ubuntu24.04-1
|
1.38 MB |
sha256:b821008fde8a91c1eea9c2ad96367610720c259e3b105b7777b65540eea33f49
|
|
|
logs_prepare_test_container
|
24.7 KB |
sha256:06e4284a427a37e45ea46fc2404cbf9c633622eddb05df9eee3fc58ca07f3b26
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_generic_int-linux-x64-2core-ubuntu24.04-1
|
614 KB |
sha256:131da4a460ce907b2561cb83b98c6d99444a7f849cab1b1bed2dd85d01ffa73f
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_gpu_int-linux-x64-4core-gpu-t4-ubuntu24.04-1
|
431 KB |
sha256:929e1ee5a2f33b42b5c6e9ca18df7c3228794d46f0f4a038b8c9ba5e03a3dfd9
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_linker_namespace_int-linux-x64-2core-ubuntu24.04-1
|
460 KB |
sha256:c62d111bd034f547776048def6be54c0ab4125e0fc9407e537bd75b1d041fe06
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_pandas_int-linux-x64-2core-ubuntu24.04-1
|
532 KB |
sha256:df27bbabef591cbe29ac07db66436f3e407dd3443482e49bf26b2c6b1f847090
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_pandas_mem_leak_dframe_int-linux-x64-2core-ubuntu24.04-1
|
719 KB |
sha256:ac3da49671c2fe4f1abff084ed864a47f1f65b959ea84065ff360986790d4d10
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_pandas_mem_leak_dtype_int-linux-x64-2core-ubuntu24.04-1
|
681 KB |
sha256:67869c139982c23ac78e3ed30d29564a7bb36005a9913a249b46c4a2e46ee1f2
|
|
|
logs_tests_template-Exasol-8-python-3.10-cuda-conda_python_int-linux-x64-2core-ubuntu24.04-1
|
512 KB |
sha256:139969b5f3e2ddd7a7fc5aa130f4d430de18227066b03c24885dbe8d95cf9350
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_generic_int-linux-x64-2core-ubuntu24.04-1
|
610 KB |
sha256:b010b01b373041ea894a905b950ab8f06a93806d67807e622280c970f2e585e3
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_gpu_int-linux-x64-4core-gpu-t4-ubuntu24.04-1
|
430 KB |
sha256:30bd1cdb32ad91057b0b2b3df0f749f6a3609fe0577c1fc0681eaceb76ebf691
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_linker_namespace_int-linux-x64-2core-ubuntu24.04-1
|
446 KB |
sha256:9964611034aa6dc10e7457fa423a336c3ba6c85b7182e96a2449b37fd19feefc
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_pandas_int-linux-x64-2core-ubuntu24.04-1
|
547 KB |
sha256:9749d74fc4282b451c720d2756c8f036e9aba6d4c74bf2f6c54bec7d3018e961
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_pandas_mem_leak_dframe_int-linux-x64-2core-ubuntu24.04-1
|
784 KB |
sha256:591b95fd7d8504f6cc77fb687b5a59089eda708286d94d7c46df42cb5d2c42fb
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_pandas_mem_leak_dtype_int-linux-x64-2core-ubuntu24.04-1
|
864 KB |
sha256:e3cb83087482b53e141daa45a5a1099bff7894595fa22613935e88e3723030e5
|
|
|
logs_tests_template-Exasol-8-python-3.12-cuda-conda_python_int-linux-x64-2core-ubuntu24.04-1
|
511 KB |
sha256:6e56247e570601d452231e0422540bf41bc15804c8b6ed06c6d3acbbc0ac2e45
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_generic_ubuntu-22.04
|
501 KB |
sha256:7b9bf5ae10fed961907eaf59b835a2a9588fe7a2ecaef890bede613d375af9f2
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_linker_namespace_ubuntu-22.04
|
390 KB |
sha256:879ce81f2328996bed6ffff59236de07d5a35e24b30b930a1fa5b6989ee3b026
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_pandas_mem_leak_dframe_ubuntu-22.04
|
543 KB |
sha256:884e35b2abe745ec4c9351f9e7b922ab19ca2924fbc05b98ac15ddb4494dad73
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_pandas_mem_leak_dtype_ubuntu-22.04
|
505 KB |
sha256:91d5dc32e601cd787a7aea1328733a554677f6f2410ad4437f71134818c45288
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_pandas_ubuntu-22.04
|
440 KB |
sha256:2bc02c8fc58f849303f284b54f61105d0620e648604ae4c3f6adc762dc957bba
|
|
|
logs_tests_template-Exasol-all-python-3.10-conda_python_ubuntu-22.04
|
435 KB |
sha256:c0c90669ac59f730273a1167569e3190326ecbad845659585608af96f6195e8f
|
|
|
logs_tests_template-Exasol-all-python-3.10_generic_ubuntu-22.04
|
494 KB |
sha256:356ac655dd6e4f02a3e342f8628e269a4bc4321c7cda3ab77ec619cda5bcf708
|
|
|
logs_tests_template-Exasol-all-python-3.10_linker_namespace_ubuntu-22.04
|
371 KB |
sha256:a629986aef5671de94d88f1d58fa62181daad6c77a49cb4aacd710f253e62819
|
|
|
logs_tests_template-Exasol-all-python-3.10_pandas_mem_leak_dframe_ubuntu-22.04
|
540 KB |
sha256:a2e6d59da4292248e10579a69de5dbae5bf29c64da5f890acfcc6458bb19a61b
|
|
|
logs_tests_template-Exasol-all-python-3.10_pandas_mem_leak_dtype_ubuntu-22.04
|
519 KB |
sha256:85454db6da1f4d272dfaf2a026cc40b3d0c8c279c3db2a43a3f92b98df596062
|
|
|
logs_tests_template-Exasol-all-python-3.10_pandas_ubuntu-22.04
|
439 KB |
sha256:ff056db8cfee7bc8a17e25475bcddd53a2c369370aeffeec73338087d8772b30
|
|
|
logs_tests_template-Exasol-all-python-3.10_python_ubuntu-22.04
|
361 KB |
sha256:e596da4efa6bf3ac12eb33a932f914c210a8b3653abe001c8f69a73d0da33ebe
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_generic_ubuntu-24.04
|
504 KB |
sha256:2b404187b4fc412c6d377195e0d8bb5866bd8617bddca23a5d1ec16b9874f987
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_linker_namespace_ubuntu-24.04
|
395 KB |
sha256:57f5ccac27293d60ffb6a248719bc0b18f13a7a57d6157b15ead0d8aa6f166aa
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_pandas_mem_leak_dframe_ubuntu-24.04
|
583 KB |
sha256:2c4e275e1949a252038db720f89a34de8057b3222ceafb7f82df9c784256acfe
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_pandas_mem_leak_dtype_ubuntu-24.04
|
626 KB |
sha256:692b197ed223b83410271d023b66eb1dfaa866ce302ed839a55d706c2f65ab67
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_pandas_ubuntu-24.04
|
455 KB |
sha256:e4fef760a073baa80361e4eabb0f2f526f9881b22c21b813bd261737d63df391
|
|
|
logs_tests_template-Exasol-all-python-3.12-conda_python_ubuntu-24.04
|
445 KB |
sha256:eb4ecce6aa02b7fcd7f1d63a9e9755ffeeec761cab0299e7dee773dedbf8da88
|
|
|
logs_tests_template-Exasol-all-python-3.12_generic_ubuntu-24.04
|
501 KB |
sha256:d4458a56ceee3fbbf4e00cb397a0a7ac0ab9b15e37c2ee5e48d22013b019e2d7
|
|
|
logs_tests_template-Exasol-all-python-3.12_linker_namespace_ubuntu-24.04
|
377 KB |
sha256:63a630b275e4c7a2cd6ae6727194d33355d824c6b47c5cceb94f529739ec7b43
|
|
|
logs_tests_template-Exasol-all-python-3.12_pandas_mem_leak_dframe_ubuntu-24.04
|
610 KB |
sha256:137699d7a69f47718e3b29f282b4f05a5b9d355f774807b4662887fb7dd7c21b
|
|
|
logs_tests_template-Exasol-all-python-3.12_pandas_mem_leak_dtype_ubuntu-24.04
|
655 KB |
sha256:e12f928315a42892e7894b3ea4faf159593599d1b2827eb050a8a10ca6a727f6
|
|
|
logs_tests_template-Exasol-all-python-3.12_pandas_ubuntu-24.04
|
437 KB |
sha256:97b45d16d55282172ae50126ee9a69fdb27cd89e4ba8c301d3c72d75e51eb81d
|
|
|
logs_tests_template-Exasol-all-python-3.12_python_ubuntu-24.04
|
442 KB |
sha256:f0988a66c0ba6e6e29a942046c687190f3307669af45500c6391bae7703d2824
|
|
|
logs_tests_test-Exasol-8-cuda-ml_generic_int-linux-x64-2core-ubuntu24.04-1
|
652 KB |
sha256:99715b462d8f4fd3d72a59af5e68f644024e8303ce657ec4020eaf9138a6de1d
|
|
|
logs_tests_test-Exasol-8-cuda-ml_gpu_int-linux-x64-4core-gpu-t4-ubuntu24.04-1
|
481 KB |
sha256:f3ed10f319353bbd0a15c6ddd5ed0617e0d428f5611dfa93df69dcbc65a8afcc
|
|
|
logs_tests_test-Exasol-8-cuda-ml_linker_namespace_int-linux-x64-2core-ubuntu24.04-1
|
419 KB |
sha256:0d8f800a91218de739f0752c587ed0debaca46f38428df70e960ed11202c8853
|
|
|
logs_tests_test-Exasol-8-cuda-ml_pandas_int-linux-x64-2core-ubuntu24.04-1
|
577 KB |
sha256:98a56bd1f4c6afc1197364dfa64a165aafbcde39e27717f04986cc4ccd810c48
|
|
|
logs_tests_test-Exasol-8-cuda-ml_pandas_mem_leak_dframe_int-linux-x64-2core-ubuntu24.04-1
|
811 KB |
sha256:1d442114089028febb2ebb7535dce85439782381497429ad802ffebcef58fa44
|
|
|
logs_tests_test-Exasol-8-cuda-ml_pandas_mem_leak_dtype_int-linux-x64-2core-ubuntu24.04-1
|
890 KB |
sha256:0ebb1ecd3202c19fdb82435428756eb41cbbd052c9fca81b9968c6a9d342bc96
|
|
|
logs_tests_test-Exasol-8-cuda-ml_python_int-linux-x64-2core-ubuntu24.04-1
|
562 KB |
sha256:13a3cf890ef9535ed90bb9dd1b2991e5f02fd00b438a01f5437e0b7f316fd3af
|
|
|
slc-template-Exasol-8-python-3.10-cuda-conda-base_test_build_run-aarch64
|
3.04 GB |
sha256:a21f4a1b5e8e13412798b55ab5dc908401500a53678a244e070fa1758a0c1eed
|
|
|
slc-template-Exasol-8-python-3.10-cuda-conda-base_test_build_run-x86_64
|
3.67 GB |
sha256:9fc145b7fb910cf60c8d7877aec13cdeaa8b89ff245d91bc4d79aaadf9d8f9b8
|
|
|
slc-template-Exasol-8-python-3.10-cuda-conda-release-aarch64
|
2.67 GB |
sha256:c762307a5946913ed38fa72bfb058624a564dccd441c221284fbc9926b4c5e5f
|
|
|
slc-template-Exasol-8-python-3.10-cuda-conda-release-x86_64
|
3.26 GB |
sha256:79ae42604a705ff1828238a600c3df01e10f7dc2d6ccaa6b444a9c6f02ffd184
|
|
|
slc-template-Exasol-8-python-3.12-cuda-conda-base_test_build_run-aarch64
|
3.08 GB |
sha256:37d860d2764b8eedfd40e65117d8a928db62a7ad4ef420bc0dfd4bcf2fe862ec
|
|
|
slc-template-Exasol-8-python-3.12-cuda-conda-base_test_build_run-x86_64
|
3.72 GB |
sha256:4cb6d13a18a96191a4381918163f68c3b2e14805ffb8c8433c0d57e3e3b03b29
|
|
|
slc-template-Exasol-8-python-3.12-cuda-conda-release-aarch64
|
2.72 GB |
sha256:11aad03062b130b88512b6da2c9c7e388ea7d163e5440b9f89914372944370a0
|
|
|
slc-template-Exasol-8-python-3.12-cuda-conda-release-x86_64
|
3.33 GB |
sha256:edd135b593cc0eb7f3d1ac055f74675fd560fe149cdd3c32a7bab622b8657b59
|
|
|
slc-template-Exasol-all-python-3.10-base_test_build_run-aarch64
|
812 MB |
sha256:7a45bbc79dd6829dd2bc4455ba6cd87644eab9d2167dce1a4b3c8cd6fd3f4e59
|
|
|
slc-template-Exasol-all-python-3.10-base_test_build_run-x86_64
|
760 MB |
sha256:fa8f161eb3dca153deb1bb4cc8f20c5d0d39a2fa8ce94194fd667b5addee8948
|
|
|
slc-template-Exasol-all-python-3.10-conda-base_test_build_run-aarch64
|
920 MB |
sha256:5d897b679de18f71fa23e648f869e18ce52c776ea7493df7ddd49982712d6087
|
|
|
slc-template-Exasol-all-python-3.10-conda-base_test_build_run-x86_64
|
1000 MB |
sha256:1e6a1914b8ac2b911a55de49dfee2fab4294392d66d75b12dbb05e8da197f730
|
|
|
slc-template-Exasol-all-python-3.10-conda-release-aarch64
|
293 MB |
sha256:8566005a91a6e29b04ebf4fd3e4fa85d3d0e14c35b73afce0fa7c2b671486a09
|
|
|
slc-template-Exasol-all-python-3.10-conda-release-x86_64
|
335 MB |
sha256:d8161b0e8995af0a56c0f586bca32441f391385fce13261e3706f6f1a05a03d7
|
|
|
slc-template-Exasol-all-python-3.10-release-aarch64
|
468 MB |
sha256:8feffb9bf64e939531850e70697c33e85116894c84454ee4c729d28162294acb
|
|
|
slc-template-Exasol-all-python-3.10-release-x86_64
|
388 MB |
sha256:f14518f40eafdc32eaa3d9ccd648ec4c3f55c0fd587bd6d7cdcd580ca06f3e9a
|
|
|
slc-template-Exasol-all-python-3.12-base_test_build_run-aarch64
|
799 MB |
sha256:8571aa106ede9fdd97c315f89b35c359e097ad44908e33eee183a848b7357e2f
|
|
|
slc-template-Exasol-all-python-3.12-base_test_build_run-x86_64
|
835 MB |
sha256:8b1cca8b7915fbf914f5361ea7449e9dff5737d9a3f57453e3e8fde7ee057ec0
|
|
|
slc-template-Exasol-all-python-3.12-conda-base_test_build_run-aarch64
|
965 MB |
sha256:dd7769d892cf957a5f1a928a9de8699a721ca5cdebeb010479ddcb4f2998cad3
|
|
|
slc-template-Exasol-all-python-3.12-conda-base_test_build_run-x86_64
|
1.04 GB |
sha256:e6f87722561e2209f9aacc331fd67d6e402682ba83c1a27a315d5011a0938a9c
|
|
|
slc-template-Exasol-all-python-3.12-conda-release-aarch64
|
302 MB |
sha256:8461d853b1e6d73da94cee851b84079265aef798c6d06dd468729d3a6155f3ef
|
|
|
slc-template-Exasol-all-python-3.12-conda-release-x86_64
|
365 MB |
sha256:cff1b6f34cb01a8c32068ece473a0985fcde360372558747bd8af346bfd41548
|
|
|
slc-template-Exasol-all-python-3.12-release-aarch64
|
390 MB |
sha256:9023f76230fb2b3c259fd46712ba827fc59edab974a9734e5af05fea1553c633
|
|
|
slc-template-Exasol-all-python-3.12-release-x86_64
|
407 MB |
sha256:63d3fd866c243dfc557a847c3c0ec0cf921ccae1b63edcd0433cf7f520bcf781
|
|
|
slc-test-Exasol-8-cuda-ml-base_test_build_run-aarch64
|
954 MB |
sha256:8495099f79d0cac7fea9e833c75647559326389170be1a484dbfe6352153e102
|
|
|
slc-test-Exasol-8-cuda-ml-base_test_build_run-x86_64
|
1.03 GB |
sha256:d10c6de720d5762ef3b691812156b30cfd0c837efcbc0ec73602b4bb72c4f48b
|
|
|
slc-test-Exasol-8-cuda-ml-release-aarch64
|
6.31 GB |
sha256:888427cf785ac8beb57e7f81134b5fc99f1641d179d9ce62f38afded5542fb78
|
|
|
slc-test-Exasol-8-cuda-ml-release-x86_64
|
7.15 GB |
sha256:a01f6147bc536710b81ccbe5cb91d5fe0c38a268e5208ff57c2e2e0b4a819596
|
|