[alert_handler,topgen] Render TOP_LOC_ALERTS
Open
Nobody has claimed this yet.
Component:Tooling
IP:alert_handler
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The build system uses a hard-coded list of alert_handler local alerts EARLGREY|DARJEELING_LOC_ALERTS
Hard-coding this list is not ideal. Instead, alert_handler should provide the necessary information to topgen, such that we can render this constant automatically.
cc @pamaury @vogelpi @andreaskurth
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 hard-coded EARLGREY|DARJEELING_LOC_ALERTS list in rules/const.bzl at the linked lines, then trace how alert_handler and topgen exchange information. The work is complete when topgen obtains the alert_handler local-alert information and renders TOP_LOC_ALERTS without that hard-coded list.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100