Added option to turn off PDB file parsing #41
Merged
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.
About
This pull request adds a new setting to the option page dialog. This setting controls whether the PDB files should be parsed at all.
The default setting maintains the original behavior of parsing symbol information.
The effects of disabling PDB parsing are as follows (mentioned in the description of the setting):
Background
Our project outputs some pretty large test binaries. Associated PDB files are tens of megabytes large with hundreds of thousands of symbols. Parsing PDB files this large via MS DIA SDK takes considerable amount of time. Moreover, it seems that DIA SDK sometimes (3 out of 5) simply returns empty list of symbols. In these cases, test traits regexes are not processed, making empty set of traits.
If a project does not make use of the GTA_Traits.h-style traits, only test name regex based, then parsing PDB files are not required, but adds ten seconds delay to every test run for test discovery.
This comes with a compromise that test source file/line information is also lost.