Skip to content
Automerge

[BOT] Conda Lock Update #4260

Sign in to view logs

[BOT] Conda Lock Update

[BOT] Conda Lock Update #4260

Triggered via pull request October 2, 2024 03:24
@tmichalaktmichalak
synchronize #2927
bot-conda-lock-update
Status Failure
Total duration 15m 4s
Artifacts –

Automerge.yml

on: pull_request
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 / testarch
The self-hosted runner: gh-actions-arch-defs-runner_5 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_1 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_10 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_8 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_19 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_53 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_22 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_18 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_58 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_39 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_41 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.