oxidecomputer / oxidecomputer/propolis
Remove setting `gpt_track_dirty` flag in test runner.
Open
Nobody has claimed this yet.
testing
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
#254 switches to the per-VM option but also leaves the old global while CI and local builds have the new bhyve bits. Left a TODO to allow some transition period.
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 issue #254 and the test runner references to the gpt_track_dirty setting, noting how the newer per-VM option is used. Remove the obsolete global flag and its transition TODO while retaining the per-VM behavior; verify the test runner and CI/local build paths still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100