-
Notifications
You must be signed in to change notification settings - Fork 4
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
Tests for #1061 and #1535 issue #195
Conversation
Fixed misprint in README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job, but some more work is required
At this point I have finished all subtasks and known comments. Except this one:
However @byko3y promised to help with it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found the cause of exception.
self.connections.append(forward_conn) | ||
forward_conn.create_socket(socket.AF_INET, socket.SOCK_STREAM) | ||
forward_conn.bind((self.listen_host, 0)) | ||
forward_conn.connect((self.forward_host, self.forward_port)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When testing suite and Tempesta FW are on different hosts, so following thing happens:
forward_conn.bind(('127.0.0.1', 0))
forward_conn.connect(('192.168.122.160', 443))
Which fails with EINVAL on my setup. Manually hardcoding the forward_conn.bind(('192.168.122.1', 0))
fixes the problem.
Also, for some reason the problematic code is triggered by very few tests, particulary malformed.test_chunking_example.CorrectHeadersTest.test_ssl
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@byko3y
Thank you very much!
Also, for some reason the problematic code is triggered by very few tests
Because it is too new tool
@byko3y |
@krizhanovsky There is some problem with example test |
Revision 3cdc3b2:
|
@byko3y Thank you! |
Seems like TLS-related failures were already existing in master branch: ./run_tests.py tls.test_tls_cert
|
So the fault was inherited rather than introduced, and shuold not prevent to merge the PR. |
The fault #195 (comment) #195 (comment) moved into issue #204 |
cache/test_purge_resp_hch.py
Outdated
# to None to check that request is missing | ||
deproxy_srv = self.get_server('deproxy') | ||
deproxy_srv.segment_size = chunksize | ||
#print (deproxy_srv.response) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is still a commented out print()
:) Why don't you use the standard debug printing from the framework?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Print produces more focused informaion than huge debug printing from framework :)
This print is not needed more, I'll delete it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good and huge work! Finally it's good to merge.
This commit closes issue #115 |
The tests include:
decribed there
It seems that the tests partialy covers issue #115.