-
Notifications
You must be signed in to change notification settings - Fork 173
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
[decomp] more of res
+ change a few macros
#527
Conversation
Pull Request Test Coverage Report for Build 874767219
💛 - Coveralls |
"name": "Release", | ||
"generator": "Ninja", | ||
"configurationType": "RelWithDebInfo", | ||
"configurationType": "Release", | ||
"buildRoot": "${projectDir}\\out\\build\\${name}", | ||
"installRoot": "${projectDir}\\out\\install\\${name}", | ||
"cmakeCommandArgs": "", | ||
"buildCommandArgs": "", | ||
"addressSanitizerEnabled": true, | ||
"addressSanitizerEnabled": false, |
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.
should we make a separate config to use in the windows CI build to still use ASan? or do we no longer care.
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.
I think it would be nice to have asan tests on windows still, but that can wait for later. We still have them under the clang linux build.
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.
I wasn't able to notice any difference with asan on/off for the github testing VM (that makes sense, 90% of the time is spent compiling and the tests take less than a minute) so it could probably be left on for those
No description provided.