codingjoe / codingjoe/threadmill
Timing-dependent inspector coverage makes the suite report flapping misses
- Ngôn ngữ chính
- Python
- Star
- 12
- Fork
- 1
- Merge trung bình
- 1 ngày 1 giờ
- Pull request đã merge (30 ngày)
- 10
Mô tả
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.
Hướng dẫn đóng góp
Hướng nghiên cứu
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.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- python
- Lĩnh vực
- testing-qa
- Loại issue
- Lỗi
- Độ khó
- 3/5
- Thời gian dự kiến
- 1-2 ngày
- Mức độ hoạt động
- Sôi nổi
- Độ rõ ràng
- Khá rõ ràng
- Mức phù hợp với người mới
- 68/100