Comments (20)
Can you please test against latest master, there are various improvements/fixes not yet released.
from pytest-cov.
Sorry, I get the same results...
from pytest-cov.
I was experiencing a similar issue where running:
$ py.test --cov mymodule --cov-report=term-missing
was reporting correct coverage. Then when running through setuptools like:
$ python setup.py test
The coverage was incorrect. However, installing the latest from master
branch has fixed my issue.
from pytest-cov.
@diefans Confirmed: https://travis-ci.org/schlamar/pytest-cov/builds/26548730
@mattupstate That seems unrelated, but thanks for confirming that master solves a few issues.
from pytest-cov.
This is an upstream issue: https://bitbucket.org/hpk42/py/issue/45/forkedfunc-skips-exit-handlers-breaks
from pytest-cov.
@diefans I have a hacky but working solution by patching py.process.ForkedFunc. Not sure if I want to roll that out officially. But it should work if you add this to your conftest.py: fb100db
from pytest-cov.
I have prepared a much nicer solution upstream:
- py pull request
- fix in cov-core schlamar/cov-core@52086bc
from pytest-cov.
@schlamar Since this is upstream bug, does this mean you can release without the monkeypatching? Or are you going to wait for upstream anyways?
from pytest-cov.
@sontek I'm going to wait for the decision on my pull request for py. If it is merged I can release because pytest-cov doesn't need any further changes.
from pytest-cov.
@sontek 1.7.0 just released
@diefans this will be fixed as soon as a new py version is released, my pull request was merged
from pytest-cov.
@diefans should be fixed, you just need to upgrade py to 1.4.21 and cov-core to 1.13.0.
from pytest-cov.
Broken again with py 1.4.22
https://bitbucket.org/hpk42/py/diff/py/_process/forkedfunc.py?diff2=37f557844498&at=default
from pytest-cov.
Yes, I know. We are working something out. For now, you can pin py to 1.4.21.
from pytest-cov.
pytest 2.6.0 depends on py 1.4.22, so you require to downgrade them both =)
My 2 years old patch is still working:
- In session start record current PID
- Before test start compare current pid with session pid and if they are different -- make multiprocessing start
- Before teardown check is we used multiprocessing and stop it if needed
But I if you want things to make right you probably should ask xdist to provide box_start/box_stop hooks which you will be able to use.
from pytest-cov.
@mocksoul Do you have some code? =)
from pytest-cov.
Do we have a fix for this?
from pytest-cov.
@aconrad #15 should fix it, I might find some time at the weekend to have a look at it.
from pytest-cov.
fixed (again) in 1633bd3, will be released soon
from pytest-cov.
Sweet! @schlamar can you ping this ticket when a new release is available? Thanks!
from pytest-cov.
As being said, it is fixed in pytest-cov-1.8.0, https://pypi.python.org/pypi/pytest-cov/1.8.0
from pytest-cov.
Related Issues (20)
- PyO3 error HOT 1
- cov-config file argument ignored when tox.ini exists HOT 1
- [docs] Delete AppVeyor mentions
- [docs] Merge overview/readme and index documents in Sphinx
- [docs] Switch to Furo
- [FR] Extend pytest mark/fixture to auto-apply `# pragma: no cover`
- Pytest and pytest-cov reload numpy HOT 1
- Remove usage of deprecated `rsyncdir`, which will be removed in pytest-xdist 4.0 HOT 2
- Ignore partial lines in the coverage report percentage HOT 3
- Strange BSD License mapping for pytest_cov-2.7.1-py2.py3-none-any.whl HOT 1
- no-data-collected under unix when using filterwarnings in pytest.ini HOT 4
- Memory Leak Python 3.12.2 HOT 13
- GitHub Actions failures on Python 3.8 and 3.9 on pytest81-xdist350-coverage74 (windows) HOT 1
- coverage starts too late when a plugin imports the project under test HOT 5
- "Fail under check" is failing because of ignoring the precession config
- Pytest-watch with coverage (If not existent)
- Coverage both says its 100% and 0% when no code lines are found, fails
- Error combining coverage when running with pytest-xdist and a custom coverage plugin HOT 3
- condition was never false HOT 2
- Is it possible to add cov-warn-under option? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pytest-cov.