You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test runs for 35 seconds and 20 of them are spent in recv() call which takes timeout=0.5 as a parameter. The problem was discussed in #103 (comment) and #103 (comment) , but with #118 (Debug mode for tests configuration) in mind (the rto parameter for TlsHandshake was introduced to be able to read data from Tempesta in debug mode) it's not easy to fix.
See also comments from commit e88af89 : helpers/remote.py and helpers/analyzer.py also struggle from the timeouts and can be reworked in event-driven fashion.
See and fix also TODO #120 comments around the code.
The text was updated successfully, but these errors were encountered:
'Traffic wasn't captured' in tls.test_tls_integrity.Proxy.test_tcp_segs
test.
Add notes for #120 to fix the timeouts on run_cmd() interface.
Use -n switch for tcpdump to make it run faster.
tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing
is an example of relatively long test and profiling tool (#119) show following statistics:The test runs for 35 seconds and 20 of them are spent in
recv()
call which takestimeout=0.5
as a parameter. The problem was discussed in #103 (comment) and #103 (comment) , but with #118 (Debug mode for tests configuration) in mind (therto
parameter forTlsHandshake
was introduced to be able to read data from Tempesta in debug mode) it's not easy to fix.See also comments from commit e88af89 :
helpers/remote.py
andhelpers/analyzer.py
also struggle from the timeouts and can be reworked in event-driven fashion.See and fix also
TODO #120
comments around the code.The text was updated successfully, but these errors were encountered: