PostCommit Python #1819
damccorm
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
beam_PostCommit_Python.yml
on: schedule
Matrix: beam_PostCommit_Python
Annotations
7 errors
|
beam_PostCommit_Python (Run Python PostCommit 3.11)
The self-hosted runner: main-runner-x5s5p-lsxlt 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-dcmgm 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-nlbdm 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-j9lht 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.
|