PostCommit Python #1828
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
8 errors
beam_PostCommit_Python (Run Python PostCommit 3.11)
Process completed with exit code 1.
|
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 operation was canceled.
|
beam_PostCommit_Python (Run Python PostCommit 3.10)
The self-hosted runner: main-runner-x5s5p-4n5dm 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-kxk8g 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-qr8w4 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.
|