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

updates for v1.5, etc. #289

Merged
merged 8 commits into from
Nov 17, 2020
Merged

updates for v1.5, etc. #289

merged 8 commits into from
Nov 17, 2020

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Nov 11, 2020

@codecov-io
Copy link

codecov-io commented Nov 11, 2020

Codecov Report

Merging #289 (5169eeb) into master (d1dfc39) will increase coverage by 19.41%.
The diff coverage is 94.54%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master     #289       +/-   ##
===========================================
+ Coverage   67.28%   86.70%   +19.41%     
===========================================
  Files           3        3               
  Lines         162      188       +26     
===========================================
+ Hits          109      163       +54     
+ Misses         53       25       -28     
Impacted Files Coverage Δ
src/codecovio.jl 86.41% <92.30%> (+21.86%) ⬆️
src/coveralls.jl 86.79% <96.55%> (+17.28%) ⬆️

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 d1dfc39...5169eeb. Read the comment docs.

@DilumAluthge
Copy link
Member

FWIW, since Travis is ending its unlimited free tier, it might be worth moving this package's CI to GitHub Actions at some point.

@vtjnash vtjnash marked this pull request as ready for review November 11, 2020 06:39
@DilumAluthge
Copy link
Member

Travis was passing earlier, now it seems to be failing.

@vtjnash vtjnash force-pushed the jn/updates-v1.5 branch 6 times, most recently from b72e084 to f98cd7a Compare November 12, 2020 04:28
Coveralls now needs the job id token to be unique, so instead post to a
mock server.
@coveralls
Copy link

coveralls commented Nov 12, 2020

Pull Request Test Coverage Report for Build 926

  • 37 of 40 (92.5%) changed or added relevant lines in 2 files are covered.
  • 3 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+13.5%) to 87.838%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/coveralls.jl 18 19 94.74%
src/codecovio.jl 19 21 90.48%
Files with Coverage Reduction New Missed Lines %
src/coveralls.jl 1 66.98%
src/codecovio.jl 2 72.84%
Totals Coverage Status
Change from base Build 913: 13.5%
Covered Lines: 130
Relevant Lines: 148

💛 - Coveralls

And for travis-ci-com, now just seems to confuse Coveralls on our repo.
Keyword args can require a high compile cost, which is not necessary here. Convert to a Dict to avoid that.
I'm assuming their choices of variables are more canonical. For Codecov,
I checked the variables against their canonical tool
(https://codecov.io/bash).

This also adds the ability to specify the Coveralls settings entirely
from environment variables, overriding autodetection.

There are couple new flags upstream (flags, name, flag_name), and so
I've added those here also.
These functions and their tests now live in CoverageTools.jl
@vtjnash
Copy link
Member Author

vtjnash commented Nov 12, 2020

Yeah, I was still testing different settings and did that intentionally. This has many new updates now, and should be good to review.

@vtjnash vtjnash requested review from fingolfin and omus November 16, 2020 19:38
Copy link
Member

@fingolfin fingolfin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR modifies a lot of things at once. I tried to look at all the changes, and they appear OK, but I won't claim to have checked all of them in detail. They seem broadly sane, though, and if there are regressions, we'll just have to deal with them as they are reported. In the meantime, it seems to unbreak the CI tests and hopefully things in general, so it should be merged.

Thanks!

global:
- COVERALLS_PARALLEL=true
notifications:
webhooks: https://coveralls.io/webhook
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am surprised this is not necessary anymore. They still mention it on https://github.com/marketplace/actions/coveralls-github-action and https://docs.coveralls.io/parallel-build-webhook, and it was absolutely vital when I last played with it -- but that was some time ago; so if that's what you found empirically, let's do it... Coveralls documentation sucks in general, so I am not completely surprised it might not reflect reality anymore :-).

I'll soon need to dig into this again for another project (where Travis cut our legs, so we moved to GitHub Actions, and that broke Coveralls integration), I'll keep this in mind, might simplify things there!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I noticed that even old builds now are showing up correctly without this flag. But the only effect it was now having here was to prevent any builds from showing up (it was unable to process the webhook now, I'm guessing perhaps due to the deprecation of travis-ci.org)

lemurheavy/coveralls-public#1461 (comment)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vtjnash looking at e.g. #288 there are now four coveralls comments there. I vaguely recall from way back that this was caused by the "parallel" support not being activated -- but it's been some time, so I might totally misremember!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It used to be disabled entirely, but I'm not sure why it'd be 4 and not 8 (the number of builds) or 1 (the top comment has 5 rolling edits as the parallel builds finished)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Top comment was created, then edited 5 times; plus 3 more comments; means a total of 1+5+3=9 results reported. The Travis build has 9 jobs. So what I think happens is that whenever one of the jobs ends, Coveralls adds or updates an issue comment. Why it didn't just put all updates in one comment, I can only guess at; most likely a race condition, but w/o being able to see the precise timestamps when each comment was made/updated, it's hard to say...

@fingolfin fingolfin merged commit 6101b62 into master Nov 17, 2020
@fingolfin fingolfin mentioned this pull request Nov 17, 2020
@vtjnash vtjnash deleted the jn/updates-v1.5 branch November 17, 2020 01:41
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.

Code coverage stopped working? Travis is failing on Julia nightly
5 participants