This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Mark.Shannon
Recipients Mark.Shannon, pablogsal
Date 2021-06-09.15:11:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623251489.92.0.918906113301.issue44363@roundup.psfhosted.org>
In-reply-to
Content
I still get quite a few failures on the main branch.
It seems like ceval.c:1600 upsets the sanitizer, at least for gcc.

There isn't anything wrong with that line, but as I plan to change it anyway I guess it doesn't matter:
https://github.com/python/cpython/pull/26595

I plan to get the main branch passing the tests with address sanitization (at least on my machine with my gcc :)

Running the tests doesn't seem to take that long (at least not compared with refleak tests).
Do you think it would be it feasible to run the address sanitizer on all PRs, so that we can keep it passing?
History
Date User Action Args
2021-06-09 15:11:29Mark.Shannonsetrecipients: + Mark.Shannon, pablogsal
2021-06-09 15:11:29Mark.Shannonsetmessageid: <1623251489.92.0.918906113301.issue44363@roundup.psfhosted.org>
2021-06-09 15:11:29Mark.Shannonlinkissue44363 messages
2021-06-09 15:11:29Mark.Shannoncreate