oxidecomputer / oxidecomputer/propolis
we should smoketest propolis-standalone in CI
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
https://github.com/oxidecomputer/propolis/pull/1218 didn't need to happen and did happen because I happen to have a particular set of configs that I forgot is not fully expressive...
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 locating the propolis-standalone configuration and the repository's existing CI workflows. Trace how configurations are exercised and add a smoke test that exposes configurations the current setup cannot fully express; done means this class of regression is detected in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100