Skip to content

Fix panic when using exportKubeConfig.name without exportKubeConfig.server #4299

Fix panic when using exportKubeConfig.name without exportKubeConfig.server

Fix panic when using exportKubeConfig.name without exportKubeConfig.server #4299

Triggered via pull request January 20, 2025 13:54
Status Cancelled
Total duration 1m 25s
Artifacts 1

e2e.yaml

on: pull_request
build-and-push-syncer-image
1m 14s
build-and-push-syncer-image
build-vcluster-cli
1m 13s
build-vcluster-cli
get-testsuites-dir
8s
get-testsuites-dir
Build e2e binaries
1m 13s
Build e2e binaries
Execute test suites
4s
Execute test suites
Install and delete virtual cluster
0s
Install and delete virtual cluster
Matrix: Execute test suites
Matrix: test if we can upgrade from older version
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 3 warnings
build-and-push-syncer-image
Canceling since a higher priority waiting request for 'E2E CI-2416' exists
build-and-push-syncer-image
The operation was canceled.
build-vcluster-cli
Canceling since a higher priority waiting request for 'E2E CI-2416' exists
build-vcluster-cli
The operation was canceled.
Build e2e binaries
Canceling since a higher priority waiting request for 'E2E CI-2416' exists
Build e2e binaries
The operation was canceled.
Execute test suites
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
get-testsuites-dir
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-and-push-syncer-image
You are using 'latest' as default version. Will lock to '~> v2'.

Artifacts

Produced during runtime
Name Size
vcluster-current
20.6 MB