next (5.3 do not merge) #6379
csviripr.yml
on: pull_request
check_format_and_unit_tests
23s
Matrix: build / httpclient-tests
Matrix: build / integration_tests
Matrix: build / special_integration_tests
Annotations
55 errors and 15 warnings
|
build / httpclient-tests (vertx) / Integration tests (25, v1.35.2, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
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)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
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)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / httpclient-tests (jdk) / Integration tests (25, v1.35.2, jdk)
The operation was canceled.
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (21, v1.35.2) / Integration tests (21, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (17, v1.32.13) / Integration tests (17, v1.32.13, vertx)
The operation was canceled.
|
|
build / httpclient-tests (jetty) / Integration tests (25, v1.35.2, jetty)
The operation was canceled.
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (17, v1.35.2) / Integration tests (17, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (25, v1.34.5) / Integration tests (25, v1.34.5, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (17, v1.34.5) / Integration tests (17, v1.34.5, vertx)
The operation was canceled.
|
|
check_format_and_unit_tests
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
check_format_and_unit_tests
The operation was canceled.
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (25, v1.35.2) / Integration tests (25, v1.35.2, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.32.13) / Integration tests (25, v1.32.13, vertx)
The operation was canceled.
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (21, v1.34.5) / Integration tests (21, v1.34.5, vertx)
The operation was canceled.
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (17, v1.33.9) / Integration tests (17, v1.33.9, vertx)
The operation was canceled.
|
|
build / integration_tests (25, v1.33.9) / Integration tests (25, v1.33.9, vertx)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
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)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / integration_tests (21, v1.33.9) / Integration tests (21, v1.33.9, vertx)
The operation was canceled.
|
|
build / Special integration tests (17)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / Special integration tests (17)
The operation was canceled.
|
|
build / Special integration tests (25)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / Special integration tests (25)
The operation was canceled.
|
|
build / Special integration tests (21)
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
build / Special integration tests (21)
The operation was canceled.
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
Verify Pull Request
Canceling since a higher priority waiting request for refs/pull/3074/merge-Verify Pull Request exists
|
|
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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)
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. 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/
|