-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal error "Can't combine line data with arc data" for code using subprocesses #243
Comments
Looks like you're mixing branch and line coverage (e.g. due to different/no config files being used in subprocesses). |
See pytest-dev/pytest-cov#237 (comment) Also pytest options for Travis CI builds were consolidated in PYTEST_ADDOPTS environment variable.
@blueyed, thank you for workaround. Feel free to close this report, if it seems to be a duplicate. Anyway, I believe there is an issue. |
@skirpichev |
I was getting (both locally and on GitHub Actions) Internal error "Can't combine line data with arc data" apparently because this test code calls subprocesses and the results are getting garbled as they are written to the single .coverage file. pytest-dev/pytest-cov#243 (comment) has more info.
I was getting (both locally and on GitHub Actions) Internal error "Can't combine line data with arc data" apparently because this test code calls subprocesses and the results are getting garbled as they are written to the single .coverage file. pytest-dev/pytest-cov#243 (comment) has more info.
Fresh setup of blue, installed requirements.txt, and ran pytest. Then got: INTERNALERROR> coverage.misc.CoverageException: Can't combine arc data with line data Debugging lead to pytest-dev/pytest-cov#243 where adding --cov-branch was identified as a workaround ¯\_(ツ)_/¯
This works around coverage config discrepancy between the main process and a subprocess. See pytest-dev/pytest-cov#243
…st Cython API functions The extension is built in temp folder. Added cython as Cython test dependency Pass --cov-config option to pytest with coverage. This works around coverage config discrepancy between the main process and a subprocess. See pytest-dev/pytest-cov#243 added _cython_api.pyx to flake exception list Exclude dpctl/tests/* and dpctl/_version from coverage reporting Fix loading of Cython extension _cython_api on Windows Add test for property=int usage
…st Cython API functions The extension is built in temp folder. Added cython as Cython test dependency Pass --cov-config option to pytest with coverage. This works around coverage config discrepancy between the main process and a subprocess. See pytest-dev/pytest-cov#243 added _cython_api.pyx to flake exception list Exclude dpctl/tests/* and dpctl/_version from coverage reporting Fix loading of Cython extension _cython_api on Windows Add test for property=int usage
Added the cov-config flag at suggestion of: pytest-dev/pytest-cov#243.
This configuration change helps prevent coverage job errors caused by the usage of subprocess module. See details at pytest-dev/pytest-cov#243
This configuration change helps prevent coverage job errors caused by the usage of subprocess module. See details at pytest-dev/pytest-cov#243
While updating travis-ci config of the diofant from dist:trusty to dist:xenial I noticed build failures like this for jobs with coverage profiling enabled.
Little debugging shows, that problem seems to be related with
autowrap()
function calls. For example, in this scenario:After such test run there are files like
.coverage.hostname.1234
, which left on the system:Problem related with the
test_2()
, if you blacklist this test by-k 'not test_2
- there will be no internal error. Also, as you can see,test_2
itself was passed, problem happens only for coverage builds.Not sure why everything was working on Trusty's Travis builds (see e.g. this and coverage for autowrap.py seems to be enabled and around 91%), the problem happens to me for all local test runs with same CPython/packages versions as on Travis-CI.
The text was updated successfully, but these errors were encountered: