Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork15
Compiler Sanitization tests CI#242
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ngoldbaum commentedDec 8, 2025
@SwayamInSync it doesn't seem like too many UBSan warnings and I think they're all inside of the quaddtype implementation. I'd probably just fix them. |
SwayamInSync commentedDec 8, 2025
Right, there were some from NumPy as well, this job only grep on Sure, I'll look over them and resolve |
ngoldbaum commentedDec 8, 2025
The NumPy ones we can add suppressions for. Or fix them in NumPy 😀. This describes how to use suppression files for TSan, it's the same for the other sanitizers:https://py-free-threading.github.io/thread_sanitizer/#tsan-suppressions |
@ngoldbaum from NumPy I added both ASAN and UBSAN, for now only UBSAN warnings seems to be there.
The workflow is set to fail only if any warnings are found. Maybe we can more loose it to as fail if only ASAN are found.