twisted
Try to get codecov responding quickly
Draft for:
- [ ] This is presently an exploratory PR... which doesn't seem to have helped with prompt codecov result reporting.
Codecov Report
Merging #307 (0e94563) into master (87860f3) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #307 +/- ##
=======================================
Coverage 95.39% 95.39%
=======================================
Files 20 20
Lines 1043 1043
Branches 103 103
=======================================
Hits 995 995
Misses 27 27
Partials 21 21
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 87860f3...0e94563. Read the comment docs.
may i recommend https://hynek.me/articles/ditch-codecov-python/ instead to simplify the whole thing?
we can give it a try as a toy task. and sprinkle it with diff-cover that is piped to a github comment :)
But codecov.io is much more than a 100% pass/fail status check. There is an HTML view of the coverage, inline annotations, flapping lines , diff coverage.
I think that codecov.io for towncrier is ok.
I know that codecov.io can be a pain, especially for big projects .
I think the main issue with codecov.io is that being a free ride is hard to fund its development. I like the codecov.io project and I hope it can solve these reliability issues and be a success :)
The problem is less about what it does and more about how it's flaky. Latest example: my PR that didn't touch code supposedly lowered coverage in files I didn't touch…
I anyone wants to implement coverate.py + GitHub action reporting, I would be more than happy to access such a PR...
I can live with a bit of flakiness for towncrier.
I can imagine that for NASA space missions codecov.io flaky behaviour is not acceptable ...but I think we are fine.