Skip to content
Scheduled Benchmark Tests on Self-hosted Runner

Scheduled Benchmark Tests on Self-hosted Runner #14460

Sign in to view logs

Scheduled Benchmark Tests on Self-hosted Runner

Scheduled Benchmark Tests on Self-hosted Runner #14460

Triggered via schedule November 21, 2024 10:17
@leecalcoteleecalcote
⁠ 4148317
master
Status Failure
Total duration 17m 27s
Artifacts –

scheduled-benchmarks-self-hosted.yaml

on: schedule
Matrix: Start self-hosted CNCF CIL runners for manual test
Matrix: Start self-hosted CNCF CIL runners for scheduled test
Matrix: Manual Benchmark Test
Matrix: Scheduled Benchmark Test
Matrix: Stop self-hosted runner
Matrix: Stop self-hosted runner
Fit to window
Zoom out
Zoom in

Annotations

26 errors
Start self-hosted CNCF CIL runners for scheduled test (istio, wrk2, load-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (istio, fortio, load-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (istio, fortio, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (linkerd, fortio, load-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (linkerd, wrk2, load-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (linkerd, fortio, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (istio, wrk2, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (linkerd, wrk2, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (osm, fortio, load-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (osm, fortio, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (osm, wrk2, soak-test)
Process completed with exit code 1.
Start self-hosted CNCF CIL runners for scheduled test (osm, wrk2, load-test)
Process completed with exit code 1.
Stop self-hosted runner (linkerd, fortio, load-test)
Process completed with exit code 1.
Stop self-hosted runner (osm, fortio, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (osm, wrk2, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (linkerd, wrk2, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (istio, fortio, load-test)
Process completed with exit code 1.
Stop self-hosted runner (osm, wrk2, load-test)
Process completed with exit code 1.
Stop self-hosted runner (istio, fortio, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (linkerd, fortio, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (linkerd, wrk2, load-test)
Process completed with exit code 1.
Stop self-hosted runner (istio, wrk2, load-test)
Process completed with exit code 1.
Stop self-hosted runner (osm, fortio, load-test)
Process completed with exit code 1.
Stop self-hosted runner (istio, wrk2, soak-test)
Process completed with exit code 1.
Stop self-hosted runner (istio, wrk2, soak-test)
unable to access 'https://github.com/layer5io/meshery-performance-action/': Failed to connect to github.com port 443 after 133846 ms: Connection timed out
Stop self-hosted runner (istio, wrk2, soak-test)
unable to access 'https://github.com/layer5io/meshery-performance-action/': Failed to connect to github.com port 443 after 133393 ms: Connection timed out