oxidecomputer / oxidecomputer/maghemite
Stuck interop jobs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
It appears interop jobs can get stuck with little to no outward logging. We should
- use RUST_LOG=debug
- collect propolis server logs
- set a timer for ~20 minutes as we don't expect interop jobs to go past 15.
So we can see where things are getting stuck.
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 with the linked Buildomat interop job and trace the interop job entry point and Propolis server logging. Enable RUST_LOG=debug, collect the server logs, and add the approximately 20-minute timeout; done means jobs exceeding the expected 15-minute duration produce enough logging to identify where they are stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100