Skip to content

build(deps): bump third_party/abseil-cpp from c6b2735 to 917bfee #2245

build(deps): bump third_party/abseil-cpp from c6b2735 to 917bfee

build(deps): bump third_party/abseil-cpp from c6b2735 to 917bfee #2245

Triggered via pull request November 16, 2024 13:54
Status Failure
Total duration 14m 59s
Artifacts

Automerge.yml

on: pull_request
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 (spartan7)
The self-hosted runner: gh-actions-prjxray-runner_28 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_48 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 (kintex7)
The self-hosted runner: gh-actions-prjxray-runner_47 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_20 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_49 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.