Skip to content

Properly handle "proxy server not fully initialized" scenario #486

Properly handle "proxy server not fully initialized" scenario

Properly handle "proxy server not fully initialized" scenario #486

Triggered via pull request April 5, 2024 19:55
Status Cancelled
Total duration 7m 52s
Artifacts

test.yaml

on: pull_request
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
build-and-test (28.1, v1.25.6)
The run was canceled by @jinnovation.
build-and-test (28.1, v1.26.1)
The run was canceled by @jinnovation.
build-and-test (29.3, v1.26.1)
The run was canceled by @jinnovation.
build-and-test (29.3, v1.23.12)
The run was canceled by @jinnovation.
build-and-test (snapshot, true)
The run was canceled by @jinnovation.
build-and-test (29.3, v1.24.10)
The run was canceled by @jinnovation.
build-and-test (29.3, v1.25.6)
The run was canceled by @jinnovation.
build-and-test (28.1, v1.24.10)
The run was canceled by @jinnovation.
build-and-test (28.1, v1.24.10)
The operation was canceled.
build-and-test (28.1, v1.23.12)
The run was canceled by @jinnovation.
build-and-test (28.1, v1.23.12)
The operation was canceled.
build-and-test (28.1, v1.24.10)
Attempt 1 failed. Reason: Timeout of 180000ms hit
build-and-test (28.1, v1.23.12)
Attempt 1 failed. Reason: Timeout of 180000ms hit