Add instrumentation tests coverage workaround #360
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
ekigamba
changed the title
ekigamba
force-pushed
the
instrumentation-coverage-workaround
branch
2 times, most recently
from
4e2400b
to
7dead40
Compare
- Enable testCoverage only for instrumentation tests and disable the flag after - Add the path for the new instrumentation test coverage ec file Relates to #358
ekigamba
force-pushed
the
instrumentation-coverage-workaround
branch
from
7dead40
to
5eb8bbc
Compare
Pull Request Test Coverage Report for Build #587
💛 - Coveralls |
- Fix flaky build
|
Coveralls cannot link to the correct source code on the repository This is the issue but this seems to be resolved |
|
Coveralls seems to have an issue related to Java 11 gradle/gradle#9764 gradle/gradle#8286 that generates the wrong source path |
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.
Relates to #358
Experimental: This is a possible workaround that is going to be flaky and will need to be removed once the issue is officially resolved