CI: Intermittent Failure in unexpected_exit_pid_ns
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
[FATAL /cache/build/exclusive-amdci3-0/julialang/rr/src/PerfCounters.cc:630:read_ticks()]
(task 105315 (rec:103563) at time 222)
-> Assertion `!counting_period || interrupt_val <= adjusted_counting_period' failed to hold. Detected 184055 ticks, expected no more than 177242
Note that the test timed out rather than failing because of the following assertion while dumping the register state using the emergency debugger:
[FATAL /cache/build/exclusive-amdci3-0/julialang/rr/src/Task.cc:1026:regs() errno: ENOTTY]
(task 105315 (rec:103563) at time 222)
-> Assertion `is_stopped' failed to hold.
Tail of trace dump:
It would be nice to make the emergency dump robust to this situation such that CI finishes rather than running into the timeout.
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 by tracing the emergency register dump through Task.cc, especially regs(), and compare it with the failure in PerfCounters.cc at read_ticks(). Reproduce unexpected_exit_pid_ns in CI and make the emergency dump handle this state so the test finishes instead of timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100