The self-hosted runner: gha-runner-coordinator-conda-eda_9 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.

Build / prjtrellis-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_15 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.

Build / vtr-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / verilator-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / prjoxide-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_33 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.

Build / yosys-linux-py38

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / magic-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_54 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.

Build / yosys-linux-py310

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / prjxray-tools-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / prjxray-db-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / icarus-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / yosys-linux-py37

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / verible-linux

Process completed with exit code 1.

Build / openroad-osx

Process completed with exit code 1.

Build / nextpnr-generic-osx

Process completed with exit code 1.

Build / yosys-osx

Process completed with exit code 1.

Build / nextpnr-fpga_interchange-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / klayout-linux-py310

The self-hosted runner: gha-runner-coordinator-conda-eda_31 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.

Build / klayout-linux-py311

The self-hosted runner: gha-runner-coordinator-conda-eda_42 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.

Build / klayout-linux-py312

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / klayout-linux-py37

The self-hosted runner: gha-runner-coordinator-conda-eda_63 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.

Build / klayout-linux-py38

The self-hosted runner: gha-runner-coordinator-conda-eda_26 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.

Build / moore-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_20 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.

Build / libunwind

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / netgen-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / nextpnr-generic-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_57 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.

Build / ngspice-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / nextpnr-xilinx-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_35 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.

Build / odin-ii-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / openroad-linux-py37

The self-hosted runner: gha-runner-coordinator-conda-eda_46 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.

Build / openroad-linux-py310

The self-hosted runner: gha-runner-coordinator-conda-eda_32 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.

Build / openroad-linux-py38

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / sv-parser-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_6 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.

Build / tcllib-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / tree-sitter-verilog-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_7 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.

Build / vtr-gui-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / vtr-optimized-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_0 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.

Build / xilinx-vivado-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_40 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.

Build / xschem-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_50 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.

Build / xls-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_59 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.

Build / zachjs-sv2v-linux

The self-hosted runner: gha-runner-coordinator-conda-eda_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.

Build / prjtrellis-osx

Process completed with exit code 1.

Build / verilator-osx

Process completed with exit code 1.

Build / klayout-osx

Process completed with exit code 1.

Upload

Process completed with exit code 1.

Build / icarus-windows

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build / icestorm-windows