Skip to content
Lint

Add pod disruption budget #122

Sign in to view logs

Add pod disruption budget

Add pod disruption budget #122

Triggered via pull request January 29, 2025 15:49
@TrayserCassaTrayserCassa
synchronize #80
add-pod-disruption-budget
Status Failure
Total duration 3m 39s
Artifacts –

lint.yaml

on: pull_request
golangci
2m 31s
golangci
go test
2m 59s
go test
helm lint
1m 4s
helm lint
Cluster E2E Test
2m 29s
Cluster E2E Test
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 4 notices
go test
Process completed with exit code 1.
go test
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.321.0. Please update to the latest version 2.322.0
helm lint
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
Cluster E2E Test
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
golangci
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.
go test
Magic cache for RunsOn is ON. Cache entries will be transparently stored on the local S3 bucket. Don't forget to use runs-on/action@v1 as the first step of your workflow.