Skip to content

allow specifying privilege modes for simulation #103

allow specifying privilege modes for simulation

allow specifying privilege modes for simulation #103

Re-run triggered July 24, 2024 11:55
Status Failure
Total duration 16m 29s
Artifacts

run-tests.yml

on: pull_request
generate-config
6s
generate-config
build-spike  /  Build Spike
8m 8s
build-spike / Build Spike
Matrix: generate-code
Matrix: run-tests
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 1 warning
generate-code (riscv_full_interrupt_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_loop_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_ebreak_debug_mode_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_arithmetic_basic_test, pyflow)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_arithmetic_basic_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_illegal_instr_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_16 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.
generate-code (riscv_ebreak_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_hint_instr_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_48 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.
generate-code (riscv_jump_stress_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_mmu_stress_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_no_fence_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_rand_instr_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_rand_jump_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_37 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.
generate-code (riscv_pmp_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_unaligned_load_store_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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.
generate-code (riscv_non_compressed_instr_test, uvm)
The self-hosted runner: gha-runner-coordinator-riscv-dv_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-spike / Build Spike
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/