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 corona10
Recipients corona10, lemburg, pitrou, serhiy.storchaka, trrhodes, vstinner
Date 2021-01-01.11:31:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1609500706.47.0.375885148787.issue42794@roundup.psfhosted.org>
In-reply-to
Content
> How to handle similar breakage of external servers?

For tests with the external environment,
How about skipping tests if servers are not available?
It is assumed that if there is a change related to NNTP, it is well checked in the CI and review.
This is because, at this point, reviewers and patch submitters check whether tests with external servers are passed.

The reason for testing with the outside is to confirm that the whole operation works well.
If external servers are not available, we can emit warning messages so that we can recognize when an issue occurs.

Other than that, I can think of local server testing or mocking testing, but I am not sure if it is easy way for the SSL environment.
History
Date User Action Args
2021-01-01 11:31:46corona10setrecipients: + corona10, lemburg, pitrou, vstinner, serhiy.storchaka, trrhodes
2021-01-01 11:31:46corona10setmessageid: <1609500706.47.0.375885148787.issue42794@roundup.psfhosted.org>
2021-01-01 11:31:46corona10linkissue42794 messages
2021-01-01 11:31:46corona10create