[SPARK-53471] Correct entrypoint.sh for Openshift #8
ReamerAnnotations
12 errors and 8 warnings
|
Run (all, 11) / main
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$680/0x0000000800710040@54bd04d2 rejected from java.util.concurrent.ThreadPoolExecutor@5ba12d58[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 415]
|
|
Run (all, 11) / main
sleep interrupted
|
|
Run (all, 11) / main
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$680/0x0000000800710040@4b4478f rejected from java.util.concurrent.ThreadPoolExecutor@5ba12d58[Shutting down, pool size = 4, active threads = 2, queued tasks = 0, completed tasks = 414]
|
|
Run (all, 11) / main
sleep interrupted
|
|
Run (all, 11) / main
Set() did not contain "decomtest-ef8e709d059290da-exec-1".
|
|
Run (all, 11) / main
Set() did not contain "decomtest-e17f009d0591af5a-exec-1".
|
|
Run (all, 17) / main
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$703/0x00007f72e45b1428@21d47860 rejected from java.util.concurrent.ThreadPoolExecutor@73e47645[Shutting down, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 411]
|
|
Run (all, 17) / main
Task io.fabric8.kubernetes.client.utils.internal.SerialExecutor$$Lambda$703/0x00007f72e45b1428@6e85603 rejected from java.util.concurrent.ThreadPoolExecutor@73e47645[Shutting down, pool size = 2, active threads = 1, queued tasks = 0, completed tasks = 412]
|
|
Run (all, 17) / main
sleep interrupted
|
|
Run (all, 17) / main
sleep interrupted
|
|
Run (all, 17) / main
Set() did not contain "decomtest-6f152c9d059a984b-exec-1".
|
|
Run (all, 17) / main
Set() did not contain "decomtest-6e880d9d0599b0f0-exec-1".
|
|
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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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, 17) / main
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, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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
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, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/cache@v3, actions/checkout@v3, actions/setup-java@v3, docker/build-push-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v3, medyagh/setup-minikube@v0.0.20. 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/
|