[WIP] Informer pools #6738
csviripr.yml
on: pull_request
check_format_and_unit_tests
19s
helm_unit_tests
10s
Matrix: build / httpclient-tests
Matrix: build / integration_tests
Matrix: build / special_integration_tests
Annotations
36 errors and 45 warnings
|
check_format_and_unit_tests
Process completed with exit code 1.
|
|
build / Special integration tests (21)
Process completed with exit code 1.
|
|
build / Special integration tests (17)
The strategy configuration was canceled because "build.special_integration_tests._21" failed
|
|
build / Special integration tests (17)
Process completed with exit code 1.
|
|
build / Special integration tests (25)
The strategy configuration was canceled because "build.special_integration_tests._21" failed
|
|
build / Special integration tests (25)
Process completed with exit code 1.
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
The operation was canceled.
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
The operation was canceled.
|
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (21, v1.32.13) / Integration tests (21, v1.32.13, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (21, v1.32.13) / Integration tests (21, v1.32.13, vertx)
The operation was canceled.
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
The job has exceeded the maximum execution time of 40m0s
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
The operation was canceled.
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
The job has exceeded the maximum execution time of 40m0s
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
The operation was canceled.
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
The job has exceeded the maximum execution time of 40m0s
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
Adding --force flag to minikube start because Kubernetes version v1.33.9 is not in Minikube's default supported list
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
Kubernetes version v1.33.9 is not in Minikube's supported list
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
Adding --force flag to minikube start because Kubernetes version v1.34.5 is not in Minikube's default supported list
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
Kubernetes version v1.34.5 is not in Minikube's supported list
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
Adding --force flag to minikube start because Kubernetes version v1.34.5 is not in Minikube's default supported list
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
Kubernetes version v1.34.5 is not in Minikube's supported list
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
Adding --force flag to minikube start because Kubernetes version v1.33.9 is not in Minikube's default supported list
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
Kubernetes version v1.33.9 is not in Minikube's supported list
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
Adding --force flag to minikube start because Kubernetes version v1.33.9 is not in Minikube's default supported list
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
Kubernetes version v1.33.9 is not in Minikube's supported list
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
Adding --force flag to minikube start because Kubernetes version v1.32.13 is not in Minikube's default supported list
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
Kubernetes version v1.32.13 is not in Minikube's supported list
|
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / integration_tests (21, v1.32.13) / Integration tests (21, v1.32.13, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (21, v1.32.13) / Integration tests (21, v1.32.13, vertx)
Adding --force flag to minikube start because Kubernetes version v1.32.13 is not in Minikube's default supported list
|
|
build / integration_tests (21, v1.32.13) / Integration tests (21, v1.32.13, vertx)
Kubernetes version v1.32.13 is not in Minikube's supported list
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
Adding --force flag to minikube start because Kubernetes version v1.35.2 is not in Minikube's default supported list
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
Kubernetes version v1.35.2 is not in Minikube's supported list
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
Adding --force flag to minikube start because Kubernetes version v1.34.5 is not in Minikube's default supported list
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
Kubernetes version v1.34.5 is not in Minikube's supported list
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@v2.16.1. 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/
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
Adding --force flag to minikube start because Kubernetes version v1.32.13 is not in Minikube's default supported list
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
Kubernetes version v1.32.13 is not in Minikube's supported list
|