oxidecomputer / oxidecomputer/propolis
Consider adding PHD runs with release propolis-server to CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
PHD runs in CI test using a debug propolis-server for its (theoretically) better debuggability when tests fail. By default, however, Omicron uses release builds of propolis-server, which can behave differently in surprising ways; see e.g. #292.
We should consider adding some kind of CI run that checks that release builds of the server pass our integration tests.
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
Review the existing PHD CI configuration and how it selects debug propolis-server builds, then compare that with Omicron's default release-server path and issue #292. Done means CI runs the integration tests against a release propolis-server build and reports failures clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100