Closed pale-emperor closed 2 years ago
Have you tried running these tests on current master
of tempesta-test
? Because with the latest changes to the framework all access_log
test section works just fine:
Running functional tests...
----------------------------------------------------------------------
test_frang (access_log.test_access_log.AccessLogFrang) ... ok
test_success_path_http1x (access_log.test_access_log.AccessLogTest) ... ok
test_uri_truncate (access_log.test_access_log.AccessLogTest) ... ok
test_tempesta (access_log.test_access_log_h2.FrangTest) ... ok
test_tempesta (access_log.test_access_log_h2.Response200Test) ... ok
test_tempesta (access_log.test_access_log_h2.Response204Test) ... ok
test_tempesta (access_log.test_access_log_h2.Response302Test) ... ok
test_tempesta (access_log.test_access_log_h2.Response404Test) ... ok
test_tempesta (access_log.test_access_log_h2.Response500Test) ... ok
test_tempesta (access_log.test_access_log_h2.TruncateUriTest) ... ok
----------------------------------------------------------------------
Ran 10 tests in 21.034s
OK
Old code: tester.wait_while_busy -> client.wait_for_finish() -> client.is_busy() -> self.exit_event
client.run_start -> client.run_start() -> client._run_client -> ok
Old problem was
is_busy - False wait_for_finish - True
In _run_client we got Exception and exit_event.set() was never executed and we get infinite wait_while_busy()