RPC tests on repeat #300
github-merge-queue[bot]Annotations
29 errors and 3 warnings
|
Calibnet RPC checks (10, 10)
Process completed with exit code 1.
|
|
Calibnet RPC checks (4, 8)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (4, 8)
Process completed with exit code 137.
|
|
Calibnet RPC checks (5, 5)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (5, 5)
Process completed with exit code 143.
|
|
Calibnet RPC checks (10, 2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (10, 2)
Process completed with exit code 137.
|
|
Calibnet RPC checks (2, 2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (2, 2)
Process completed with exit code 137.
|
|
Calibnet RPC checks (2, 6)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (2, 6)
Process completed with exit code 143.
|
|
Calibnet RPC checks (10, 3)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (10, 3)
Process completed with exit code 143.
|
|
Calibnet RPC checks (1, 6)
Process completed with exit code 1.
|
|
Calibnet RPC checks (10, 7)
Process completed with exit code 1.
|
|
Calibnet RPC checks (8, 2)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (8, 2)
Process completed with exit code 137.
|
|
Calibnet RPC checks (6, 7)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (6, 7)
Process completed with exit code 137.
|
|
Calibnet RPC checks (7, 1)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (7, 1)
Process completed with exit code 137.
|
|
Calibnet RPC checks (7, 10)
Process completed with exit code 1.
|
|
Calibnet RPC checks (6, 9)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Calibnet RPC checks (6, 9)
Process completed with exit code 137.
|
|
Calibnet RPC checks (2, 10)
Process completed with exit code 1.
|
|
Calibnet RPC checks (7, 5)
Process completed with exit code 1.
|
|
Calibnet RPC checks (6, 5)
Process completed with exit code 1.
|
|
Calibnet RPC checks (5, 2)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Calibnet RPC checks (5, 7)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Calibnet RPC checks (4, 5)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
Calibnet RPC checks (10, 4)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
Calibnet RPC checks (10, 1)
Received request to deprovision: The request was cancelled by the remote provider.
|