Show coverage stats online via coveralls.io
When config.ignore_errors
is Falsey, failures to parse Pyhton files or
look up file sources will now interrupt and early exit collection, which
matches default coverage
behaviour. Previously, we had manually muted
these errors and/or only errored after collecting multiple failures.
pyproject.toml
packages by default (via coverage[toml]
) (962e2242)python-coveralls
entrypoint (3d8d56e4)CoverallsException
(be446287)coverage
v7.0 - v7.4 (8fb36645)coverage
v4.x (752f52a0)docker
imagescoverage
public interface (#421)coverage
versions (#337)coverage
versions v6.0.0 through v6.1.1 exhibited some incompatibilies with
coveralls
; we've updated our version compatibility ranges to exclude those
versions.
Note this implicitly improves support for Python 3.10, as coverage v6.x includes some fixes for v3.10 of Python.
This solves some edge cases around duplicated / unmerged coverage results in parallel runs.
We have reversed the order in which configurations are parsed. This means we are now following the following precedence (latest configured value is used):
If you have the same fields set in multiple of the above locations, please double-check them before upgrading to v3.
The motivation for this change is allowing users to selectively fix values which may be automatically set to the wrong value. For example, Github Actions users may find that Github Actions expects you to use a different "service name" in various different cases. Now you can run, for example:
coveralls --service=github
In places where you need to override the default (which is github-actions
).
--finish
command
introduced in v2.1.0, which did not seem to work for some CircleCI
users.