[prim] Reach coverage metrics for V3
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
For most smaller primitives in the `prim_*` library, we collect coverage as part of the comportable IP block-level DV. However, a few larger prims have their own DV environment, and hence they are excluded from coverage collection in the comportable IP block-level DV environments.
In order to reach V3 for the entire top-level, we should make sure that the coverage of these primitives reaches 100% (with waivers).
The affected primitives are:
- [ ] #14845
- [ ] #14846
- [ ] #14847
- [ ] #14848
- [ ] #14849
The coverage can be found in the nightly regression dashboard [here](https://reports.opentitan.org/hw/top_earlgrey/dv/summary/latest/report.html).
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 with the nightly regression dashboard and the five affected primitive issues: #14845 through #14849. Review each primitive's coverage status and its linked work, then consider the task complete when all listed primitives reach 100% coverage with documented waivers where needed.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100