From cdafdf017eec36c3943b53383fe7c558fee020f5 Mon Sep 17 00:00:00 2001 From: Azat Khuzhin Date: Wed, 2 Sep 2015 17:49:41 +0300 Subject: [PATCH] test/regress_ssl: check events fd/pending after timeout triggered In this case client can't connect to server, and this bring to the front some bugs with assigning on already added events (because of ```fd_is_set``` stuff), for more info see #258, since this is the reproducible for it. --- test/regress_ssl.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/regress_ssl.c b/test/regress_ssl.c index 628d56dd..5872c729 100644 --- a/test/regress_ssl.c +++ b/test/regress_ssl.c @@ -614,6 +614,9 @@ struct testcase_t ssl_testcases[] = { { "bufferevent_socketpair_timeout", regress_bufferevent_openssl, TT_ISOLATED, &basic_setup, T(REGRESS_OPENSSL_SOCKETPAIR | REGRESS_OPENSSL_TIMEOUT) }, + { "bufferevent_socketpair_timeout_freed_fd", regress_bufferevent_openssl, + TT_ISOLATED, &basic_setup, + T(REGRESS_OPENSSL_SOCKETPAIR | REGRESS_OPENSSL_TIMEOUT | REGRESS_OPENSSL_FREED | REGRESS_OPENSSL_FD) }, #undef T { "bufferevent_connect", regress_bufferevent_openssl_connect, -- 2.50.1