bpo-44022: Improve the security fix regression test. #26503
Conversation
It wasn't actually detecting the regression due to the assertion being too lenient.
|
Thanks @gpshead for the PR |
It wasn't actually detecting the regression due to the assertion being too lenient. (cherry picked from commit e60ab84) Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
GH-26504 is a backport of this pull request to the 3.10 branch. |
It wasn't actually detecting the regression due to the assertion being too lenient. (cherry picked from commit e60ab84) Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
GH-26505 is a backport of this pull request to the 3.9 branch. |
|
GH-26506 is a backport of this pull request to the 3.8 branch. |
|
GH-26507 is a backport of this pull request to the 3.7 branch. |
|
GH-26508 is a backport of this pull request to the 3.6 branch. |
It wasn't actually detecting the regression due to the assertion being too lenient. (cherry picked from commit e60ab84) Co-authored-by: Gregory P. Smith <greg@krypto.org>
It wasn't actually detecting the regression due to the assertion being too lenient. (cherry picked from commit e60ab84) Co-authored-by: Gregory P. Smith <greg@krypto.org>
|
|
|
|
|
It wasn't actually detecting the regression due to the
assertion being too lenient.
The fix that is already in is still good, this just corrects the test.
https://bugs.python.org/issue44022