Timing-dependent inspector coverage makes the suite report flapping misses
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start with tests/test_inspector.py, which passes independently, then inspect threadmill/inspector/telemetry.py lines 37-41 and 81 and threadmill/inspector/app.py lines 592-603. Reproduce the coverage flapping and make those timing-dependent paths deterministic, or mark the assertions so coverage no longer depends on scheduling; the inspector tests and coverage should remain stable.
Written by the indexing model from the issue text.
Description
Found by testJoe while adding coverage for the fair multi-queue rotation (codingjoe-fair-multi-queue-scheduling). Pre-existing and untouched by that diff.
Coverage of these inspector paths flaps from run to run, which means the lines are reached by timing rather than deterministically — the tests under tests/test_inspector.py pass on their own (58/58 per run), so this is a flaky-coverage problem, not a red suite:
threadmill/inspector/telemetry.py:37-41— therates_forpath.threadmill/inspector/telemetry.py:81— the_evictpopitempath.threadmill/inspector/app.py:592-603—_refresh_sparklines.
Either drive those paths deterministically (inject the clock, shorten the refresh interval) or mark the timing-dependent assertions so coverage stops depending on scheduling.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 19h 11m
- Merged PRs (30d)
- 12
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.
More from codingjoe/threadmill
-
Difficulty 2/5 Half a day Newbie friendliness 84/100
codingjoe/threadmill#52 ·
-
WorkerProcess passes None poll intervals to the backend, breaking acquire in the consumer thread Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
codingjoe/threadmill#53 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
codingjoe/threadmill#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codingjoe/threadmill#47 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
codingjoe/threadmill#54 ·
All issues in codingjoe/threadmill
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·