Skip to content

raspi-2

raspi-2 #213

Triggered via schedule September 20, 2023 04:10
Status Failure
Total duration 1d 6h 14m 40s
Artifacts

raspi-2.yaml

on: schedule
raspi-2-modular  /  initialize
3m 1s
raspi-2-modular / initialize
raspi-2-skia  /  initialize
36s
raspi-2-skia / initialize
raspi-2  /  initialize
39s
raspi-2 / initialize
raspi-2-modular  /  docker-build-image
0s
raspi-2-modular / docker-build-image
raspi-2-modular  /  docker-unittest-image
0s
raspi-2-modular / docker-unittest-image
raspi-2-skia  /  docker-build-image
0s
raspi-2-skia / docker-build-image
raspi-2-skia  /  docker-unittest-image
0s
raspi-2-skia / docker-unittest-image
raspi-2  /  docker-build-image
0s
raspi-2 / docker-build-image
raspi-2  /  docker-unittest-image
0s
raspi-2 / docker-unittest-image
Matrix: raspi-2-modular / build
Matrix: raspi-2-skia / build
Matrix: raspi-2 / build
Matrix: raspi-2-modular / on-device-test
Matrix: raspi-2-modular / on-host-test
Matrix: raspi-2-skia / on-device-test
Matrix: raspi-2-skia / on-host-test
Matrix: raspi-2 / on-device-test
Matrix: raspi-2 / on-host-test
Fit to window
Zoom out
Zoom in

Annotations

3 errors
raspi-2 / docker-build-image
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
raspi-2-skia / docker-build-image
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
raspi-2-modular / docker-build-image
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.