Skip to content

fix: delete k8s jobs after failure (important in setups where the system attaches sidecar pods, which can otherwise remain after failure) #163

fix: delete k8s jobs after failure (important in setups where the system attaches sidecar pods, which can otherwise remain after failure)

fix: delete k8s jobs after failure (important in setups where the system attaches sidecar pods, which can otherwise remain after failure) #163

Triggered via pull request June 13, 2025 09:57
Status Failure
Total duration 3m 46s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
linting
Process completed with exit code 1.
testing
Failed to save: reserveCache failed: Cache service responded with 503
testing
Failed to save: reserveCache failed: Cache service responded with 503
testing
Failed to restore: getCacheEntry failed: Cache service responded with 503
testing
Failed to restore: getCacheEntry failed: Cache service responded with 503
testing
Failed to restore: getCacheEntry failed: Cache service responded with 503