Skip to content
PostCommit Python

PostCommit Python #1815

Sign in to view logs

PostCommit Python

PostCommit Python #1815

Triggered via schedule October 14, 2023 00:15
@damccormdamccorm
⁠ f93f62e
master
Status Failure
Total duration 1h 33m 51s
Artifacts –

beam_PostCommit_Python.yml

on: schedule
Matrix: beam_PostCommit_Python
Fit to window
Zoom out
Zoom in

Annotations

7 errors
beam_PostCommit_Python (Run Python PostCommit 3.11)
The self-hosted runner: main-runner-x5s5p-shz6j lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
beam_PostCommit_Python (Run Python PostCommit 3.10)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
beam_PostCommit_Python (Run Python PostCommit 3.10)
The self-hosted runner: main-runner-x5s5p-jfstn lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
beam_PostCommit_Python (Run Python PostCommit 3.9)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
beam_PostCommit_Python (Run Python PostCommit 3.9)
The self-hosted runner: main-runner-x5s5p-9zgwr lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
beam_PostCommit_Python (Run Python PostCommit 3.8)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
beam_PostCommit_Python (Run Python PostCommit 3.8)
The self-hosted runner: main-runner-x5s5p-xp6tp lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.