-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
WIP: ci: Travis: revisit/fix coverage reporting #4846
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4846 +/- ##
==========================================
+ Coverage 94.28% 94.82% +0.54%
==========================================
Files 113 113
Lines 25160 25161 +1
Branches 2497 2497
==========================================
+ Hits 23723 23860 +137
+ Misses 1100 971 -129
+ Partials 337 330 -7
Continue to review full report at Codecov.
|
After 1st commit:
|
Now without windows:
|
Now:
Need to investigate/compare coverage again. |
btw: so apparently tests are failing with |
😞 |
codecov/patch link still times out, with only 5 uploads now.. https://codecov.io/gh/pytest-dev/pytest/commit/11b531be0a38e3c9ce9e43e52fbc3c56fb72b6a5/build |
@nicoddemus |
The diff status is pretty much expected, since I've added comments where coverage regressed due to #4839. |
Not sure how to proceed then. Can we reach out to them perhaps? Or even drop the current base and start fresh, if that's the issue? |
I'm slacking with them since September last year about this at least.. :/ I will compare this manually again, clean it up, and then we should merge it. I will bring back the jobs as before, but only ~5 then with coverage reporting. I also plan to e.g. replace py37 with py37-pexpect (to get one less job) etc. |
Bummer. They have no idea why our coverage report view times out? |
Yeah, not really apparently.. the suggested it might be flags, or combinations in general. |
@nicoddemus |
Yeah, I agree. Feel free to merge this then when you clean it up and deem it good enough. |
This should bring coverage back that got missing with 9dcd6f2. 1. add PYTEST_COVERAGE to py37-pexpect,… job For `_pytest.debugging`, `Testdir.spawn`, `_pytest.terminal`. 2. re-add py37-xdist macos job This covers e.g. `_disable_output_capturing_for_darwin` again. NOTES: I have compared the coverage manually on Codecov, e.g. for `_pytest.debugging`: Before: https://codecov.io/gh/pytest-dev/pytest/src/ee62674322206299e0caaa36c172d9bb63feeaaf/src/_pytest/debugging.py After: https://codecov.io/gh/pytest-dev/pytest/src/9dcd6f2a87650f31f5b3b754e38a1cf4d6a14fe4/src/_pytest/debugging.py
Nearly there - will hopefully finish it tomorrow or on the weekend then. |
With master being merged here this also now does not time out anymore on codecov.io. |
So in summary |
Looks like it, yes. |
Good, I'm sure they would like to know that. 👍 |
It is something they suspect already. But it is not the only factor apparently. |
This should bring coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
Continued / restarted in #4865. |
This should bring coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
This should bring coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
This brings coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
This brings coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
This brings coverage back that got missing with 9dcd6f2. Continuation of pytest-dev#4839 / pytest-dev#4846.
This should bring coverage back that got missing with 9dcd6f2.
Continuation of #4839.