codingjoe / codingjoe/threadmill
Timing-dependent inspector coverage makes the suite report flapping misses
- 主要语言
- Python
- 星标
- 12
- 派生
- 1
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 10
描述
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` — the `rates_for` path.
- `threadmill/inspector/telemetry.py:81` — the `_evict` `popitem` path.
- `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.
贡献指南
调研方向
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.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- testing-qa
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 68/100