oxidecomputer / oxidecomputer/transceiver-control
`xcvradm` should deliver test status messages
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 0
- Avg merge
- 57m
- Merged PRs (30d)
- 3
Description
Related to https://github.com/oxidecomputer/hubris/issues/1783
When we are using Medusa to test Front IO boards, it would be nice to be able to tell the LEDs what color to be over the network (as that is how the test will be administered). We should noodle on what those statuses would be and what the appropriate colors would be. Some initial thoughts:
- "no test running" = LEDs off
- "test running" = blue
- "test pass" = green
- "test fail" = red
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
Start by examining the xcvradm entry point and the related Hubris issue 1783 to understand how Medusa administers Front IO board tests over the network. Define the test statuses and LED colors, then determine how those status messages should be delivered; done means the agreed statuses and colors are supported end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, embedded-iot, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100