[test-triage] otbn_stress_all_with_rand_reset is flaky
@rswarbrick is already working on this.
Since Apr 22, 2024.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Hierarchy of regression failure
Block level
### Failure Description
DV report: https://reports.opentitan.org/hw/ip/otbn/dv/uvm/latest/report.html
```
UVM_ERROR (cip_base_vseq.sv:830) [otbn_common_vseq] Check failed (!has_outstanding_access()) Waited * cycles to issue a reset with no outstanding accesses. has 2 failures:
Test otbn_stress_all_with_rand_reset has 2 failures.
0.otbn_stress_all_with_rand_reset.104907153325211843464581083247314622963277057383913080883219845442687497919404
Line 442, in log /container/opentitan-public/scratch/os_regression/otbn-sim-xcelium/0.otbn_stress_all_with_rand_reset/latest/run.log
UVM_ERROR @ 3622247063 ps: (cip_base_vseq.sv:830) [uvm_test_top.env.virtual_sequencer.otbn_common_vseq] Check failed (!has_outstanding_access()) Waited 10000 cycles to issue a reset with no outstanding accesses.
UVM_INFO @ 3622247063 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
6.otbn_stress_all_with_rand_reset.8687027932647823061256316391027474130934709492245935392526277250887041940037
Line 418, in log /container/opentitan-public/scratch/os_regression/otbn-sim-xcelium/6.otbn_stress_all_with_rand_reset/latest/run.log
UVM_ERROR @ 10178581868 ps: (cip_base_vseq.sv:830) [uvm_test_top.env.virtual_sequencer.otbn_common_vseq] Check failed (!has_outstanding_access()) Waited 10000 cycles to issue a reset with no outstanding accesses.
UVM_INFO @ 10178581868 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
```
### Steps to Reproduce
- GitHub Revision: [4fd94db59a](https://github.com/lowrisc/opentitan/tree/4fd94db59a656b28be60db223f1698d5b397904a)
- dvsim random seem: --build-seed 89274329416853274976097168471417145417282051311181377329444669936981619711436
### Tests with similar or related failures
_No response_
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.
Assessment
This issue has not been assessed yet.