astropy / astropy/astropy-benchmarks
How to see which code is covered or not by benchmarks?
- Dominant language
- Python
- Stars
- 9
- Forks
- 35
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 1
Description
Recently @eerovaher brought up this good question. Would be nice to see what code is actually benchmarked (like `codecov` style) without having to dig through each benchmark module.
Not sure how hard this is to do. Running coverage during actual benchmarking would give you inaccurate timing, so the coverage measurement would have to be a separate job just for coverage, not timing. 💭
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the benchmark modules and how benchmarking is currently run. Determine how a separate coverage-only job could report which code is exercised without changing benchmark timings. Done means the project exposes a usable coverage view across the benchmarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100