firecracker-microvm / firecracker-microvm/firecracker-containerd
Recode metrics to make sure that we don't leak resources
Open
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Description
For example, if our tests leak loopback devices, we wouldn't notice that since our BuildKite instances are replaced regularly.
Contributor guide
Research direction
The issue names tests, BuildKite instances, metrics, and loopback devices but no files or entry points. Start by locating the test metrics and resource-cleanup code, then determine how repeated test runs can expose leaked loopback devices; done means leaks are observable despite BuildKite instance replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100