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

iOS: Disable code coverage #1195

Merged
merged 1 commit into from
Sep 1, 2020
Merged

iOS: Disable code coverage #1195

merged 1 commit into from
Sep 1, 2020

Conversation

badboy
Copy link
Member

@badboy badboy commented Aug 28, 2020

This avoids linker errors due to missing errors such as as "___llvm_profile_runtime".
We only use code coverage in development for our manual checks, but we
should not put that in released binary frameworks.

@auto-assign auto-assign bot requested a review from brizental August 28, 2020 07:05
@badboy badboy requested review from travis79 and removed request for brizental August 28, 2020 07:05
@badboy
Copy link
Member Author

badboy commented Aug 28, 2020

I actually need to properly test this once more against Firefox iOS

This avoids linker errors due to missing errors such as as "___llvm_profile_runtime".
We only use code coverage in development for our manual checks, but we
should not put that in released binary frameworks.
@badboy badboy force-pushed the disable-code-coverage-in-release branch from 2513969 to 7de6b1e Compare August 28, 2020 07:11
Copy link
Member

@travis79 travis79 left a comment

Choose a reason for hiding this comment

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

\o/

@badboy badboy changed the title iOS: Disable code coverage in release builds iOS: Disable code coverage Aug 28, 2020
@badboy badboy merged commit b78fc65 into main Sep 1, 2020
@badboy badboy deleted the disable-code-coverage-in-release branch September 1, 2020 12:54
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