Package: python-eventlet / 0.19.0-6
Metadata
Package | Version | Patches format |
---|---|---|
python-eventlet | 0.19.0-6 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
remove self.assert in tests.patcher_test.py.patch | (download) |
tests/patcher_test.py |
4 2 + 2 - 0 ! |
fixes tests in tests.patcher_test.threading |
fix FTBFS on sphinx build.patch | (download) |
doc/modules/zmq.rst |
1 0 + 1 - 0 ! |
removes line that is doing ftbfs in doc |
fixed privacy breach in examples.patch | (download) |
examples/websocket.html |
4 2 + 2 - 0 ! |
fixed privacy breach in examples Upstream is referencing external websites, we don't allow this. |
allow more busy cpu.patch | (download) |
tests/zmq_test.py |
6 3 + 3 - 0 ! |
allow more busy cpu The tests assume a fast CPU, but under my VMs, the tests are just failing with the CPU being more than 10% busy. |
remove networking tests.patch | (download) |
tests/greenio_test.py |
20 0 + 20 - 0 ! |
remove networking tests Upstream is attempting connection to 192.0.2.1 on port 80, and expects it to always timeout. However, some Debian users may well have a web server running on that IP address, meaning the test would fail in such setup (even if this is reserved IANA IPs). Therefore, removing such bad tests. . Also, these tests have been failing for a reason on my arm64 builder, probably because it's a slow machine. |
greendns_tests_fix.patch | (download) |
tests/greendns_test.py |
7 1 + 6 - 0 ! |
[patch] greendns tests: work around patcher/green package weirdness The issue can be demonstrated by running the following piece of code: # t.py from __future__ import print_function from eventlet.support import greendns import sys if sys.argv[1] == 'yes': import dns.resolver print(sys.argv[1], issubclass(greendns.HostsAnswer, greendns.dns.resolver.Answer)) The results: # Python 2.7.11 % python t.py yes yes False % python t.py no no True # Python 3.5.1 % python t.py yes yes False % python t.py no no True Interestingly enough this particular test issue was only affecting Python 3.5+ before 861d684. Why? * This issue appears to be caused by importing green version of a package being followed by importing a non-green version of the same package * When we run tests using nose it first imports the main tests module (tests/__init__.py) which imports eventlet, that imports eventlet.convenience and that then imports eventlet.green.sockt. * Before 861d684 on Python < 3.5 the eventlet.green.socket import mentioned above would fail to import greendns (because of an import cycle) so when running those tests greendns was only being correctly imported *after* the regular dns * Since 861d684 (or on Python 3.5+) the green socket module correctly imports greendns which means that when the regular dns subpackages are being imported in this test file greendns is already imported and the patching issue demonstrated by the code above is in effect The patching/greening weirdness is reported[1] now. Fixes https://github.com/eventlet/eventlet/issues/267 This patch is contributed by Smarkets Limited. [1] https://github.com/eventlet/eventlet/issues/316 |
remove test_import_patched_defaults.patch | (download) |
tests/patcher_test.py |
22 0 + 22 - 0 ! |
removed failing test This test fails in Sid. |
patch out intersphinx.patch | (download) |
doc/conf.py |
2 1 + 1 - 0 ! |
patch out intersphinx Avoids internet access during build |
fix FTBFS test_getaddrinfo.patch | (download) |
tests/greendns_test.py |
18 9 + 9 - 0 ! |
patched test_getaddrinfo due netbase update Asserting udp for ssh introduce test failures with netbase 5.4 because removed ssh (22/udp). This fix changes ssh -> domain, which better suit for test name and allows tcp and udp simultaneously. |
disable_test_server_connection_timeout_exception.patch | (download) |
tests/wsgi_test.py |
10 5 + 5 - 0 ! |
disable test_server_connection_timeout_exception() As per the bug report, the test is non-deterministic. Therefore, remove it it. |