oxidecomputer / oxidecomputer/quartz
CI: mark bitfile targets which fail to meet timing as failed
Open
Nobody has claimed this yet.
CI
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
For the OSS toolchain flow, we get a report.txt which will end up with a line along the lines of:
Info: Max frequency for clock '$glbnet$clk_50m_fpga$TRELLIS_IO_IN': 42.99 MHz (FAIL at 50.00 MHz)
Seems pretty simple to add some logic to a build step that looks for the FAIL and can take action off that.
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
Locate the OSS toolchain build step that produces or consumes report.txt, then inspect how build success is currently determined. Make timing lines containing FAIL affect the bitfile target result, and verify that a report with a failed timing requirement causes CI to mark the target failed.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100