Skip to content

NO MERGE: testing CI worked #3

NO MERGE: testing CI worked

NO MERGE: testing CI worked #3

Triggered via pull request September 28, 2023 16:38
Status Cancelled
Total duration 46m 59s
Artifacts
Matrix: SOLO SHiELD build
Matrix: SOLO SHiELD test suite
Matrix: Shutdown Processes
Fit to window
Zoom out
Zoom in

Annotations

27 errors
Shutdown Processes (C96.solo.BCmoist)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.solo.mtn_rest.hyd.diff2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.sw.BTwave)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_1k.solo.mtn_rest_shear)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.sw.RHwave)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_1k.solo.mtn_rest_shear.olddamp)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_1k.solo.mtn_schar.mono)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_2k.solo.bubble)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_2k.solo.bubble.nhK)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_1k.solo.mtn_schar)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (d96_2k.solo.bubble.n0)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.solo.mtn_rest.nonmono.diff2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.solo.mtn_rest.nonmono.diff2)
The operation was canceled.
Shutdown Processes (C96.solo.mtn_rest.hyd)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.solo.mtn_rest.hyd)
The operation was canceled.
Shutdown Processes (C96.sw.BLvortex)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.sw.BLvortex)
The operation was canceled.
Shutdown Processes (C96.sw.modon)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.sw.modon)
The operation was canceled.
Shutdown Processes (C96.solo.mtn_rest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Shutdown Processes (C96.solo.mtn_rest)
The operation was canceled.