Skip to content
Automerge

[BOT] Conda Lock Update #4032

Sign in to view logs

[BOT] Conda Lock Update

[BOT] Conda Lock Update #4032

Triggered via push July 21, 2024 03:18
@tmichalaktmichalak
pushed 9324fdf
bot-conda-lock-update
Status Failure
Total duration 15m 4s
Artifacts –

Automerge.yml

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

Annotations

11 errors
Pipeline / Install | ql
The self-hosted runner: gh-actions-arch-defs-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 / docs
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 / Install | xc7
The self-hosted runner: gh-actions-arch-defs-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 / testarch
The self-hosted runner: gh-actions-arch-defs-runner_14 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_27 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_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.
Pipeline / tests
The self-hosted runner: gh-actions-arch-defs-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 / xc7
The self-hosted runner: gh-actions-arch-defs-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 / xc7a200t
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 / xc7a200t-vendor
The self-hosted runner: gh-actions-arch-defs-runner_25 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_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.