Skip to content

build(deps): bump third_party/litex from 95b310e to 34b98ab #4276

build(deps): bump third_party/litex from 95b310e to 34b98ab

build(deps): bump third_party/litex from 95b310e to 34b98ab #4276

Triggered via pull request October 9, 2024 06:07
Status Failure
Total duration 10m 5s
Artifacts

Automerge.yml

on: pull_request
Matrix: Pipeline / Install
Matrix: Pipeline / Test
Automerge dependabot PRs
0s
Automerge dependabot PRs
Fit to window
Zoom out
Zoom in

Annotations

11 errors
Pipeline / Install | xc7
The self-hosted runner: gh-actions-arch-defs-runner_4 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 / xc7a200t-vendor
The self-hosted runner: gh-actions-arch-defs-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 / Install | ql
The self-hosted runner: gh-actions-arch-defs-runner_29 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 / ice40
The self-hosted runner: gh-actions-arch-defs-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.
Pipeline / xc7a200t
The self-hosted runner: gh-actions-arch-defs-runner_24 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 / xc7-vendor
The self-hosted runner: gh-actions-arch-defs-runner_38 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-arch-defs-runner_44 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 / testarch
The self-hosted runner: gh-actions-arch-defs-runner_60 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 / ql
The self-hosted runner: gh-actions-arch-defs-runner_56 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 / xc7
The self-hosted runner: gh-actions-arch-defs-runner_62 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 / docs
The self-hosted runner: gh-actions-arch-defs-runner_55 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.