opencontainers / opencontainers/runc
`runc run [timens with no offsets]` is flaky on ubuntu
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Seen this failure twice already:
not ok 184 runc run [timens with no offsets]
# (in test file tests/integration/timens.bats, line 37)
# `grep -E '^monotonic\s+0\s+0$' <<<"$output"' failed
# runc spec --rootless (status=0):
#
# runc run test_busybox (status=0):
# monotonic 0 0
# boottime 0 0
I stared at the code and it looks just fine, yet grep fails. I suspect a problem with grep (or me).
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 tests/integration/timens.bats at line 37 and reproduce the runc run [timens with no offsets] test on Ubuntu, inspecting the captured output and the grep condition. Determine why the expected monotonic 0 0 line is intermittently rejected, then make the test reliable and confirm it passes repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ubuntu
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100