Skip to content
Integration tests

fix: Logs API stops functioning when a pod fails #36463

Sign in to view logs

fix: Logs API stops functioning when a pod fails

fix: Logs API stops functioning when a pod fails #36463

Triggered via pull request December 24, 2024 04:07
@Fluder-ParadyneFluder-Paradyne
synchronize #21287
Fluder-Paradyne:exclude-broken-pods
Status Failure
Total duration 38m 39s
Artifacts 3

ci-build.yaml

on: pull_request
changes
13s
changes
Build & cache Go code
3m 13s
Build & cache Go code
Build, test & lint UI code
1m 37s
Build, test & lint UI code
Ensure Go modules synchronicity
24s
Ensure Go modules synchronicity
Lint Go code
3m 10s
Lint Go code
Check changes to generated code
4m 31s
Check changes to generated code
Matrix: Run end-to-end tests
Run unit tests for Go packages
5m 20s
Run unit tests for Go packages
Run unit tests with -race for Go packages
9m 30s
Run unit tests with -race for Go packages
E2E Tests - Composite result
0s
E2E Tests - Composite result
Process & analyze test artifacts
0s
Process & analyze test artifacts
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Run end-to-end tests (v1.31.0, true)
Process completed with exit code 2.
E2E Tests - Composite result
Process completed with exit code 1.
changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
e2e-server-k8sv1.31.0.log
2.95 MB
race-results
1.29 MB
test-results
1.29 MB