-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Enable Windows runs of AddressSanitizer #95758
Conversation
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsWe now have a new enough version of VS for this
|
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
7154b75
to
32b3836
Compare
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
Most of the libraries failures on Windows are due to #96035. |
/azp run runtime-sanitized |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, aside from failures around the XUnitLogChecker. Looks like we might need to condition that again
- template: /eng/pipelines/common/platform-matrix.yml | ||
parameters: | ||
jobTemplate: /eng/pipelines/common/global-build-job.yml | ||
buildConfig: Debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does Debug
make a difference? That is, is asan supported in Release? Is it better/worse?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ASAN is supported in release, but it can miss some checks as the instrumentation pass runs after many optimization passes, which can cause false negatives on some of the stack usage validation.
The XUnitLogChecker failures are tracked by the issue I linked above (same underlying issue in both scenarios). |
We now have a new enough version of VS for this