Skip to content

Restrict coverage collection to release builds. #532

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

Merged
merged 1 commit into from
Jun 18, 2019

Conversation

allisonbm92
Copy link
Contributor

Code coverage can fail for local builds, becuase there are multiple
definitions for the same classes (debug and release). On CI, debug is
disabled. This change forces the coverage check to use on release
builds, thus making it compatible with both local and CI use cases.

This fixes the problem presented in #531.

Code coverage can fail for local builds, becuase there are multiple
definitions for the same classes (debug and release). On CI, debug is
disabled. This change forces the coverage check to use on release
builds, thus making it compatible with both local and CI use cases.

This fixes the problem presented in #531.
Copy link
Contributor

@yifanyang yifanyang left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for the finding out the root cause and providing a fix!

@allisonbm92 allisonbm92 merged commit 3b5a1f4 into master Jun 18, 2019
@allisonbm92 allisonbm92 deleted the allison-release-cov branch June 18, 2019 22:16
@firebase firebase locked and limited conversation to collaborators Oct 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants