diff proxy_cache_revalidate.t @ 790:dfd214db57f4

Tests: adjusted proxy_cache_revalidate.t timeouts. Two adjacent requests may not fit in 1s caching time on slow hosts.
author Sergey Kandaurov <pluknet@nginx.com>
date Wed, 25 Nov 2015 15:53:08 +0300
parents 2cd00179f4b2
children e9064d691790
line wrap: on
line diff
--- a/proxy_cache_revalidate.t
+++ b/proxy_cache_revalidate.t
@@ -47,7 +47,7 @@ http {
             proxy_pass    http://127.0.0.1:8081;
             proxy_cache   one;
 
-            proxy_cache_valid  200 404  1s;
+            proxy_cache_valid  200 404  2s;
 
             add_header X-Cache-Status $upstream_cache_status;
         }
@@ -104,7 +104,7 @@ like(http_get('/t3'), qr/SEE/, 'cache be
 
 # wait for a while for cached responses to expire
 
-select undef, undef, undef, 2.5;
+select undef, undef, undef, 3.5;
 
 # 1st document isn't modified, and should be revalidated on first request
 # (a 304 status code will appear in backend's logs), then cached again
@@ -148,7 +148,7 @@ unlike(http_get('/201'), qr/X-If-Modifie
 
 # wait for a while for a cached 404 response to expire
 
-select undef, undef, undef, 2.5;
+select undef, undef, undef, 3.5;
 
 # check that conditional requests are not used to revalidate 404 response