opencontainers / opencontainers/runc
ci: race in TestExecIn
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Description
Just saw this in CI here on alma-linux-8:
=== RUN TestExecIn
execin_test.go:63: unexpected running process, output "PID USER TIME COMMAND\n 1 root 0:00 [runc:[2:INIT]]\n 7 root 0:00 ps\n"
--- FAIL: TestExecIn (0.17s)
Apparently it's a race -- container "init" process (cat) in this case has not yet started, but the container "exec" process (ps) already ran.
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 with TestExecIn in execin_test.go and run the test to reproduce the reported CI failure. Compare the expected process output with the output showing ps before the container init process, then trace the test's init and exec ordering. Done means TestExecIn reliably observes the intended process state without this race in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100