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

Ignore AccessViolationException in the coverage analyser #2036

Merged
merged 1 commit into from
Dec 26, 2018

Conversation

eggrobin
Copy link
Member

The coverage analysis worked when run by Jenkins before the upgrade, but seems to be broken now even when the rebuild, instrumentation, profiling, and test running are done by hand.
This fails to make sense.
Handling AccessViolationException is disturbing, but let's see if this gives us coverage and whether Jenkins continues to hang following the coverage analysis.

@pleroy pleroy added the LGTM label Dec 26, 2018
@pleroy pleroy merged commit 75f4444 into mockingbirdnest:master Dec 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants