The profiler job's make coverage repeats the slow tests the benchmark-harness job runs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Read .github/workflows/audits.yml and inspect the profiler and benchmark-harness jobs, then check the Makefile targets and slow-test markers they use. Map each slow test file to the job that runs it and confirm no slow test runs in both jobs. Done when the workflow runs every slow test in exactly one required job and a test lists which job runs each slow test file.
Written by the indexing model from the issue text.
Description
Where: .github/workflows/audits.yml (profiler and benchmark-harness jobs).
Current gap: make coverage runs the whole suite including the slow benchmark tests (5 minutes of the 316 s parallel run), and the benchmark-harness job runs tests/test_metrics.py, test_manifest.py, test_strategies.py and test_benchmark.py again.
Suggested approach: Run the slow tests once: either give the benchmark-harness job the slow marker (and collect their coverage there) or have the profiler job use make coverage-fast, keeping every slow test in exactly one required job.
Done when: no slow test runs in both jobs and a test lists which job runs each slow test file.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 85
Getting set up
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 yakew7/Fair-Code
-
community
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
community
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
check_contributors.py --stub cannot write the closing issue numberPossibly taken @obethgeoff10c-ops claimed this 1 day ago. Opencommunity enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yakew7/Fair-Code#1308 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
The generated-files builder timeout cannot be changedPossibly taken @renuvenugopal178 claimed this 3 days ago. Openenhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yakew7/Fair-Code#1306 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
area/installation kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/aibrix#3456 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cadence-workflow/cadence-ai-samples#175 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DecapodLabs/decapod#1626 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
sk7n4k3d/delonghi-ha#52 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fdittgen-png/deskilo#3753 ·
Maintainers usually reply within 1 day