oxidecomputer / oxidecomputer/buildomat
lab factory should collect crash dumps from machines that panic
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
If a machine running a lab job panics today, the console output during the panic (which usually includes a stack trace) is included in the event stream for the job by the lab factory. In the environment provided by the agent, though, we do not configure a dump device -- and even if we did, there is no subsequent factory-controlled boot to get in there and recover the dump.
We should add support for configuring a dump device, and for booting from a maintenance image (different to the target-specified image) for dump recovery.
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 tracing the lab factory's job execution, machine boot, and event-stream flows; the issue does not name specific files or tests. Determine how a dump device and a factory-controlled maintenance-image boot could be configured and recovered, then verify that panic dumps are collected into the job event stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100