Skip to content

Automerge

Automerge #2153

Triggered via schedule October 3, 2024 01:18
Status Failure
Total duration 10m 5s
Artifacts

Automerge.yml

on: schedule
Matrix: Pipeline / BuildDatabase
Pipeline  /  Tests
0s
Pipeline / Tests
Automerge dependabot PRs
0s
Automerge dependabot PRs
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Pipeline / BuildDatabase (kintex7)
The self-hosted runner: gh-actions-prjxray-runner_9 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.
Pipeline / BuildDatabase (spartan7)
The self-hosted runner: gh-actions-prjxray-runner_1 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.
Pipeline / Tests
The self-hosted runner: gh-actions-prjxray-runner_2 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.
Pipeline / BuildDatabase (zynq7)
The self-hosted runner: gh-actions-prjxray-runner_11 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.
Pipeline / BuildDatabase (artix7)
The self-hosted runner: gh-actions-prjxray-runner_51 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.