Commit e6b09d53 authored by Poul-Henning Kamp's avatar Poul-Henning Kamp

Make this testcase a bit more predictable.

I am not convinced this test-case is really necessary, since a
similar and much cheaper check is already in place in the
wrk_herdtimer_thread() function.




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5465 d4fa192b-c00b-0410-8231-f00ffab90ce4
parent a0e1f24f
...@@ -5,9 +5,10 @@ test "Test that errno is thread-local" ...@@ -5,9 +5,10 @@ test "Test that errno is thread-local"
server s1 { server s1 {
rxreq rxreq
txresp txresp -bodylen 1
sema r1 sync 2
rxreq rxreq
txresp txresp -bodylen 2
} -start } -start
varnish v1 -vcl+backend { varnish v1 -vcl+backend {
...@@ -48,9 +49,6 @@ varnish v1 -vcl+backend { ...@@ -48,9 +49,6 @@ varnish v1 -vcl+backend {
char buf[16]; char buf[16];
int fd; int fd;
/* make sure "one" has done its open */
sleep(1);
fd = open("/dev/null", O_RDONLY); fd = open("/dev/null", O_RDONLY);
sprintf(buf, "%d", errno); sprintf(buf, "%d", errno);
...@@ -75,6 +73,7 @@ client c1 { ...@@ -75,6 +73,7 @@ client c1 {
} -start } -start
client c2 { client c2 {
sema r1 sync 2
txreq -url "/two" -hdr "Client: two" txreq -url "/two" -hdr "Client: two"
rxresp rxresp
expect resp.status == 200 expect resp.status == 200
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment