oxidecomputer / oxidecomputer/omicron
want regular automated testing of upgrade from previous commit to "main"
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This is very similar to #9989 and is presumably blocked on the same stuff.
This test essentially covers upgrading "from" the tip of main -- thought it would need to go one commit back in order to have something to upgrade to.
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 by reading the related issue #9989, since this issue says it shares the same blockers. Then identify the existing upgrade-test entry point and how to exercise an upgrade from the previous commit to main. Done means regular automation covers that upgrade path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100