Skip to content

[v0.23] change approach for checking existing vclusters in an ns #4532

[v0.23] change approach for checking existing vclusters in an ns

[v0.23] change approach for checking existing vclusters in an ns #4532

Re-run triggered February 24, 2025 15:18
Status Success
Total duration 8m 30s
Artifacts 4

e2e.yaml

on: pull_request
build-and-push-syncer-image
4m 6s
build-and-push-syncer-image
build-vcluster-cli
3m 55s
build-vcluster-cli
get-testsuites-dir
8s
get-testsuites-dir
Build e2e binaries
4m 2s
Build e2e binaries
Execute test suites
5s
Execute test suites
Install and delete virtual cluster
1m 49s
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

4 warnings
build-and-push-syncer-image
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.23.2-a503360e591c24e59190746a70c48826c96fb51039bad4547e21adba1f6ce492
build-and-push-syncer-image
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
build-and-push-syncer-image
You are using 'latest' as default version. Will lock to '~> v2'.
build-vcluster-cli
Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.23.2-a503360e591c24e59190746a70c48826c96fb51039bad4547e21adba1f6ce492