coverallsapp / coverallsapp/github-action
Parallel job coverage is reported on the next run
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
When running parallel coverage jobs and starting the next run before the previous one is finished, the reports of the previous run show up on the newest one instead of the one they belong to.
Check out trixi-framework/Trixi.jl#400. I started a run with all tests and then removed most of the tests. The newest run reports for example 1d and 3d tests even though I removed them all. The previous run doesn't report any individual coverage jobs, they all show up on the latest run.
Also, the coverage is reported to remain the same although I removed most of the tests.
Here you can clearly see that more coverage reports than test runs show up:
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.
Research direction
Use the overlapping-run scenario described in trixi-framework/Trixi.jl#400 as the reproduction case; this issue names no repository file or test. Compare the coverage reports attached to each concurrent run, and consider the work done when each run contains only its own parallel-job reports and its coverage reflects its own tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, julia
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100