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.

classification
Title: update tests relying on a copy of a TLS certificate (pem) to support two versions
Type: enhancement Stage: needs patch
Components: Tests Versions: Python 3.8, Python 3.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: gregory.p.smith
Priority: normal Keywords:

Created on 2019-05-08 17:05 by gregory.p.smith, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg341912 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2019-05-08 17:05
We're having pain today due to the Lib/test/selfsigned_pythontestdotnet.pem certificate update sychronization.

This wouldn't be painful if our tests relying on a specific certificate matching something elsewhere on the network supported multiple possible certificates.  Specifically an old and a new cert.  When doing that, we could go ahead and commit the new cert, moving the existing one to old, before flipping the update on the test infrastructure.  in all branches.

that'd prevent massive PR CI and buildbot failure fallout.
History
Date User Action Args
2022-04-11 14:59:14adminsetgithub: 81036
2019-05-08 17:05:33gregory.p.smithcreate