Skip to content
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

Closed
wants to merge 38 commits into from

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Feb 27, 2019

This should bring coverage back that got missing with 9dcd6f2.

Continuation of #4839.

@blueyed blueyed changed the title ci: Travis: revisit/fix coverage reporting WIP: ci: Travis: revisit/fix coverage reporting Feb 27, 2019
@codecov
Copy link

codecov bot commented Feb 27, 2019

Codecov Report

Merging #4846 into master will increase coverage by 0.54%.
The diff coverage is 66.66%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
src/_pytest/warnings.py 87.65% <ø> (ø) ⬆️
src/_pytest/compat.py 96.98% <ø> (ø) ⬆️
src/_pytest/unittest.py 87.3% <ø> (ø) ⬆️
src/_pytest/terminal.py 91.74% <0%> (+2.64%) ⬆️
testing/test_pdb.py 95.84% <100%> (+47.69%) ⬆️
testing/test_argcomplete.py 20.28% <0%> (-47.83%) ⬇️
src/_pytest/_argcomplete.py 33.33% <0%> (-41.67%) ⬇️
src/_pytest/pytester.py 80.93% <0%> (-5.41%) ⬇️
testing/deprecated_test.py 96.77% <0%> (-3.23%) ⬇️
testing/python/fixture.py 98.5% <0%> (-0.58%) ⬇️
... and 6 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df8869c...3d0ef12. Read the comment docs.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

After 1st commit:

increase coverage by 0.99%.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

Now without windows:

will increase coverage by 0.31%.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

Now:

will increase coverage by 0.46%.

Need to investigate/compare coverage again.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

btw: so apparently tests are failing with PYTEST_ADDOPTS=-vv on Travis.. :/
(https://travis-ci.org/pytest-dev/pytest/builds/499355099?utm_source=github_status&utm_medium=notification)

@nicoddemus
Copy link
Member

btw: so apparently tests are failing with PYTEST_ADDOPTS=-vv on Travis.. :/

😞

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

codecov/patch link still times out, with only 5 uploads now.. https://codecov.io/gh/pytest-dev/pytest/commit/11b531be0a38e3c9ce9e43e52fbc3c56fb72b6a5/build
So the base might also be relevant here.. :/

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

@nicoddemus
But we can see that only ~5 build jobs are necessary to have ~current coverage.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

The diff status is pretty much expected, since I've added comments where coverage regressed due to #4839.

@nicoddemus
Copy link
Member

codecov/patch link still times out, with only 5 uploads now.. codecov.io/gh/pytest-dev/pytest/commit/11b531be0a38e3c9ce9e43e52fbc3c56fb72b6a5/build
So the base might also be relevant here.. :/

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?

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

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.

@nicoddemus
Copy link
Member

I'm slacking with them since September last year about this at least.. :/

Bummer. They have no idea why our coverage report view times out?

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

Yeah, not really apparently.. the suggested it might be flags, or combinations in general.
I've also seen it with other projects though (awesome/awesomeWM), where using less flags appeared to help.. there are less jobs though.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 27, 2019

@nicoddemus
FWIW I could invite you on the slack conversation they've created with me, but it would not really help I guess.

@blueyed blueyed mentioned this pull request Feb 27, 2019
@nicoddemus
Copy link
Member

Yeah, I agree.

Feel free to merge this then when you clean it up and deem it good enough.

@blueyed
Copy link
Contributor Author

blueyed commented Feb 28, 2019

Nearly there - will hopefully finish it tomorrow or on the weekend then.

@blueyed
Copy link
Contributor Author

blueyed commented Mar 1, 2019

With master being merged here this also now does not time out anymore on codecov.io.

@nicoddemus
Copy link
Member

So in summary flags were to blame then?

@blueyed
Copy link
Contributor Author

blueyed commented Mar 1, 2019

So in summary flags were to blame then?

Looks like it, yes.

@nicoddemus
Copy link
Member

Good, I'm sure they would like to know that. 👍

@blueyed
Copy link
Contributor Author

blueyed commented Mar 1, 2019

It is something they suspect already. But it is not the only factor apparently.

blueyed added a commit to blueyed/pytest that referenced this pull request Mar 1, 2019
This should bring coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
@blueyed
Copy link
Contributor Author

blueyed commented Mar 1, 2019

Continued / restarted in #4865.

@blueyed blueyed closed this Mar 1, 2019
@blueyed blueyed deleted the revisit-cov branch March 1, 2019 14:38
blueyed added a commit to blueyed/pytest that referenced this pull request Mar 1, 2019
This should bring coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
blueyed added a commit to blueyed/pytest that referenced this pull request Mar 1, 2019
This should bring coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
blueyed added a commit to blueyed/pytest that referenced this pull request Mar 4, 2019
This brings coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
blueyed added a commit to blueyed/pytest that referenced this pull request Mar 5, 2019
This brings coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
blueyed added a commit to blueyed/pytest that referenced this pull request Mar 5, 2019
This brings coverage back that got missing with 9dcd6f2.

Continuation of pytest-dev#4839 / pytest-dev#4846.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants