GH Actions: try a work-around for weird Coveralls results #127
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrfnl
force-pushed
the
feature/ghactions-work-around-for-coveralls-reporting
branch
2 times, most recently
from
5e63daa
to
81f739f
Compare
jrfnl
force-pushed
the
feature/ghactions-work-around-for-coveralls-reporting
branch
from
81f739f
to
f274ada
Compare
The aggregate coverage results reported back by Coveralls for PRs have been off for quite a while now. While the Coveralls team has not found the root cause yet, they have put an endpoint in place which _should_ help in working around this. The short of it is that the initial run results get calculated incorrectly, but that a re-run of the same coveralls build gets the correct results for the calculation, so triggering this calculation re-run from within the build _should_ (theoretically) fix the issue. I am the first to implement this solution though, so consider this a trial for the time being. Ref: * lemurheavy/coveralls-public#1631
jrfnl
force-pushed
the
feature/ghactions-work-around-for-coveralls-reporting
branch
from
f274ada
to
37371d1
Compare
jrfnl
deleted the
feature/ghactions-work-around-for-coveralls-reporting
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The aggregate coverage results reported back by Coveralls for PRs have been off for quite a while now.
While the Coveralls team has not found the root cause yet, they have put an endpoint in place which should help in working around this.
The short of it is that the initial run results get calculated incorrectly, but that a re-run of the same coveralls build gets the correct results for the calculation, so triggering this calculation re-run from within the build should (theoretically) fix the issue.
I am the first to implement this solution though, so consider this a trial for the time being.
Ref: