Georg Brandl added the comment: OK, a hopefully complete overview of the network-using tests and the services they use, checked by tracing connect() calls during a test run:
* test_codecencodings_*, test_normalization, test_ucn: some Unicode-related data files from unicode.org:80 icu-project.org:80 people.freebsd.org:80 Most of these files are not expected to change; they could be copied to our new host. Some are dependent on the unidata version, new versions would have to be copied each time after updating the unicodedata database. * test_httplib: checks HTTPS with svn.python.org:443 This would require a basic HTTPS setup on the host. * test_imaplib: checks IMAP protocol with cyrus.andrew.cmu.edu:143 cyrus.andrew.cmu.edu:993 Requires an IMAP server on the host that allows unencrypted and encrypted connections (both with STARTTLS and with IMAPS port) and speaks very basic IMAP (login then quit). * test_nntplib: checks NNTP protocol with news.trigofacile.com:119 nntp.aioe.org:563 Requires an NNTP server on the host that allows unencrypted and encrypted connections (both with STARTTLS and on the NNTPS port) and has at least one group with some messages. * test_smtpnet: checks SMTP protocol encryption with smtp.gmail.com:25 smtp.gmail.com:465 Requires an SMTP server that allows encrypted connections (both with STARTTLS and on the SMTPS port) and speaks very basic SMTP (just EHLO and then QUIT). * test_ssl: checks encrypted connections to svn.python.org:443 sha256.tbs-internet.com:443 The svn.python.org is probably a basic HTTPS setup. The second host is apparently used for especially checking SHA256. * test_socket: makes some connection to example.com while resolving the IDNA name испытание.python.org (which is an alias). * test_timeout: checks TCP timeout with blackhole.snakebite.net:56666 whitehole.snakebite.net:56667 www.python.org:80 The first two are testing timeout with a connection that silently drops packets. It is set up using some packet filtering rules for the two ports. * test_urllibnet and test_urllib2net: various checks of HTTP, FTP protocols on example.com:80 www.google.com:80 bit.ly:80 docs.python.org:443 imdb.com:80 ftp.debian.org:21 ftp.mirror.nl:21 gatekeeper.research.compaq.com:21 Most of them are probably fine with a basic readonly FTP server that servers a few files and a basic HTTP server. Some check special cases with broken servers (like imdb.com) that might be a little harder to reproduce. The two disabled tests mentioned by Berker need HTTP Basic Auth enabled on some URL. * test_xmlrpc_net: checks XML-RPC protocol with buildbot.python.org:80 With the current test, serving a static XML page at a certain URL is sufficient: it makes only one request. Another possibility is setting up a small XML-RPC server on a dedicated port. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22650> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com