Ignore AccessViolationException in the coverage analyser #2036
+18
−7
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 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.