Skip to content

build(deps): bump third_party/abseil-cpp from e64dd62 to 67d1260 #2108

build(deps): bump third_party/abseil-cpp from e64dd62 to 67d1260

build(deps): bump third_party/abseil-cpp from e64dd62 to 67d1260 #2108

Triggered via pull request September 7, 2024 13:27
Status Failure
Total duration 15m 2s
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 / Tests
The self-hosted runner: gh-actions-prjxray-runner_3 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_17 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_45 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_36 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_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.