-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test failures on master #454
Comments
This is with tornado==3.1.1? |
Yep tornado 3.1.1, cpython 2.7.8 |
I'm all for fixing flakey tests, but I usually don't bother dropping what I'm doing unless it's happening like >10-20% of the time. I definitely welcome any effort here though. |
@kevinburke Is this still an issue? |
Here are some more On Travis test_ssl_correct_system_time raised the following warning (and failed) 2 out of 3 times on Python 3.4: {message : ResourceWarning("unclosed <ssl.SSLSocket fd=64, family=AddressFamily.AF_INET6, type=SocketType.SOCK_STREAM, proto=6, laddr=('::1', 41582, 0, 0), raddr=('::1', 59505, 0, 0)>",), category : 'ResourceWarning', filename : '/opt/python/3.4.1/lib/python3.4/socket.py', lineno : 266, line : None} Locally this proxy test fails 3 out of 10 times or so:
|
confirmed. which has this second; test_ssl_wrong_system_time. Appears some form of regression under py3.4? awaiting a fix. |
❤️ Gentoo; 💩 this bug. Hmm. |
This issue is probably outdated. Closing for now. |
Running on a Mac, 10.9, with the following command
Some of the failures are below.
ProtocolError not raised (got this one twice):
Not sure what r.data actually was:
Connection failed:
Another one
The server from the same error
This is the result of running the tests maybe 100 times, while connected to a stable wifi network. Occasionally I also see
No handlers could be found for logger "tornado.access"
.The text was updated successfully, but these errors were encountered: