| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
It isn't run under coverage testing in CI, so it gives false negatives
There was a problem hiding this comment.
Turns out I had a branch to do this earlier this year (except of course not the benchmarks.py bit), but never got round to opening the PR :)
Here's the other things I was going to include.
Sorry, something went wrong.
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Andrew Murray <3112309+radarhere@users.noreply.github.com>
|
Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
As it says in the commits and on the tin; I noticed Codecov (rightly) said benchmarks.py is at zero coverage.
While at it, ported .coveragerc to the pyproject.toml format for one less loose config file in the repo root.