Skip to content

build(deps): bump third_party/googletest from 4b21f1a to 1204d63 #2210

build(deps): bump third_party/googletest from 4b21f1a to 1204d63

build(deps): bump third_party/googletest from 4b21f1a to 1204d63 #2210

Triggered via pull request November 2, 2024 13:55
Status Failure
Total duration 15m 4s
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_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 (kintex7)
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 (zynq7)
The self-hosted runner: gh-actions-prjxray-runner_21 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_23 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_52 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.