[SPARK-53471] Correct entrypoint.sh for Openshift #9
ReamerAnnotations
22 errors and 9 warnings
|
Run (python, 11) / main
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -ex; apt-get update; apt-get install -y python3 python3-pip; rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
|
|
Run (python, 17) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (python, 17) / main
The operation was canceled.
|
|
Run (all, 11) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (all, 11) / main
The operation was canceled.
|
|
Run (all, 17) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (all, 17) / main
The operation was canceled.
|
|
Run (r, 17) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (r, 17) / main
The operation was canceled.
|
|
Run (r, 11) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (r, 11) / main
The operation was canceled.
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (scala, 11) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Build and Test (3.5.6)
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (scala, 11) / main
The operation was canceled.
|
|
Run (scala, 17) / main
The strategy configuration was canceled because "run-build.python_11" failed
|
|
Run (scala, 17) / main
The operation was canceled.
|
|
Run (python, 11) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/upload-artifact@v4, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (python, 11) / main
No files were found with the provided path: **/target/integration-tests.log. No artifacts will be uploaded.
|
|
Run (python, 17) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (all, 11) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (all, 17) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (r, 17) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (r, 11) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (scala, 11) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run (scala, 17) / main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|