Skip to content
checks

feat(preflight): Storage container checks for Nutanix #3739

Sign in to view logs

feat(preflight): Storage container checks for Nutanix

feat(preflight): Storage container checks for Nutanix #3739

Triggered via pull request June 6, 2025 19:09
@dlipovetskydlipovetsky
synchronize #1136
jira/NCN-105203
Status Success
Total duration 34m 58s
Artifacts –

checks.yml

on: pull_request
Matrix: lint-go
unit-test
7m 6s
unit-test
lint-gha
9s
lint-gha
pre-commit
3m 1s
pre-commit
lint-test-helm
7m 56s
lint-test-helm
Matrix: e2e-quick-start
Matrix: e2e-self-hosted
Fit to window
Zoom out
Zoom in

Annotations

29 warnings
lint-go (common)
Failed to restore: getCacheEntry failed: Cache service responded with 503
lint-go (common)
Failed to save: reserveCache failed: Cache service responded with 503
lint-go (common)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
lint-go (.)
Failed to restore: getCacheEntry failed: Cache service responded with 503
lint-go (.)
Failed to save: reserveCache failed: Cache service responded with 503
lint-go (.)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
lint-go (api)
Failed to restore: getCacheEntry failed: Cache service responded with 503
lint-go (api)
Failed to save: reserveCache failed: Cache service responded with 503
lint-go (api)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
pre-commit
Failed to restore: getCacheEntry failed: Cache service responded with 503
pre-commit
Failed to save: reserveCache failed: Cache service responded with 503
unit-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
unit-test
Failed to save: reserveCache failed: Cache service responded with 503
lint-test-helm
Failed to restore: getCacheEntry failed: Cache service responded with 503
lint-test-helm
Failed to save: reserveCache failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.31) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.31) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.32) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.32) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.33) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.33) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.30) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-quick-start (Docker provider, Kubernetes v1.30) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.32) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.32) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.31) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.31) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.33) / e2e-test
Failed to restore: getCacheEntry failed: Cache service responded with 503
e2e-self-hosted (Docker provider, Kubernetes v1.33) / e2e-test
Failed to save: reserveCache failed: Cache service responded with 503