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 vstinner
Recipients christian.heimes, gregory.p.smith, miss-islington, pablogsal, vstinner
Date 2022-03-04.09:42:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't agree with GH-31673. Did you try defining NO_MISALIGNED_ACCESSES instead?

Did you read the commit message? The change is not about skipping the test, but fixing the CI. Previously, test_hashlib was not run at all on the UBSan buildbot, now most test_hashlib tests are run. The intent is to make sure that we don't add *new* undefined behavior.

As I wrote in the commit, the UD must be fixed in _sha3.

No, I didn't try NO_MISALIGNED_ACCESSES, I don't know this macro. If you have an idea on how _sha3 can be fixed on the UBSan buildbot, please go head!
Date User Action Args
2022-03-04 09:42:54vstinnersetrecipients: + vstinner, gregory.p.smith, christian.heimes, pablogsal, miss-islington
2022-03-04 09:42:54vstinnersetmessageid: <>
2022-03-04 09:42:54vstinnerlinkissue46913 messages
2022-03-04 09:42:54vstinnercreate