Skip to content
Verify Pull Request

feat: resource operation support multiple update modes #7063

Sign in to view logs

feat: resource operation support multiple update modes

feat: resource operation support multiple update modes #7063

Triggered via pull request July 14, 2026 07:15
@csviricsviri
synchronize #3491
csviri:kroxybug-extended-matchers
Status Cancelled
Total duration 40m 20s
Artifacts –

pr.yml

on: pull_request
check_format_and_unit_tests
2m 58s
check_format_and_unit_tests
helm_unit_tests
7s
helm_unit_tests
Matrix: build / httpclient-tests
Matrix: build / integration_tests
Matrix: build / special_integration_tests
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 30 warnings
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 (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 (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 (17, v1.33.9) / Integration tests (17, v1.33.9, 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 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 (21, v1.34.5) / Integration tests (21, v1.34.5, 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 / 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.35.2) / Integration tests (17, v1.35.2, 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 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 (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 (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 / 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 (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.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 / 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 (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 (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 (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 (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 (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 / 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.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.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)
Kubernetes version v1.35.2 is not in Minikube's supported list
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 (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
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 / 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)
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 (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.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