dv_report_catcher
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
file dv_report_catcher in directory /opentitan/hw/dv/sv/dv_utils/dv_report_catcher.sv
uvm_re_match return 0 for successful match, I think the code should be changed from
if (uvm_re_match(msg, report_msg)) begin --> if (!uvm_re_match(msg, report_msg)) begin
// Called for all report messages - defined in uvm_report_catcher
virtual function action_e catch();
string id = get_id();
if (m_changed_sev.exists(id)) begin
string report_msg = get_message();
foreach (m_changed_sev[id, msg]) begin
if (uvm_re_match(msg, report_msg)) begin
set_severity(m_changed_sev[id][msg]);
end
end
end
return THROW;
endfunction
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
Open /opentitan/hw/dv/sv/dv_utils/dv_report_catcher.sv and inspect the catch() function's uvm_re_match condition. Confirm the documented return convention for a successful match, then verify that matching report messages receive the configured severity and that non-matches do not.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100