Avoid breakage when `earlgrey_1.0.0` is updated
Open
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 1
- Forks
- 7
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
Twice now in the span of a couple of weeks, the repository has been broken due to changes in the earlgrey_1.0.0 branch. Should we add a CI step in the opentitan repository to make sure that it doesn't completely break ot-sku? Potential elemtns to tests:
- make sure the perso and rom_ext compile (easy)
- run the FPGA manufacturing flows (easyish?)
- test the release flow (hard)
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 examining how the opentitan repository can validate ot-sku changes from the earlgrey_1.0.0 branch. Check the perso and rom_ext compilation first, then investigate the FPGA manufacturing and release flows. Done means the CI coverage and its required checks are defined so branch updates cannot silently break ot-sku.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100