oxidecomputer / oxidecomputer/buildomat
Feature Request: Tracking sub-task timing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Context: https://github.com/oxidecomputer/omicron/issues/4471#issuecomment-1802579053
It would be reasonably low cost for me to let you expose sub-task timing information in buildomat at this point. Would that be helpful?
I want to buy! I'd be stoked to integrate this feature into Omicron, and then we could start making a CI speed dashboard to track optimizations.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reading the linked Omicron discussion, then trace how buildomat represents and reports build tasks; done means exposing sub-task timing in a form Omicron can integrate for a CI speed dashboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100