riscv_nested_interrupt_test case failed
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
I use the comand ```make TEST=riscv_nested_interrupt_test SEED=8037``` will have one case failed.
Due to random delay for load/store, 750 cycles for timeout sometimes is not enough. when I modify dv/uvm/core_ibex/tests/core_ibex_test_lib.sv line 247 to "check_next_core_status(HANDLING_IRQ, "Core did not jump to vectored interrupt handle", 760) ", then it will pass. The value of timeout may need a suitable value.
"Synopsys VCS 2020.03-SP1"
"Ubuntu Linux 18.04".
commit id: fd1195a1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running `make TEST=riscv_nested_interrupt_test SEED=8037` in the Ibex repository and inspect `dv/uvm/core_ibex/tests/core_ibex_test_lib.sv` around line 247. Reproduce the intermittent timeout with the reported VCS and Ubuntu versions, then verify the test passes reliably with an appropriate timeout value.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100