Skip to content

test: reset ExternalIDGenServiceMock between tests to fix flaky external-state ITs #6795

test: reset ExternalIDGenServiceMock between tests to fix flaky external-state ITs

test: reset ExternalIDGenServiceMock between tests to fix flaky external-state ITs #6795

Triggered via pull request May 28, 2026 09:36
Status Failure
Total duration 28m 28s
Artifacts

pr.yml

on: pull_request
check_format_and_unit_tests
25s
check_format_and_unit_tests
helm_unit_tests
12s
helm_unit_tests
Matrix: build / httpclient-tests
Matrix: build / integration_tests
Matrix: build / special_integration_tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 30 warnings
check_format_and_unit_tests
Process completed with exit code 1.
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 / 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.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 (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 (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.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 / 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 / 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.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.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 / 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.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 (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.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 (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