From c6cad84c9db9ff8205dd1795dc0e1fd801ee13d0 Mon Sep 17 00:00:00 2001 From: Thibault Charbonnier Date: Mon, 11 Sep 2023 11:30:51 -0700 Subject: [PATCH] tests(openresty) disable a test with Valgrind mode Attempted to be re-enabled in #408 but unfortunately the nature of the test makes it flaky in Valgrind CI. --- t/04-openresty/lua-bridge/003-proxy_wasm_lua_resolver_timeouts.t | 1 + 1 file changed, 1 insertion(+) diff --git a/t/04-openresty/lua-bridge/003-proxy_wasm_lua_resolver_timeouts.t b/t/04-openresty/lua-bridge/003-proxy_wasm_lua_resolver_timeouts.t index 1d50b0437..19da85e83 100644 --- a/t/04-openresty/lua-bridge/003-proxy_wasm_lua_resolver_timeouts.t +++ b/t/04-openresty/lua-bridge/003-proxy_wasm_lua_resolver_timeouts.t @@ -105,6 +105,7 @@ Using a non-local resolver lua-resty-dns-resolver client timeout Behaves strangely on GHA Valgrind. Seems fine locally. Will run with TEST_NGINX_USE_VALGRIND_ALL. +--- skip_valgrind: 5 --- load_nginx_modules: ngx_http_echo_module --- main_config eval qq{