Run address sanitiser in the GitHub CI#26640
Conversation
|
Looks like you've found an X11 bug. |
Sorry, something went wrong.
|
I'd exclude the failing tests for now and add a note somewhere to revisit the exclusions in a month or two. |
Sorry, something went wrong.
|
Rather than putting |
Sorry, something went wrong.
👍 Makes sense, that's clearly a better option |
Sorry, something went wrong.
|
|
Sorry, something went wrong.
|
Yeah, that makes sense, although it may be worth to also add some option so you can easily run this locally. I think we should also add something to the devguide about what is excluded and why. In any case, I am going to merge this and add the option to regrtest in a separate PR. |
Sorry, something went wrong.
My concern is that there is also an ASAN buildbot, and this denylist is copied manually. It increases the maintenance burden. Well, since @pablogsal runs the buildbot, he is likely eagger to maintain these two lists manually ;-) Maybe an option is not needed, and regrtest could detected if Python was built with ASAN using sysconfig to get compiler flags.
Sure, it would be great to skip less tests ;-) |
Sorry, something went wrong.
No description provided.