You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Windows code in theory can work with CLang, which includes a bunch of features including coverage analysis. However, figuring out how to make use of this in the GitHub environment is somewhat challenging.
In addition to the challenge of collecting the data, we might have to deal with differences in the path names (slash vs backslash).
If anyone brilliant is looking at this and has already done this, I'd be grateful for a contribution.
The text was updated successfully, but these errors were encountered:
fixes#1063 Include sanitizer runs in CI
fixes#1068 Wssfile test sometimes fails with wrong error code
While here, addressed a number of clang-tidy items, and some light
cleanup of code we were already in.
We have been using opencppcoverage for Code Coverage analysis on windows, very easy to setup and use, just run any (debug compiled) .exe with opencppcoverage and it will spit out coverage data.
The Windows code in theory can work with CLang, which includes a bunch of features including coverage analysis. However, figuring out how to make use of this in the GitHub environment is somewhat challenging.
In addition to the challenge of collecting the data, we might have to deal with differences in the path names (slash vs backslash).
If anyone brilliant is looking at this and has already done this, I'd be grateful for a contribution.
The text was updated successfully, but these errors were encountered: