The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

[stdout] Network's state test === RUN TestNetworkStatus nw_test.go:132: time: 2024-06-24T13:59:37.882341952Z out: networks: '[n1]' expected state: '-' secs: 600 time: 2024-06-24T13:59:37.893730679Z out: netName n1 state changed to ACTIVATED nw_test.go:157: ASSERTION FAILED (2024-06-24T14:09:37.89439898Z): expected networks [n1] in - state nw_test.go:159: actual n1: ACTIVATED nw_test.go:161: history of states for n1: nw_test.go:163: state: no info from controller received in: 2024-06-24T13:59:37.882372712Z nw_test.go:163: state: ACTIVATED received in: 2024-06-24T13:59:37.89372733Z testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 10m0s --- FAIL: TestNetworkStatus (601.01s) FAIL [exit status 1] FAIL: ../network/testdata/network_test.txt:26: command failure

Process completed with exit code 1.

Process completed with exit code 130.

A task was canceled.