[#1805] feat(spark): Support Spark 4 in client-spark/extension #7939
LuciferYangbuild.yml
on: pull_request
changes
/
detect
5s
spotless
/
java 8
1m 16s
docker
/
speculate fail tasks
8m 36s
Event File
4s
Matrix: integration / maven
Matrix: unit / maven
kubernetes
/
maven
Annotations
71 errors, 39 warnings, and 3 notices
|
unit / -Pspark3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.2
The operation was canceled.
|
|
unit / -Pspark3.0
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.0
The operation was canceled.
|
|
unit / -Pmr-hadoop2.8
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pmr-hadoop2.8
The operation was canceled.
|
|
integration / -Pspark3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.2
The operation was canceled.
|
|
integration / -Pspark2
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark2
The operation was canceled.
|
|
unit / -Pspark4
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark4
The operation was canceled.
|
|
integration / -Pspark3.4
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.4
The operation was canceled.
|
|
integration / -Pspark3.3
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.3
The operation was canceled.
|
|
docker / speculate fail tasks
Canceling since a higher priority waiting request for build-2749 exists
|
|
docker / speculate fail tasks
The operation was canceled.
|
|
integration / -Pspark2.3
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark2.3
The operation was canceled.
|
|
integration / -Ptez
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pmr-hadoop2.8
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pmr-hadoop2.8
The operation was canceled.
|
|
integration / -Ptez
The operation was canceled.
|
|
integration / -Pspark3.5-scala2.13
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.5-scala2.13
The operation was canceled.
|
|
unit / -Pspark3.5
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.5
The operation was canceled.
|
|
unit / -Pspark3.4
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.4
The operation was canceled.
|
|
unit / -Pdashboard
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Ptez-hadoop3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pdashboard
The operation was canceled.
|
|
integration / -Ptez-hadoop3.2
The operation was canceled.
|
|
integration / -Pspark4
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark4
The operation was canceled.
|
|
integration / -Pspark3
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3
The operation was canceled.
|
|
unit / -Ptez-hadoop3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Ptez-hadoop3.2
The operation was canceled.
|
|
unit / -Pmr-hadoop3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pmr-hadoop3.2
The operation was canceled.
|
|
integration / -Pspark3.0
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.0
The operation was canceled.
|
|
integration / -Pmr-hadoop3.2
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pmr-hadoop3.2
The operation was canceled.
|
|
unit / -Pspark3.3
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.3
The operation was canceled.
|
|
integration / -Pspark3.2.0
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.2.0
The operation was canceled.
|
|
unit / -Pspark3
The operation was canceled.
|
|
unit / -Pspark2.3
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark2.3
The operation was canceled.
|
|
unit / -Pspark3.5-scala2.13
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.5-scala2.13
The operation was canceled.
|
|
unit / -Ptez
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Ptez
The operation was canceled.
|
|
unit / -Pspark2
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark2
The operation was canceled.
|
|
unit / -Pspark3.2.0
Canceling since a higher priority waiting request for build-2749 exists
|
|
unit / -Pspark3.2.0
The operation was canceled.
|
|
integration / -Pspark3.5
Canceling since a higher priority waiting request for build-2749 exists
|
|
integration / -Pspark3.5
The operation was canceled.
|
|
spotbugs / java 8
Canceling since a higher priority waiting request for build-2749 exists
|
|
spotbugs / java 8
The operation was canceled.
|
|
build
Canceling since a higher priority waiting request for build-2749 exists
|
|
build
Canceling since a higher priority waiting request for build-2749 exists
|
|
build
Canceling since a higher priority waiting request for build-2749 exists
|
|
build
Canceling since a higher priority waiting request for build-2749 exists
|
|
build
Canceling since a higher priority waiting request for build-2749 exists
|
|
Event File
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. 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/
|
|
changes / detect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
license / java 8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3. 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/
|
|
spotless / java 8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3. 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/
|
|
checkstyle / java 8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3. 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/
|
|
integration / -Pdashboard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4, codecov/codecov-action@v3. 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/
|
|
unit / -Pspark3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pmr-hadoop2.8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / speculate fail tasks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3. 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/
|
|
integration / -Pspark2.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pmr-hadoop2.8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Ptez
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.5-scala2.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pdashboard
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Ptez-hadoop3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Ptez-hadoop3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pmr-hadoop3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pmr-hadoop3.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.2.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark2.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.5-scala2.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Ptez
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit / -Pspark3.2.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
integration / -Pspark3.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
spotbugs / java 8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3. 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/
|
|
11 skipped tests found
There are 11 skipped tests, see "Raw output" for the full list of skipped tests.
|
|
951 tests found (test 1 to 723)
There are 951 tests, see "Raw output" for the list of tests 1 to 723.
|
|
951 tests found (test 724 to 951)
There are 951 tests, see "Raw output" for the list of tests 724 to 951.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Event File
|
4.93 KB |
sha256:e244e017bb4592768fce1c156097f6f5ae0c4635bd7fac9fc1f3441316eb45dd
|
|
|
integration-reports-dashboard
|
1.13 MB |
sha256:d2ad041aa4af4e1eaa12f19d0817e1b496a18bb8932f7d1aade150bb04ee0bfc
|
|
|
integration-reports-mr-hadoop2.8
|
1.2 MB |
sha256:71963cfc89c9aa1a013272fd8013fffe9aab543f306db4be03ffdc30d766e2fc
|
|
|
integration-reports-mr-hadoop3.2
|
1.21 MB |
sha256:d6bc0c4f8617a8ff8c248915cf0c6cd9c63816ecaae9c45c9fa3c25a09764c59
|
|
|
integration-reports-spark2
|
1.24 MB |
sha256:aa9490be7f338553c3bde0177d32b5ea6c97f0d041a57277504e110729e076fb
|
|
|
integration-reports-spark2.3
|
1.3 MB |
sha256:ab92380eace62fed9aa675cd02d2d309cc9df9ae9cdde3546e72301ccb774451
|
|
|
integration-reports-spark3
|
1.29 MB |
sha256:5dd16a16f98e8fb30b5558c4a60a13d081e8b744501584ecb41b2b6eaf01f806
|
|
|
integration-reports-spark3.0
|
1.29 MB |
sha256:99a30ce5ca85e410a784d8b7a2476968183fd77839be22d1bcb619052e238a2d
|
|
|
integration-reports-spark3.2
|
1.22 MB |
sha256:e6f90d004079302ecaa656a1ac767ad11339beb2db59c645f5ef959eb0db6288
|
|
|
integration-reports-spark3.2.0
|
1.24 MB |
sha256:f4c4954b0721955917cd29f49d7d7492a8bfd76ed86dc660b47df47bbfc5b00c
|
|
|
integration-reports-spark3.3
|
1.17 MB |
sha256:bd30e4126fb142bc56a549ffcaeefeb7f97e625c62e19ca9338267adeb757ad1
|
|
|
integration-reports-spark3.4
|
1.26 MB |
sha256:e18775a571b82745cdd67b32b927afd7c728cde47777d536285ff3658a19cc91
|
|
|
integration-reports-spark3.5
|
1.26 MB |
sha256:decd5c8633b109059dc2fa386e59273d8ed65aa3392d685fcd715ce6707acb2a
|
|
|
integration-reports-spark3.5-scala2.13
|
1.26 MB |
sha256:a4956ed30d83ad16e5c506108e3a0a46ef19f2935091aced588fbfcee82906c8
|
|
|
integration-reports-spark4
|
1.3 MB |
sha256:b3f74fba53073c30fd35729fc59aeda04766da192e91ed156c23c00e45c8e87e
|
|
|
integration-reports-tez
|
1.23 MB |
sha256:4a27bfeba0131167f22276cfb6c3c5884e18354811da8ecb363f4aa1b01edfe8
|
|
|
integration-reports-tez-hadoop3.2
|
1.24 MB |
sha256:005afb29efed48e447f120fb6f1e6e7b87cebefacbaa30c893ac5e65f687a9cf
|
|
|
unit-reports-dashboard
|
1.11 MB |
sha256:9f0e8a85b0406f27a69c7d94f0eeb277ffb2ef73f5a1aa4f19c5b2a8bfa2a2cc
|
|
|
unit-reports-mr-hadoop2.8
|
1.04 MB |
sha256:8bf62069f23ab37b3cebe9724bd8b615ff8dec2a994750202a08f47e3b459288
|
|
|
unit-reports-mr-hadoop3.2
|
1.08 MB |
sha256:809cd405dcd2f7db10cf52ffd76a47e7afd17239c5f243076b0eb57d13640aaa
|
|
|
unit-reports-spark2
|
1.11 MB |
sha256:037ac37511413b25ffbc52f3f79080ac4b3557f0435c93fe69d500ba7606faa5
|
|
|
unit-reports-spark2.3
|
1.11 MB |
sha256:74d17320e070634883520570f12ac433b27e29b5c09678b6adaea8858dc63964
|
|
|
unit-reports-spark3
|
1.09 MB |
sha256:11e9885438b4d99fab913a048ecf9cafb0f72622aadca7054dd58214a127a4ea
|
|
|
unit-reports-spark3.0
|
1.04 MB |
sha256:72f06dd0f14fbc9de0458824a2cb82f0919902db0cdb3fc0790bd4716fb4b2ac
|
|
|
unit-reports-spark3.2
|
1.04 MB |
sha256:0b79197914e11a6fd628f536520238b77e4a7a47a8ac0db579c267e0d0cb51c1
|
|
|
unit-reports-spark3.2.0
|
1.11 MB |
sha256:c6cb76a1d951f79119e55e8123290d3f0eba46ee88c700392aa714604019d144
|
|
|
unit-reports-spark3.3
|
1.11 MB |
sha256:c4be04388c3187e2f0e1dcb3ba46c44d2ecd57d461645514df65970876ffc944
|
|
|
unit-reports-spark3.4
|
1.09 MB |
sha256:22b8ec1576d7ed80adf88427ddeb838feaee92d800baa207e43b0806766c382f
|
|
|
unit-reports-spark3.5
|
1.09 MB |
sha256:3cbe167efb0e38cae23279d3449132b161f4d99b02b093ce73a17560efdd1b2d
|
|
|
unit-reports-spark3.5-scala2.13
|
1.11 MB |
sha256:bec7633ec6c343ae2d9f0a69e959e865fbb7e4536676f161850c599fcfb0807e
|
|
|
unit-reports-spark4
|
1.04 MB |
sha256:9bc941c74654b0dd43536663af724f0306580d07cbdcd1bb3cbb85e5ce600a90
|
|
|
unit-reports-tez
|
1.1 MB |
sha256:56230c71090559798cd93931c6f90fa123c9b1178299d70a42c8335f5079b2cf
|
|
|
unit-reports-tez-hadoop3.2
|
1.05 MB |
sha256:97609a82d2758a90d1ece9cc51535cfab6229f19cf3fac2245382caefb127d87
|
|