Detailed Test Report for ngx_lua in linux i386 (wv)

Summary
LuaJIT
OpenSSL
Compilation Error
Unexpected Failures
Expected Failures
Warnings

Summary

Commit	Testing Time	Unexpected Failures	Expected Failures	Files	Tests	Elapsed Time
ee47e55e	2019-02-24 06:09:40 GMT	87	108	199	20526	17926 sec

LuaJIT

LuaJIT 2.1.0-beta3, commit 864c72e

OpenSSL

OpenSSL 1.1.0j 20 Nov 2018

Compilation Errors

Unexpected Failures

File	Name	Details
010-request_body.t	ERROR: client socket timed out - TEST 10: on disk request body	'
010-request_body.t	TEST 10: on disk request body - status code ok	got: '' expected: '200'
010-request_body.t	ERROR: client socket timed out - TEST 10: on disk request body	'
010-request_body.t	TEST 10: on disk request body - status code ok	got: '' expected: '200'
020-subrequest.t	ERROR: client socket timed out - TEST 67: leafo test case 2 for assertion failures	'
020-subrequest.t	TEST 67: leafo test case 2 for assertion failures - status code ok	got: '' expected: '200'
020-subrequest.t	TEST 67: leafo test case 2 for assertion failures - response_body - response is expected (repeated req 0, req 0)	@@ -1,3 +0,0 @@ -hello -hello -hello '
020-subrequest.t	ERROR: client socket timed out - TEST 67: leafo test case 2 for assertion failures	'
020-subrequest.t	TEST 67: leafo test case 2 for assertion failures - status code ok	got: '' expected: '200'
020-subrequest.t	TEST 67: leafo test case 2 for assertion failures - response_body - response is expected (repeated req 1, req 0)	@@ -1,3 +0,0 @@ -hello -hello -hello '
023-rewrite/tcp-socket.t	TEST 4: with resolver - response_body - response is expected (repeated req 0, req 0)	got: ..."received: Date: Sun, 24 Feb 2019 13:00:00 GMT\x{0a}"... length: 125 expected: ..."received: Server: openresty\x{0a}"... length: 107 strings begin to differ at char 90 (line 4 column 23)
023-rewrite/tcp-socket.t	TEST 4: with resolver - response_body - response is expected (repeated req 1, req 0)	got: ..."received: Date: Sun, 24 Feb 2019 13:00:01 GMT\x{0a}"... length: 125 expected: ..."received: Server: openresty\x{0a}"... length: 107 strings begin to differ at char 90 (line 4 column 23)
023-rewrite/uthread-exit.t	TEST 6: exit in user thread (entry thread is still pending on the DNS resolver for ngx.socket.udp) - response_body - response is expected (repeated req 1, req 0)	@@ -1,3 +1,4 @@ before hello in thread after +end '
023-rewrite/uthread-spawn.t	ERROR: client socket timed out - TEST 25: multiple user threads + subrequests returning 404 remotely (no wait)	'
023-rewrite/uthread-spawn.t	TEST 25: multiple user threads + subrequests returning 404 remotely (no wait) - status code ok	got: '' expected: '200'
023-rewrite/uthread-spawn.t	TEST 25: multiple user threads + subrequests returning 404 remotely (no wait) - response_body - response is expected (repeated req 0, req 0)	@@ -1,6 +0,0 @@ -ok -status: 404 -status: 404 -status: 404 -status: 404 -status: 404 '
023-rewrite/uthread-spawn.t	ERROR: client socket timed out - TEST 25: multiple user threads + subrequests returning 404 remotely (no wait)	'
023-rewrite/uthread-spawn.t	TEST 25: multiple user threads + subrequests returning 404 remotely (no wait) - status code ok	got: '' expected: '200'
023-rewrite/uthread-spawn.t	TEST 25: multiple user threads + subrequests returning 404 remotely (no wait) - response_body - response is expected (repeated req 1, req 0)	@@ -1,6 +0,0 @@ -ok -status: 404 -status: 404 -status: 404 -status: 404 -status: 404 '
024-access/uthread-exit.t	TEST 6: exit in user thread (entry thread is still pending on the DNS resolver for ngx.socket.udp) - response_body - response is expected (repeated req 1, req 0)	@@ -1,3 +1,4 @@ before hello in thread after +end '
028-req-header.t	ERROR: client socket timed out - TEST 28: clear_header() does not duplicate subsequent headers (old bug)	'
028-req-header.t	TEST 28: clear_header() does not duplicate subsequent headers (old bug) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 28: clear_header() does not duplicate subsequent headers (old bug) - response_body_like - response is expected ()	'' doesn't match '(?^:Bah: bah\r Test-Header: 1\r Foo1: foo1\r Foo2: foo2\r Foo3: foo3\r Foo4: foo4\r Foo5: foo5\r Foo6: foo6\r Foo7: foo7\r Foo8: foo8\r Foo9: foo9\r Foo10: foo10\r Foo11: foo11\r Foo12: foo12\r Foo13: foo13\r Foo14: foo14\r Foo15: foo15\r Foo16: foo16\r Foo17: foo17\r Foo18: foo18\r Foo19: foo19\r Foo20: foo20\r Foo21: foo21\r Foo22: foo22\r )'
028-req-header.t	ERROR: client socket timed out - TEST 28: clear_header() does not duplicate subsequent headers (old bug)	'
028-req-header.t	TEST 28: clear_header() does not duplicate subsequent headers (old bug) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 28: clear_header() does not duplicate subsequent headers (old bug) - response_body_like - response is expected ()	'' doesn't match '(?^:Bah: bah\r Test-Header: 1\r Foo1: foo1\r Foo2: foo2\r Foo3: foo3\r Foo4: foo4\r Foo5: foo5\r Foo6: foo6\r Foo7: foo7\r Foo8: foo8\r Foo9: foo9\r Foo10: foo10\r Foo11: foo11\r Foo12: foo12\r Foo13: foo13\r Foo14: foo14\r Foo15: foo15\r Foo16: foo16\r Foo17: foo17\r Foo18: foo18\r Foo19: foo19\r Foo20: foo20\r Foo21: foo21\r Foo22: foo22\r )'
028-req-header.t	ERROR: client socket timed out - TEST 35: clear input header (just more than 21 headers)	'
028-req-header.t	TEST 35: clear input header (just more than 21 headers) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 35: clear input header (just more than 21 headers) - response_body - response is expected (repeated req 0, req 0)	@@ -1,43 +0,0 @@ -GET /back HTTP/1.0 -Host: foo -Connection: close -User-Agent: curl -Bah: bah -A: a -B: b -C: c -D: d -E: e -F: f -G: g -H: h -I: i -J: j -K: k -L: l -M: m -N: n -O: o -P: p -foo-1: 1 -foo-2: 2 -foo-3: 3 -foo-4: 4 -foo-5: 5 -foo-6: 6 -foo-7: 7 -foo-8: 8 -foo-9: 9 -foo-10: 10 -foo-11: 11 -foo-12: 12 -foo-13: 13 -foo-14: 14 -foo-15: 15 -foo-16: 16 -foo-17: 17 -foo-18: 18 -foo-19: 19 -foo-20: 20 -foo-21: 21 - '
028-req-header.t	ERROR: client socket timed out - TEST 35: clear input header (just more than 21 headers)	'
028-req-header.t	TEST 35: clear input header (just more than 21 headers) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 35: clear input header (just more than 21 headers) - response_body - response is expected (repeated req 1, req 0)	@@ -1,43 +0,0 @@ -GET /back HTTP/1.0 -Host: foo -Connection: close -User-Agent: curl -Bah: bah -A: a -B: b -C: c -D: d -E: e -F: f -G: g -H: h -I: i -J: j -K: k -L: l -M: m -N: n -O: o -P: p -foo-1: 1 -foo-2: 2 -foo-3: 3 -foo-4: 4 -foo-5: 5 -foo-6: 6 -foo-7: 7 -foo-8: 8 -foo-9: 9 -foo-10: 10 -foo-11: 11 -foo-12: 12 -foo-13: 13 -foo-14: 14 -foo-15: 15 -foo-16: 16 -foo-17: 17 -foo-18: 18 -foo-19: 19 -foo-20: 20 -foo-21: 21 - '
028-req-header.t	ERROR: client socket timed out - TEST 33: clear input header (just more than 20 headers, and add more)	'
028-req-header.t	TEST 33: clear input header (just more than 20 headers, and add more) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 33: clear input header (just more than 20 headers, and add more) - response_body - response is expected (repeated req 0, req 0)	@@ -1,43 +0,0 @@ -GET /back HTTP/1.0 -Host: foo -Connection: close -User-Agent: curl -A: a -B: b -C: c -D: d -E: e -F: f -G: g -H: h -I: i -J: j -K: k -L: l -M: m -N: n -O: o -P: p -Q: q -foo-1: 1 -foo-2: 2 -foo-3: 3 -foo-4: 4 -foo-5: 5 -foo-6: 6 -foo-7: 7 -foo-8: 8 -foo-9: 9 -foo-10: 10 -foo-11: 11 -foo-12: 12 -foo-13: 13 -foo-14: 14 -foo-15: 15 -foo-16: 16 -foo-17: 17 -foo-18: 18 -foo-19: 19 -foo-20: 20 -foo-21: 21 - '
028-req-header.t	ERROR: client socket timed out - TEST 33: clear input header (just more than 20 headers, and add more)	'
028-req-header.t	TEST 33: clear input header (just more than 20 headers, and add more) - status code ok	got: '' expected: '200'
028-req-header.t	TEST 33: clear input header (just more than 20 headers, and add more) - response_body - response is expected (repeated req 1, req 0)	@@ -1,43 +0,0 @@ -GET /back HTTP/1.0 -Host: foo -Connection: close -User-Agent: curl -A: a -B: b -C: c -D: d -E: e -F: f -G: g -H: h -I: i -J: j -K: k -L: l -M: m -N: n -O: o -P: p -Q: q -foo-1: 1 -foo-2: 2 -foo-3: 3 -foo-4: 4 -foo-5: 5 -foo-6: 6 -foo-7: 7 -foo-8: 8 -foo-9: 9 -foo-10: 10 -foo-11: 11 -foo-12: 12 -foo-13: 13 -foo-14: 14 -foo-15: 15 -foo-16: 16 -foo-17: 17 -foo-18: 18 -foo-19: 19 -foo-20: 20 -foo-21: 21 - '
058-tcp-socket.t	TEST 4: with resolver - response_body - response is expected (repeated req 0, req 0)	@@ -1,4 +1,4 @@ connected: 1 request sent: 56 first line received: HTTP/1.1 200 OK -second line received: Server: openresty +second line received: Date: Sun, 24 Feb 2019 14:43:24 GMT '
058-tcp-socket.t	TEST 4: with resolver - response_body - response is expected (repeated req 1, req 0)	@@ -1,4 +1,4 @@ connected: 1 request sent: 56 first line received: HTTP/1.1 200 OK -second line received: Server: openresty +second line received: Date: Sun, 24 Feb 2019 14:43:25 GMT '
068-socket-keepalive.t	TEST 47: conn queuing: resume connect operation if resumed connect failed (connection refused) - response_body - response is expected (repeated req 0, req 0)	@@ -1,3 +1,3 @@ -connection refused +timeout connected in uthread ok '
082-body-filter.t	ERROR: client socket timed out - TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy)	'
082-body-filter.t	TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy) - status code ok	got: '' expected: '200'
082-body-filter.t	TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy) - response_body - response is expected (repeated req 0, req 0)	got: '' expected: '[aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb]'
082-body-filter.t	ERROR: client socket timed out - TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy)	'
082-body-filter.t	TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy) - status code ok	got: '' expected: '200'
082-body-filter.t	TEST 16: fully buffered output (string scalar, buffering to disk by ngx_proxy) - response_body - response is expected (repeated req 1, req 0)	got: '' expected: '[aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb]'
093-uthread-spawn.t	ERROR: client socket timed out - TEST 29: multiple user threads + subrequests returning 404 remotely (wait)	'
093-uthread-spawn.t	TEST 29: multiple user threads + subrequests returning 404 remotely (wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 29: multiple user threads + subrequests returning 404 remotely (wait) - response_body - response is expected (repeated req 0, req 0)	@@ -1,6 +0,0 @@ -1: 404 -2: 404 -3: 404 -4: 404 -5: 404 -ok '
093-uthread-spawn.t	ERROR: client socket timed out - TEST 29: multiple user threads + subrequests returning 404 remotely (wait)	'
093-uthread-spawn.t	TEST 29: multiple user threads + subrequests returning 404 remotely (wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 29: multiple user threads + subrequests returning 404 remotely (wait) - response_body - response is expected (repeated req 1, req 0)	@@ -1,6 +0,0 @@ -1: 404 -2: 404 -3: 404 -4: 404 -5: 404 -ok '
093-uthread-spawn.t	ERROR: client socket timed out - TEST 26: multiple user threads + subrequests returning 404 remotely (no wait)	'
093-uthread-spawn.t	TEST 26: multiple user threads + subrequests returning 404 remotely (no wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 26: multiple user threads + subrequests returning 404 remotely (no wait) - response_body - response is expected (repeated req 0, req 0)	@@ -1,6 +0,0 @@ -ok -status: 404 -status: 404 -status: 404 -status: 404 -status: 404 '
093-uthread-spawn.t	ERROR: client socket timed out - TEST 26: multiple user threads + subrequests returning 404 remotely (no wait)	'
093-uthread-spawn.t	TEST 26: multiple user threads + subrequests returning 404 remotely (no wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 26: multiple user threads + subrequests returning 404 remotely (no wait) - response_body - response is expected (repeated req 1, req 0)	@@ -1,6 +0,0 @@ -ok -status: 404 -status: 404 -status: 404 -status: 404 -status: 404 '
093-uthread-spawn.t	ERROR: client socket timed out - TEST 30: multiple user threads + subrequests remotely (wait)	'
093-uthread-spawn.t	TEST 30: multiple user threads + subrequests remotely (wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 30: multiple user threads + subrequests remotely (wait) - response_body - response is expected (repeated req 0, req 0)	@@ -1,21 +0,0 @@ -1: 200 -2: 200 -3: 200 -4: 200 -5: 200 -6: 200 -7: 200 -8: 200 -9: 200 -10: 200 -11: 200 -12: 200 -13: 200 -14: 200 -15: 200 -16: 200 -17: 200 -18: 200 -19: 200 -20: 200 -ok '
093-uthread-spawn.t	ERROR: client socket timed out - TEST 30: multiple user threads + subrequests remotely (wait)	'
093-uthread-spawn.t	TEST 30: multiple user threads + subrequests remotely (wait) - status code ok	got: '' expected: '200'
093-uthread-spawn.t	TEST 30: multiple user threads + subrequests remotely (wait) - response_body - response is expected (repeated req 1, req 0)	@@ -1,21 +0,0 @@ -1: 200 -2: 200 -3: 200 -4: 200 -5: 200 -6: 200 -7: 200 -8: 200 -9: 200 -10: 200 -11: 200 -12: 200 -13: 200 -14: 200 -15: 200 -16: 200 -17: 200 -18: 200 -19: 200 -20: 200 -ok '
094-uthread-exit.t	TEST 6: exit in user thread (entry thread is still pending on the DNS resolver for ngx.socket.udp) - response_body - response is expected (repeated req 1, req 0)	@@ -1,3 +1,4 @@ before hello in thread after +end '
109-timer-hup.t	ERROR: client socket timed out - TEST 7: HUP reload should abort pending timers (fuzz test)	'
109-timer-hup.t	TEST 7: HUP reload should abort pending timers (fuzz test) - response_body - response is expected (repeated req 0, req 0)	got: 'Transfer-E' expected: 'ok '
109-timer-hup.t	ERROR: client socket timed out - TEST 7: HUP reload should abort pending timers (fuzz test)	'
109-timer-hup.t	TEST 7: HUP reload should abort pending timers (fuzz test) - response_body - response is expected (repeated req 1, req 0)	got: 'Transfer-' expected: 'ok '
124-init-worker.t	TEST 13: cosocket with resolver - response_body - response is expected (repeated req 0, req 0)	@@ -2,4 +2,4 @@ connected: 1 request sent: 56 first line received: HTTP/1.1 200 OK -second line received: Server: openresty +second line received: Date: Sun, 24 Feb 2019 16:19:55 GMT '
145-shdict-list.t	ERROR: client socket timed out - TEST 15: list removed: expired	'
145-shdict-list.t	TEST 15: list removed: expired - status code ok	got: '' expected: '200'
145-shdict-list.t	TEST 15: list removed: expired - response_body - response is expected (repeated req 0, req 0)	@@ -1,4 +0,0 @@ -max - 1 matched keys length: true -keys all expired, left number: 0 -loop again, max matched: true -loop again, max matched: true '
145-shdict-list.t	ERROR: client socket timed out - TEST 16: list removed: forcibly	'
145-shdict-list.t	TEST 16: list removed: forcibly - status code ok	got: '' expected: '200'
145-shdict-list.t	TEST 16: list removed: forcibly - response_body - response is expected (repeated req 0, req 0)	@@ -1,3 +0,0 @@ -two == number 2: true -no one left: 0 -two == number 2: true '
147-tcp-socket-timeouts.t	TEST 1: sanity - response_body_like - response is expected (failed to send request: timeout)	'failed to send request: timeout ' doesn't match '(?^s:received: foo )'
147-tcp-socket-timeouts.t	TEST 1: sanity - pattern "[error]" should not match any line in error.log but matches line "2019/02/24 16:43:56 [error] 26840\#0: *1 lua tcp socket write timed out, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"" (req 0)	2019/02/24 16:43:56 [debug] 26840\#0: 1 lua tcp socket handle write error 2019/02/24 16:43:56 [debug] 26840\#0: 1 lua tcp socket waking up the current request 2019/02/24 16:43:56 [debug] 26840\#0: 1 lua tcp operation done, resuming lua thread 2019/02/24 16:43:56 [debug] 26840\#0: 1 lua tcp socket calling prepare retvals handler 081528F6, u:049DA6F8 2019/02/24 16:43:56 [debug] 26840\#0: 1 lua tcp socket send return value handler 2019/02/24 16:43:56 [debug] 26840\#0: 1 poll del event: fd:8 ev:4 2019/02/24 16:43:56 [debug] 26840\#0: 1 poll del index: 3 2019/02/24 16:43:56 [debug] 26840\#0: 1 delete posted event 049D5BD0 2019/02/24 16:43:56 [debug] 26840\#0: *1 lua run thread, top:8 c:1 '
147-tcp-socket-timeouts.t	TEST 7: different timeout with duplex socket (settimeouts) - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1 @@ -received: ok +failed to send request: timeout -failed to receive a line: closed [] '
147-tcp-socket-timeouts.t	TEST 7: different timeout with duplex socket (settimeouts) - pattern "[error]" should not match any line in error.log but matches line "2019/02/24 16:44:27 [error] 26845\#0: *1 lua tcp socket write timed out, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"" (req 0)	2019/02/24 16:44:27 [debug] 26845\#0: 1 lua tcp socket handle write error 2019/02/24 16:44:27 [debug] 26845\#0: 1 lua tcp socket waking up the current request 2019/02/24 16:44:27 [debug] 26845\#0: 1 lua tcp operation done, resuming lua thread 2019/02/24 16:44:27 [debug] 26845\#0: 1 lua tcp socket calling prepare retvals handler 081528F6, u:049DB7F0 2019/02/24 16:44:27 [debug] 26845\#0: 1 lua tcp socket send return value handler 2019/02/24 16:44:27 [debug] 26845\#0: 1 poll del event: fd:8 ev:4 2019/02/24 16:44:27 [debug] 26845\#0: 1 poll del index: 3 2019/02/24 16:44:27 [debug] 26845\#0: 1 delete posted event 049D67E0 2019/02/24 16:44:27 [debug] 26845\#0: *1 lua run thread, top:8 c:1 '
147-tcp-socket-timeouts.t	TEST 2: read timeout - response_body_like - response is expected (failed to send request: timeout)	'failed to send request: timeout ' doesn't match '(?^s:failed to receive a line: timeout \[\] )'
147-tcp-socket-timeouts.t	TEST 2: read timeout - pattern "lua tcp socket read timed out" should match a line in error.log (req 0)
147-tcp-socket-timeouts.t	TEST 6: different timeout with duplex socket (settimeout) - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1 @@ -received: ok +failed to send request: timeout -failed to receive a line: closed [] '
147-tcp-socket-timeouts.t	TEST 6: different timeout with duplex socket (settimeout) - pattern "lua tcp socket read timed out" should match a line in error.log (req 0)
147-tcp-socket-timeouts.t	TEST 6: different timeout with duplex socket (settimeout) - pattern "failed to receive data: timeout" should match a line in error.log (req 0)
151-initby-hup.t	TEST 5: error in init after HUP, not reloaded but foo have changed. - response_body - response is expected (repeated req 0, req 0)	got: "hello, FOO\x{0a}" length: 11 expected: "foo have changed\x{0a}" length: 17 strings begin to differ at char 1 (line 1 column 1)

Expected Failures

File	Name	Details
005-exit.t	TEST 24: exit 444 in header filter - status code ok	got: '' expected: '444'
005-exit.t	TEST 22: exit 201 in header filter - status code ok	got: '' expected: '201'
005-exit.t	TEST 21: exit 403 in header filter - status code ok	got: '' expected: '403'
005-exit.t	TEST 21: exit 403 in header filter - response_body_like - response is expected ()	'' doesn't match '(?^s:403 Forbidden)'
005-exit.t	TEST 21: exit 403 in header filter - status code ok	got: '' expected: '403'
005-exit.t	TEST 21: exit 403 in header filter - response_body_like - response is expected ()	'' doesn't match '(?^s:403 Forbidden)'
005-exit.t	TEST 23: exit both in header filter and content handler - status code ok	got: '' expected: '201'
020-subrequest.t	ERROR: client socket timed out - TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size)	'
020-subrequest.t	TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size) - status code ok	got: '' expected: '200'
020-subrequest.t	TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size) - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +0,0 @@ -hello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello world -hello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello world '
020-subrequest.t	ERROR: client socket timed out - TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size)	'
020-subrequest.t	TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size) - status code ok	got: '' expected: '200'
020-subrequest.t	TEST 54: forwarding in-file request bodies to multiple subrequests (exceeding client_body_buffer_size) - response_body - response is expected (repeated req 1, req 0)	@@ -1,2 +0,0 @@ -hello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello world -hello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello worldhello world '
023-rewrite/req-socket.t	TEST 7: Expect & 100 Continue - status code ok	got: '200' expected: '100'
023-rewrite/req-socket.t	TEST 7: Expect & 100 Continue - response_body_like - response is expected (failed to get the request socket: test expect failed)	'failed to get the request socket: test expect failed ' doesn't match '(?^s:\breceived: hello\b.*?\breceived: worl\b)'
023-rewrite/req-socket.t	TEST 7: Expect & 100 Continue - status code ok	got: '200' expected: '100'
023-rewrite/req-socket.t	TEST 7: Expect & 100 Continue - response_body_like - response is expected (failed to get the request socket: test expect failed)	'failed to get the request socket: test expect failed ' doesn't match '(?^s:\breceived: hello\b.*?\breceived: worl\b)'
025-codecache.t	TEST 29: cosocket connection pool timeout (after Lua VM destroys) - pattern "(?^:\blua tcp socket keepalive: free connection pool [0-9A-F]+ for "127.0.0.1:)" should match a line in error.log (req 0)
025-codecache.t	TEST 29: cosocket connection pool timeout (after Lua VM destroys) - pattern "lua tcp socket keepalive max idle timeout" should not match any line in error.log but matches line "2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive max idle timeout" (req 0)	2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive close handler: fd:8 2019/02/24 13:30:11 [debug] 24254\#0: poll del event: fd:8 ev:1 2019/02/24 13:30:11 [debug] 24254\#0: reusable connection: 0 2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive: free connection pool for "127.0.0.1:11211" 2019/02/24 13:30:11 [debug] 24254\#0: posted event 049CD2F0 2019/02/24 13:30:11 [debug] 24254\#0: 1 delete posted event 049CD2F0 2019/02/24 13:30:11 [debug] 24254\#0: 1 http run request: "/t?" 2019/02/24 13:30:11 [debug] 24254\#0: 1 http writer handler: "/t?" 2019/02/24 13:30:11 [debug] 24254\#0: 1 http output filter "/t?" '
025-codecache.t	TEST 29: cosocket connection pool timeout (after Lua VM destroys) - pattern "(?^:\blua tcp socket keepalive: free connection pool [0-9A-F]+ for "127.0.0.1:)" should match a line in error.log (req 1)
025-codecache.t	TEST 29: cosocket connection pool timeout (after Lua VM destroys) - pattern "lua tcp socket keepalive max idle timeout" should not match any line in error.log but matches line "2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive max idle timeout" (req 1)	2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive close handler: fd:8 2019/02/24 13:30:11 [debug] 24254\#0: poll del event: fd:8 ev:1 2019/02/24 13:30:11 [debug] 24254\#0: reusable connection: 0 2019/02/24 13:30:11 [debug] 24254\#0: lua tcp socket keepalive: free connection pool for "127.0.0.1:11211" 2019/02/24 13:30:11 [debug] 24254\#0: posted event 049CD2F0 2019/02/24 13:30:11 [debug] 24254\#0: 1 delete posted event 049CD2F0 2019/02/24 13:30:11 [debug] 24254\#0: 1 http run request: "/t?" 2019/02/24 13:30:11 [debug] 24254\#0: 1 http writer handler: "/t?" 2019/02/24 13:30:11 [debug] 24254\#0: 1 http output filter "/t?" '
025-codecache.t	TEST 29: cosocket connection pool timeout (after Lua VM destroys) - pattern "lua tcp socket keepalive max idle timeout" should not match any line in error.log but matches line "2019/02/24 13:30:12 [debug] 24254\#0: lua tcp socket keepalive max idle timeout" (req 1)	2019/02/24 13:30:12 [debug] 24254\#0: lua tcp socket keepalive close handler: fd:8 2019/02/24 13:30:12 [debug] 24254\#0: poll del event: fd:8 ev:1 2019/02/24 13:30:12 [debug] 24254\#0: reusable connection: 0 2019/02/24 13:30:12 [debug] 24254\#0: lua tcp socket keepalive: free connection pool for "127.0.0.1:11211" 2019/02/24 13:30:12 [debug] 24254\#0: posted event 049CD2F0 2019/02/24 13:30:12 [debug] 24254\#0: 3 delete posted event 049CD2F0 2019/02/24 13:30:12 [debug] 24254\#0: 3 http run request: "/t?" 2019/02/24 13:30:12 [debug] 24254\#0: 3 http writer handler: "/t?" 2019/02/24 13:30:12 [debug] 24254\#0: 3 http output filter "/t?" '
025-codecache.t	TEST 24: lua_max_pending_timers - chained timers (non-zero delay) - not exceeding - pattern "decrementing the reference count for Lua VM: 3" should not match any line in error.log but matches line "2019/02/24 13:30:30 [debug] 24258\#0: lua decrementing the reference count for Lua VM: 3" (req 0)	2019/02/24 13:30:30 [debug] 24258\#0: free: 049F36D0, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3658, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F35E0, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3498, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3330, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F2F98, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F23C8, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: posted event 049CD180 2019/02/24 13:30:30 [debug] 24258\#0: *1 delete posted event 049CD180 '
025-codecache.t	TEST 24: lua_max_pending_timers - chained timers (non-zero delay) - not exceeding - pattern "decrementing the reference count for Lua VM: 3" should not match any line in error.log but matches line "2019/02/24 13:30:30 [debug] 24258\#0: lua decrementing the reference count for Lua VM: 3" (req 1)	2019/02/24 13:30:30 [debug] 24258\#0: free: 049F36D0, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3658, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F35E0, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3498, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F3330, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F2F98, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: free: 049F23C8, unused: 0 2019/02/24 13:30:30 [debug] 24258\#0: posted event 049CD180 2019/02/24 13:30:30 [debug] 24258\#0: *1 delete posted event 049CD180 '
025-codecache.t	TEST 24: lua_max_pending_timers - chained timers (non-zero delay) - not exceeding - pattern "decrementing the reference count for Lua VM: 3" should not match any line in error.log but matches line "2019/02/24 13:30:31 [debug] 24258\#0: lua decrementing the reference count for Lua VM: 3" (req 1)	2019/02/24 13:30:31 [debug] 24258\#0: free: 04A19D90, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A19D18, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A19CA0, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A19B58, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A199F0, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A19658, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: free: 04A18A88, unused: 0 2019/02/24 13:30:31 [debug] 24258\#0: posted event 049CD180 2019/02/24 13:30:31 [debug] 24258\#0: *4 delete posted event 049CD180 '
041-header-filter.t	TEST 41: filter finalize - status code ok	got: '' expected: '302'
041-header-filter.t	TEST 41: filter finalize - response_body_like - response is expected ()	'' doesn't match '(?^s:302 Found)'
041-header-filter.t	TEST 41: filter finalize - status code ok	got: '' expected: '302'
041-header-filter.t	TEST 41: filter finalize - response_body_like - response is expected ()	'' doesn't match '(?^s:302 Found)'
043-shdict.t	nginx: [emerg]	lua_shared_dict "dogs" is already defined as "dogs" in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:26
056-flush.t	TEST 1: flush wait - content - pattern "lua reuse free buf chain, but reallocate memory because 5 >= 0" should match a line in error.log (req 0)
056-flush.t	TEST 1: flush wait - content - pattern "lua reuse free buf chain, but reallocate memory because 5 >= 0" should match a line in error.log (req 1)
056-flush.t	TEST 17: limit_rate - pattern "(?^:lua writes elapsed [12](?:\.\d+)? sec)" should match a line in error.log (req 0)
056-flush.t	TEST 17: limit_rate - pattern "(?^:lua writes elapsed [12](?:\.\d+)? sec)" should match a line in error.log (req 1)
058-tcp-socket.t	TEST 67: receiveany with limited, max is larger than data - response_body - response is expected (repeated req 0, req 0)	got: 'h ' expected: 'hello world '
058-tcp-socket.t	TEST 67: receiveany with limited, max is larger than data - response_body - response is expected (repeated req 1, req 0)	got: 'h ' expected: 'hello world '
058-tcp-socket.t	TEST 64: receiveany method in cosocket - response_body - response is expected (repeated req 0, req 0)	@@ -1,3 +1,14 @@ 1 -22 +2 -hello world +2 +h +e +l +l +o + +w +o +r +l +d '
058-tcp-socket.t	TEST 64: receiveany method in cosocket - response_body - response is expected (repeated req 1, req 0)	@@ -1,3 +1,14 @@ 1 -22 +2 -hello world +2 +h +e +l +l +o + +w +o +r +l +d '
058-tcp-socket.t	TEST 68: receiveany with limited, max is smaller than data - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1,11 @@ -hello w +h -orld +e +l +l +o + +w +o +r +l +d '
058-tcp-socket.t	TEST 68: receiveany with limited, max is smaller than data - response_body - response is expected (repeated req 1, req 0)	@@ -1,2 +1,11 @@ -hello w +h -orld +e +l +l +o + +w +o +r +l +d '
067-req-socket.t	TEST 7: Expect & 100 Continue - status code ok	got: '200' expected: '100'
067-req-socket.t	TEST 7: Expect & 100 Continue - response_body_like - response is expected (failed to get the request socket: test expect failed)	'failed to get the request socket: test expect failed ' doesn't match '(?^s:\breceived: hello\b.*?\breceived: worl\b)'
067-req-socket.t	TEST 7: Expect & 100 Continue - status code ok	got: '200' expected: '100'
067-req-socket.t	TEST 7: Expect & 100 Continue - response_body_like - response is expected (failed to get the request socket: test expect failed)	'failed to get the request socket: test expect failed ' doesn't match '(?^s:\breceived: hello\b.*?\breceived: worl\b)'
067-req-socket.t	TEST 14: successful reread after reading timeout happens (receive -> receive) - response_body - response is expected (repeated req 0, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 11 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: err: timeout, partial: '
067-req-socket.t	TEST 14: successful reread after reading timeout happens (receive -> receive) - response_body - response is expected (repeated req 1, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 11 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: err: timeout, partial: '
067-req-socket.t	TEST 15: successful reread after reading timeout happens (receive -> receiveuntil) - response_body - response is expected (repeated req 0, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 12 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: '
067-req-socket.t	TEST 15: successful reread after reading timeout happens (receive -> receiveuntil) - response_body - response is expected (repeated req 1, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 12 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: '
067-req-socket.t	TEST 16: successful reread after reading timeout happens (receiveuntil -> receive) - response_body - response is expected (repeated req 0, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 12 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: '
067-req-socket.t	TEST 16: successful reread after reading timeout happens (receiveuntil -> receive) - response_body - response is expected (repeated req 1, req 0)	@@ -1,4 +1,4 @@ sent: 65 sent: 12 -received: err: timeout, partial: abc +received: err: timeout, partial: abchello world -received: received: hello world +received: '
068-socket-keepalive.t	TEST 42: conn queuing: set timeout via lua_socket_connect_timeout - pattern "lua tcp socket queued connect timed out, when trying to connect to 127.0.0.1:11211" should match a line in error.log (req 0)
072-conditional-get.t	TEST 3: If-Unmodified-Since false - Can't connect to 127.0.0.1:1984: Connection refused	==25496== Invalid read of size 4 ==25496== at 0x8068236: ngx_chain_update_chains (ngx_buf.c:191) ==25496== by 0x81401EE: ngx_http_lua_output_filter (ngx_http_lua_util.c:629) ==25496== by 0x8140B8A: ngx_http_lua_send_chain_link (ngx_http_lua_util.c:575) ==25496== by 0x8131885: ngx_http_lua_ngx_echo (ngx_http_lua_output.c:233) ==25496== by 0x8131908: ngx_http_lua_ngx_say (ngx_http_lua_output.c:34) ==25496== by 0x406B253: lj_BC_FUNCC (in /opt/luajit-sysm/lib/libluajit-5.1.so.2.1.0) ==25496== by 0x4082095: lua_resume (lj_api.c:1221) ==25496== by 0x81426C0: ngx_http_lua_run_thread (ngx_http_lua_util.c:1084) ==25496== by 0x81465EE: ngx_http_lua_content_by_chunk (ngx_http_lua_contentby.c:122) ==25496== by 0x81466D8: ngx_http_lua_content_handler_inline (ngx_http_lua_contentby.c:312) ==25496== by 0x81461C5: ngx_http_lua_content_handler (ngx_http_lua_contentby.c:224) ==25496== by 0x80A1EEB: ngx_http_core_content_phase (ngx_http_core_module.c:1180) ==25496== by 0x809CE92: ngx_http_core_run_phases (ngx_http_core_module.c:869) ==25496== by 0x809CFA7: ngx_http_handler (ngx_http_core_module.c:852) ==25496== by 0x80A818D: ngx_http_process_request (ngx_http_request.c:1956) ==25496== by 0x80A87E9: ngx_http_process_request_headers (ngx_http_request.c:1381) ==25496== by 0x80A8D33: ngx_http_process_request_line (ngx_http_request.c:1051) ==25496== by 0x80A9408: ngx_http_wait_request_handler (ngx_http_request.c:500) ==25496== by 0x8084FA6: ngx_event_process_posted (ngx_event_posted.c:34) ==25496== by 0x8084961: ngx_process_events_and_timers (ngx_event.c:269) ==25496== by 0x808EC91: ngx_single_process_cycle (ngx_process_cycle.c:333) ==25496== by 0x8064EE4: main (nginx.c:382) ==25496== Address 0x98 is not stack'd, malloc'd or (recently) free'd ==25496== { <insert_a_suppression_name_here> Memcheck:Addr4 fun:ngx_chain_update_chains fun:ngx_http_lua_output_filter fun:ngx_http_lua_send_chain_link fun:ngx_http_lua_ngx_echo fun:ngx_http_lua_ngx_say fun:lj_BC_FUNCC fun:lua_resume fun:ngx_http_lua_run_thread fun:ngx_http_lua_content_by_chunk fun:ngx_http_lua_content_handler_inline fun:ngx_http_lua_content_handler fun:ngx_http_core_content_phase fun:ngx_http_core_run_phases fun:ngx_http_handler fun:ngx_http_process_request fun:ngx_http_process_request_headers fun:ngx_http_process_request_line fun:ngx_http_wait_request_handler fun:ngx_event_process_posted fun:ngx_process_events_and_timers fun:ngx_single_process_cycle fun:main }
072-conditional-get.t	TEST 3: If-Unmodified-Since false - Can't connect to 127.0.0.1:1984: Connection refused	==25496== ==25496== Process terminating with default action of signal 11 (SIGSEGV) ==25496== Access not within mapped region at address 0x98 ==25496== at 0x8068236: ngx_chain_update_chains (ngx_buf.c:191) ==25496== by 0x81401EE: ngx_http_lua_output_filter (ngx_http_lua_util.c:629) ==25496== by 0x8140B8A: ngx_http_lua_send_chain_link (ngx_http_lua_util.c:575) ==25496== by 0x8131885: ngx_http_lua_ngx_echo (ngx_http_lua_output.c:233) ==25496== by 0x8131908: ngx_http_lua_ngx_say (ngx_http_lua_output.c:34) ==25496== by 0x406B253: lj_BC_FUNCC (in /opt/luajit-sysm/lib/libluajit-5.1.so.2.1.0) ==25496== by 0x4082095: lua_resume (lj_api.c:1221) ==25496== by 0x81426C0: ngx_http_lua_run_thread (ngx_http_lua_util.c:1084) ==25496== by 0x81465EE: ngx_http_lua_content_by_chunk (ngx_http_lua_contentby.c:122) ==25496== by 0x81466D8: ngx_http_lua_content_handler_inline (ngx_http_lua_contentby.c:312) ==25496== by 0x81461C5: ngx_http_lua_content_handler (ngx_http_lua_contentby.c:224) ==25496== by 0x80A1EEB: ngx_http_core_content_phase (ngx_http_core_module.c:1180) ==25496== by 0x809CE92: ngx_http_core_run_phases (ngx_http_core_module.c:869) ==25496== by 0x809CFA7: ngx_http_handler (ngx_http_core_module.c:852) ==25496== by 0x80A818D: ngx_http_process_request (ngx_http_request.c:1956) ==25496== by 0x80A87E9: ngx_http_process_request_headers (ngx_http_request.c:1381) ==25496== by 0x80A8D33: ngx_http_process_request_line (ngx_http_request.c:1051) ==25496== by 0x80A9408: ngx_http_wait_request_handler (ngx_http_request.c:500) ==25496== by 0x8084FA6: ngx_event_process_posted (ngx_event_posted.c:34) ==25496== by 0x8084961: ngx_process_events_and_timers (ngx_event.c:269) ==25496== by 0x808EC91: ngx_single_process_cycle (ngx_process_cycle.c:333) ==25496== by 0x8064EE4: main (nginx.c:382) ==25496== If you believe this happened as a result of a stack ==25496== overflow in your program's main thread (unlikely but ==25496== possible), you can try to increase the size of the ==25496== main thread stack using the --main-stacksize= flag. ==25496== The main thread stack size used in this run was 8388608.
072-conditional-get.t	TEST 3: If-Unmodified-Since false - status code ok	got: '' expected: '412'
072-conditional-get.t	TEST 3: If-Unmodified-Since false - response_body_like - response is expected ()	'' doesn't match '(?^s:412 Precondition Failed)'
072-conditional-get.t	TEST 3: If-Unmodified-Since false - pattern "say failed: nginx output filter error" should match a line in error.log (req 0)
072-conditional-get.t	TEST 3: If-Unmodified-Since false - Can't connect to 127.0.0.1:1984: Connection refused (aborted)	'
072-conditional-get.t	TEST 3: If-Unmodified-Since false - status code ok	got: '' expected: '412'
072-conditional-get.t	TEST 3: If-Unmodified-Since false - response_body_like - response is expected ()	'' doesn't match '(?^s:412 Precondition Failed)'
072-conditional-get.t	TEST 3: If-Unmodified-Since false - pattern "say failed: nginx output filter error" should match a line in error.log (req 1)
086-init-by.t	nginx: [error]	init_by_lua error: init_by_lua:2: failed to init
100-client-abort.t	TEST 28: ngx.print - pattern "print failed: nginx output filter error" should match a line in error.log (req 0)
100-client-abort.t	TEST 28: ngx.print - pattern "print failed: nginx output filter error" should match a line in error.log (req 1)
100-client-abort.t	TEST 27: ngx.say - pattern "say failed: nginx output filter error" should match a line in error.log (req 0)
100-client-abort.t	TEST 27: ngx.say - pattern "say failed: nginx output filter error" should match a line in error.log (req 1)
100-client-abort.t	TEST 31: ngx.eof - pattern "eof failed: nginx output filter error" should match a line in error.log (req 0)
100-client-abort.t	TEST 31: ngx.eof - pattern "eof succeeded" should not match any line in error.log but matches line "2019/02/24 15:35:11 [warn] 25981\#0: *1 [lua] content_by_lua(nginx.conf:49):8: eof succeeded, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"" (req 0)	2019/02/24 15:35:11 [debug] 25981\#0: 1 lua resume returned 0 2019/02/24 15:35:11 [debug] 25981\#0: 1 lua light thread ended normally 2019/02/24 15:35:11 [debug] 25981\#0: 1 lua deleting light thread 2019/02/24 15:35:11 [debug] 25981\#0: 1 lua run thread returned 0 2019/02/24 15:35:11 [debug] 25981\#0: 1 http finalize request: 0, "/t?" a:1, c:1 2019/02/24 15:35:11 [debug] 25981\#0: 1 event timer add: 7: 60000:34071708 2019/02/24 15:35:11 [debug] 25981\#0: *1 poll add event: fd:7 ev:4 2019/02/24 15:35:11 [debug] 25981\#0: worker cycle 2019/02/24 15:35:11 [debug] 25981\#0: poll timer: 60000 '
100-client-abort.t	TEST 31: ngx.eof - pattern "eof failed: nginx output filter error" should match a line in error.log (req 1)
100-client-abort.t	TEST 31: ngx.eof - pattern "eof succeeded" should not match any line in error.log but matches line "2019/02/24 15:35:11 [warn] 25981\#0: *2 [lua] content_by_lua(nginx.conf:49):8: eof succeeded, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"" (req 1)	2019/02/24 15:35:11 [debug] 25981\#0: 2 lua resume returned 0 2019/02/24 15:35:11 [debug] 25981\#0: 2 lua light thread ended normally 2019/02/24 15:35:11 [debug] 25981\#0: 2 lua deleting light thread 2019/02/24 15:35:11 [debug] 25981\#0: 2 lua run thread returned 0 2019/02/24 15:35:11 [debug] 25981\#0: 2 http finalize request: 0, "/t?" a:1, c:1 2019/02/24 15:35:11 [debug] 25981\#0: 2 event timer add: 7: 60000:34072052 2019/02/24 15:35:11 [debug] 25981\#0: *2 poll add event: fd:7 ev:4 2019/02/24 15:35:11 [debug] 25981\#0: worker cycle 2019/02/24 15:35:11 [debug] 25981\#0: poll timer: 60000 '
106-timer.t	TEST 9: simple at (sleep in the timer callback) - log_by_lua - pattern "(?^:\[lua\] log_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-6]))" should match a line in error.log (req 0)
106-timer.t	TEST 9: simple at (sleep in the timer callback) - log_by_lua - pattern "(?^:\[lua\] log_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-6]))" should match a line in error.log (req 1)
106-timer.t	TEST 4: simple at (sleep in the timer callback) - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.(?:1[4-9]\|2[0-6]?))" should match a line in error.log (req 0)
106-timer.t	TEST 1: simple at - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6])\d*, context: ngx\.timer, client: \d+\.\d+\.\d+\.\d+, server: 0\.0\.0\.0:\d+)" should match a line in error.log (req 0)
106-timer.t	TEST 30: user args - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6])\d*, context: ngx\.timer)" should match a line in error.log (req 0)
106-timer.t	TEST 2: globals are shared - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 0)
106-timer.t	TEST 2: globals are shared - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 1)
106-timer.t	TEST 3: lua variable sharing via upvalue - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 0)
106-timer.t	TEST 3: lua variable sharing via upvalue - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 1)
106-timer.t	TEST 7: 0 timer - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0(?:[^.]\|\.00))" should match a line in error.log (req 0)
106-timer.t	TEST 7: 0 timer - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0(?:[^.]\|\.00))" should match a line in error.log (req 1)
108-timer-safe.t	TEST 1: simple at - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 0)
108-timer-safe.t	TEST 1: simple at - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6]))" should match a line in error.log (req 1)
108-timer-safe.t	TEST 5: 0 timer - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0(?:[^.]\|\.00))" should match a line in error.log (req 0)
108-timer-safe.t	TEST 5: 0 timer - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0(?:[^.]\|\.00))" should match a line in error.log (req 1)
108-timer-safe.t	TEST 7: simple at (sleep in the timer callback) - log_by_lua - pattern "(?^:\[lua\] log_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-9]\|8[0-6]))" should match a line in error.log (req 0)
108-timer-safe.t	TEST 7: simple at (sleep in the timer callback) - log_by_lua - pattern "(?^:\[lua\] log_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-9]\|8[0-6]))" should match a line in error.log (req 1)
108-timer-safe.t	TEST 2: simple at (sleep in the timer callback) - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-6]))" should match a line in error.log (req 0)
108-timer-safe.t	TEST 2: simple at (sleep in the timer callback) - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:6[4-9]\|7[0-6]))" should match a line in error.log (req 1)
109-timer-hup.t	TEST 7: HUP reload should abort pending timers (fuzz test) - grep_error_log_out (req 0)	got: 'lua found 8182 pending timers ' expected: 'lua found 8191 pending timers '
109-timer-hup.t	TEST 7: HUP reload should abort pending timers (fuzz test) - grep_error_log_out (req 1)	got: 'lua found 8182 pending timers ' expected: 'lua found 8191 pending timers '
109-timer-hup.t	TEST 6: HUP reload should abort pending timers (coroutine + cosocket) - grep_error_log_out (req 0)	got: '' expected: 'lua found 1 pending timers '
126-shdict-frag.t	TEST 9: cannot merge in-used big slabs page (forward) - response_body - response is expected (repeated req 0, req 0)	@@ -2,4 +2,4 @@ failed to safe set baz: no memory found bar: 4000 delete bar -failed to safe set baz: no memory +successfully safe set baz '
132-lua-blocks.t	nginx: [emerg]	Lua code block missing the closing long bracket "]==]" in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:41
132-lua-blocks.t	nginx: [emerg]	Lua code block missing the closing long bracket "]=]" in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:41
132-lua-blocks.t	nginx: [emerg]	Lua code block missing the closing long bracket "]]" in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:41
132-lua-blocks.t	nginx: [emerg]	"events" directive is not allowed here in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:56
139-ssl-cert-by.t	TEST 2: sleep - pattern "(?^:elapsed in ssl cert by lua: 0.(?:09\|1[01])\d+,)" should match a line in error.log (req 0)
142-ssl-session-store.t	nginx: [emerg]	"ssl_session_store_by_lua_block" directive is not allowed here in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:28
142-ssl-session-store.t	TEST 9: inter-operation with ssl_certificate_by_lua - pattern "(?^:elapsed in ssl cert by lua: 0.(?:09\|1[01])\d+,)" should match a line in error.log (req 0)
143-ssl-session-fetch.t	TEST 2: sleep - grep_error_log_out (req 1)	'' doesn't match '(?^:elapsed in ssl fetch session by lua: 0.(?:09\|1[01])\d+,)'
146-malloc-trim.t	TEST 5: malloc_trim() every 2 req, in subreq, big memory usage - grep_error_log_out (req 0)	@@ -1,3 +1,3 @@ -malloc_trim(1) returned 1 +malloc_trim(1) returned 0 -malloc_trim(1) returned 1 +malloc_trim(1) returned 0 -malloc_trim(1) returned 1 +malloc_trim(1) returned 0 '
148-fake-shm-zone.t	nginx: [emerg]	lua_fake_shm "x1" is already defined as "x1" in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:26
152-timer-every.t	TEST 3: lua variable sharing via upvalue - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1,2 @@ registered timer -foo = 6 +foo = 3 '
152-timer-every.t	TEST 3: lua variable sharing via upvalue - response_body - response is expected (repeated req 1, req 0)	@@ -1,2 +1,2 @@ registered timer -foo = 6 +foo = 3 '
152-timer-every.t	TEST 6: memory leak check - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1,2 @@ registered timer -growth1 == growth2: true +growth1 == growth2: false '
152-timer-every.t	TEST 4: create the next timer immediately when timer start running - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1,2 @@ registered timer -foo = 6 +foo = 3 '
152-timer-every.t	TEST 1: simple very - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.0(?:4[4-9]\|5[0-6])\d*, context: ngx\.timer, client: \d+\.\d+\.\d+\.\d+, server: 0\.0\.0\.0:\d+)" should match a line in error.log (req 0)
152-timer-every.t	TEST 1: simple very - pattern "(?^:\[lua\] content_by_lua$nginx\.conf:\d+$:\d+: elapsed: 0\.(?:09\|10)\d*, context: ngx\.timer, client: \d+\.\d+\.\d+\.\d+, server: 0\.0\.0\.0:\d+)" should match a line in error.log (req 0)

Warnings

TEST 37: globals are shared in all requests. - 2019/02/24 11:58:29 [warn] 22879#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 38: user modules using ngx.arg - 2019/02/24 11:59:24 [warn] 22891#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 12:04:30 [warn] 22978#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 29: globals sharing by using _G (header_filter_by_lua*) - 2019/02/24 12:13:01 [warn] 23134#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('t') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 26: globals sharing by using _G - 2019/02/24 12:13:45 [warn] 23142#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('t') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 27: globals sharing by using _G (set_by_lua*) - 2019/02/24 12:14:03 [warn] 23145#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('t') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 30: globals sharing by using _G (body_filter_by_lua*) - 2019/02/24 12:14:18 [warn] 23147#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('t') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 28: globals sharing by using _G (log_by_lua*) - 2019/02/24 12:18:22 [warn] 23155#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('t') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 39: lua_code_cache off + setkeepalive - 2019/02/24 12:19:21 [warn] 23165#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 39: lua_code_cache off + setkeepalive - 2019/02/24 12:19:20 [alert] 23165#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:39
TEST 39: lua_code_cache off + setkeepalive - 2019/02/24 12:19:22 [warn] 23165#0: *4 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 39: lua_code_cache off + setkeepalive - 2019/02/24 12:19:23 [warn] 23165#0: *7 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: set response content-type header - unexpected extra bytes after last chunk in response: "lo\x{0a}"
killing the child process 23377 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23378 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23380 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23383 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23396 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23399 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23402 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23403 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23429 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23430 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23443 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23444 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23449 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 23450 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 4: attempt to use the req socket across request boundary - 2019/02/24 12:49:45 [warn] 23658#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 5: receive until on request_body - receiveuntil(1) on the last byte of the body - 2019/02/24 12:49:50 [warn] 23659#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: pipelined POST requests - 2019/02/24 12:50:05 [warn] 23661#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 12:54:45 [warn] 23733#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: free up the whole connection pool if no active connections - 2019/02/24 12:54:51 [warn] 23734#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 11: sanity (uds) - 2019/02/24 12:56:11 [warn] 23745#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 13: github issue #110: ngx.exit with HTTP_NOT_FOUND causes worker process to exit - 2019/02/24 12:56:27 [warn] 23747#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 36: bad request tries to close - 2019/02/24 12:59:35 [warn] 23792#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 37: bad request tries to set keepalive - 2019/02/24 12:59:49 [warn] 23796#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 19: cannot survive across request boundary (send) - 2019/02/24 13:00:13 [warn] 23800#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 20: cannot survive across request boundary (receive) - 2019/02/24 13:00:43 [warn] 23806#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 35: bad request tries to send - 2019/02/24 13:00:48 [warn] 23809#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 34: bad request tries to receive - 2019/02/24 13:00:53 [warn] 23810#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 21: cannot survive across request boundary (close) - 2019/02/24 13:01:09 [warn] 23823#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 33: bad request tries to connect - 2019/02/24 13:01:28 [warn] 23826#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 38: bad request tries to receiveuntil - 2019/02/24 13:01:49 [warn] 23830#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 30: cosocket connection pool timeout (before Lua VM destroys) - 2019/02/24 13:28:02 [warn] 24227#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 30: cosocket connection pool timeout (before Lua VM destroys) - 2019/02/24 13:28:03 [warn] 24227#0: *3 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 9: code cache explicitly on (affects require) + set_by_lua_file - 2019/02/24 13:28:07 [warn] 24228#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: code cache explicitly off (affects require) + content_by_lua - 2019/02/24 13:28:26 [warn] 24232#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: code cache explicitly off (affects require) + content_by_lua - 2019/02/24 13:28:27 [warn] 24232#0: *2 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 16: do not skip luarocks* - 2019/02/24 13:28:31 [warn] 24233#0: *1 [lua] _G write guard:12: writing a global lua variable ('luarocks2') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 16: do not skip luarocks* - 2019/02/24 13:28:32 [warn] 24233#0: *2 [lua] _G write guard:12: writing a global lua variable ('luarocks2') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 8: code cache explicitly off (affects require) + set_by_lua_file - 2019/02/24 13:28:36 [warn] 24234#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 8: code cache explicitly off (affects require) + set_by_lua_file - 2019/02/24 13:28:38 [warn] 24234#0: *2 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 17: clear _G table - 2019/02/24 13:28:41 [warn] 24235#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 17: clear _G table - 2019/02/24 13:28:42 [warn] 24235#0: *2 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 7: code cache explicitly off (affects require) + content_by_lua_file - 2019/02/24 13:28:45 [warn] 24236#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 7: code cache explicitly off (affects require) + content_by_lua_file - 2019/02/24 13:28:47 [warn] 24236#0: *2 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: do not skip luarocks - 2019/02/24 13:29:09 [warn] 24241#0: *1 [lua] _G write guard:12: writing a global lua variable ('luarocks') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: do not skip luarocks - 2019/02/24 13:29:10 [warn] 24241#0: *2 [lua] _G write guard:12: writing a global lua variable ('luarocks') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: no clear builtin lib "string" - 2019/02/24 13:29:47 [warn] 24249#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: no clear builtin lib "string" - 2019/02/24 13:29:49 [warn] 24249#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 29: cosocket connection pool timeout (after Lua VM destroys) - 2019/02/24 13:30:10 [warn] 24254#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 29: cosocket connection pool timeout (after Lua VM destroys) - 2019/02/24 13:30:12 [warn] 24254#0: *3 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 18: ngx.ctx gets prematurely released ngx.exit() (lua_code_cache off) - 2019/02/24 13:57:56 [alert] 24461#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:40
TEST 19: gmatch iterator used by another request - 2019/02/24 14:03:13 [warn] 24566#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 20: globals are shared by all requests - 2019/02/24 14:24:09 [warn] 24778#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 19: cannot survive across request boundary (send) - 2019/02/24 14:43:39 [warn] 25109#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 44: bad request tries to connect - 2019/02/24 14:45:39 [warn] 25166#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 48: bad request tries to set keepalive - 2019/02/24 14:45:54 [warn] 25183#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 46: bad request tries to send - 2019/02/24 14:47:10 [warn] 25207#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 21: cannot survive across request boundary (close) - 2019/02/24 14:47:15 [warn] 25208#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 47: bad request tries to close - 2019/02/24 14:48:12 [warn] 25216#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 45: bad request tries to receive - 2019/02/24 14:49:51 [warn] 25235#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 49: bad request tries to receiveuntil - 2019/02/24 14:49:56 [warn] 25236#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 20: cannot survive across request boundary (receive) - 2019/02/24 14:50:09 [warn] 25238#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: raw memcached - 2019/02/24 14:50:44 [warn] 25267#0: *1 [lua] _G write guard:12: writing a global lua variable ('resty') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 14:50:48 [warn] 25268#0: *1 [lua] _G write guard:12: writing a global lua variable ('Memcached') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 14:50:48 [warn] 25268#0: *1 [lua] _G write guard:12: writing a global lua variable ('CRC32') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: coroutine-based pub/sub - 2019/02/24 14:50:53 [warn] 25272#0: *1 [lua] _G write guard:12: writing a global lua variable ('Redis') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 14:51:03 [warn] 25273#0: *1 [lua] _G write guard:12: writing a global lua variable ('Redis') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 30: ngx.exit(400) should break xpcall and skip os.execute (all in user module) - 2019/02/24 14:52:26 [warn] 25301#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 28: ngx.set_uri(uri, true) should break pcall and skip os.execute (all in user module) - 2019/02/24 14:52:31 [warn] 25302#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 17: ngx.exit(400) should abort ngx.shared.DICT (set) - 2019/02/24 14:52:36 [warn] 25303#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 8: ngx.exit(400) should abort ngx.send_headers - 2019/02/24 14:52:41 [warn] 25304#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 31: ngx.exec() should skip os.execute (all in user module) - 2019/02/24 14:52:46 [warn] 25305#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: ngx.exit(400) should abort ngx.location.capture - 2019/02/24 14:52:50 [warn] 25306#0: *1 [lua] _G write guard:12: writing a global lua variable ('memd') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 10: ngx.exit(400) should abort ngx.say - 2019/02/24 14:52:55 [warn] 25307#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 26: ngx.exec() should break pcall and skip os.execute (all in user module) - 2019/02/24 14:53:04 [warn] 25309#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 7: ngx.exit(400) should abort ngx.exec - 2019/02/24 14:53:08 [warn] 25310#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 9: ngx.exit(400) should abort ngx.print - 2019/02/24 14:53:13 [warn] 25311#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 5: ngx.exit(400) should abort ngx.redirect - 2019/02/24 14:53:18 [warn] 25312#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: ngx.exit(400) should abort ngx.re.gmatch - 2019/02/24 14:53:23 [warn] 25313#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: ngx.exit(400) should abort ngx.exit - 2019/02/24 14:53:28 [warn] 25314#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: ngx.exit(400) should abort ngx.log - 2019/02/24 14:53:33 [warn] 25315#0: *1 [lua] _G write guard:12: writing a global lua variable ('memd') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 20: ngx.exit(400) should abort ngx.shared.DICT (get) - 2019/02/24 14:53:38 [warn] 25316#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 16: ngx.exit(400) should abort ngx.re.gsub - 2019/02/24 14:53:43 [warn] 25317#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 32: ngx.exec() should break pcall and skip os.execute (all in user module) - 2019/02/24 14:53:48 [warn] 25318#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 27: ngx.exec() should skip os.execute (all in user module) - 2019/02/24 14:53:52 [warn] 25319#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 24: ngx.redirect() should break pcall and skip os.execute (all in user module) - 2019/02/24 14:53:56 [warn] 25320#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: ngx.exit(400) should abort print - 2019/02/24 14:54:01 [warn] 25321#0: *1 [lua] _G write guard:12: writing a global lua variable ('memd') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 13: ngx.exit(400) should abort ngx.re.match - 2019/02/24 14:54:07 [warn] 25322#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 25: ngx.redirect() should skip os.execute (all in user module) - 2019/02/24 14:54:12 [warn] 25323#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 22: ngx.exit(400) should break pcall and skip os.execute - 2019/02/24 14:54:17 [warn] 25324#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 11: ngx.exit(400) should abort ngx.flush - 2019/02/24 14:54:22 [warn] 25325#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 18: ngx.exit(400) should abort ngx.shared.DICT (replace) - 2019/02/24 14:54:27 [warn] 25326#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 23: ngx.exit(400) should break pcall and skip os.execute (all in user module) - 2019/02/24 14:54:32 [warn] 25327#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 12: ngx.exit(400) should abort ngx.eof - 2019/02/24 14:54:37 [warn] 25328#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: ngx.exit(400) should abort ngx.re.sub - 2019/02/24 14:54:42 [warn] 25329#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 21: ngx.exit(400) should skip os.execute - 2019/02/24 14:54:47 [warn] 25330#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 19: ngx.exit(400) should abort ngx.shared.DICT (incr) - 2019/02/24 14:54:52 [warn] 25331#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 4: ngx.exit(400) should abort ngx.location.capture_multi - 2019/02/24 14:54:57 [warn] 25332#0: *1 [lua] _G write guard:12: writing a global lua variable ('memd') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 4: attempt to use the req socket across request boundary - 2019/02/24 14:59:42 [warn] 25392#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 5: receive until on request_body - receiveuntil(1) on the last byte of the body - 2019/02/24 14:59:47 [warn] 25393#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: pipelined POST requests - 2019/02/24 14:59:53 [warn] 25394#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: sanity - 2019/02/24 15:01:13 [warn] 25419#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: free up the whole connection pool if no active connections - 2019/02/24 15:01:17 [warn] 25420#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 12: sanity (uds) - 2019/02/24 15:02:14 [warn] 25430#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: github issue #110: ngx.exit with HTTP_NOT_FOUND causes worker process to exit - 2019/02/24 15:02:24 [warn] 25432#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: custom pools (different pool for the same host:port) - tcp - 2019/02/24 15:02:28 [warn] 25433#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 16: custom pools (same pool for different host:port) - tcp - 2019/02/24 15:02:32 [warn] 25434#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 17: custom pools (different pool for the same host:port) - unix - 2019/02/24 15:02:36 [warn] 25435#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 18: custom pools (same pool for the same path) - unix - 2019/02/24 15:02:39 [warn] 25436#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 19: numeric pool option value - 2019/02/24 15:02:43 [warn] 25437#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 20: nil pool option value - 2019/02/24 15:02:47 [warn] 25438#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 21: (bad) table pool option value - 2019/02/24 15:02:51 [warn] 25439#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 22: (bad) boolean pool option value - 2019/02/24 15:02:55 [warn] 25440#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 24: bug in send(): clear the chain writer ctx - 2019/02/24 15:03:02 [warn] 25442#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 46: conn queuing: resume connect operation if resumed connect failed (could not be resolved) - 2019/02/24 15:04:32 [alert] 25466#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
Child process 25496 is already gone.
TEST 2: ${prefix} - 2019/02/24 15:06:42 [warn] 25507#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: $prefix - 2019/02/24 15:06:46 [warn] 25508#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 11: globals sharing - 2019/02/24 15:07:44 [warn] 25524#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: read chunks (user module) - 2019/02/24 15:12:51 [warn] 25642#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: bad request tries to setpeer - 2019/02/24 15:17:59 [warn] 25742#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 17: bad request tries to receive - 2019/02/24 15:18:26 [warn] 25753#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 5: access conflicts of receive() on shared udp objects - 2019/02/24 15:18:29 [warn] 25754#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 16: bad request tries to send - 2019/02/24 15:18:33 [warn] 25755#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 19: bad request tries to receive - 2019/02/24 15:18:41 [warn] 25757#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 4: access conflicts of connect() on shared udp objects - 2019/02/24 15:18:44 [warn] 25758#0: *1 [lua] _G write guard:12: writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 18: bad request tries to close - 2019/02/24 15:18:51 [warn] 25760#0: *1 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 10: tcp cosocket in timer handler (keep-alive connections) - log_by_lua - 2019/02/24 16:02:55 [warn] 26090#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 11: tcp cosocket in timer handler (keep-alive connections) - header_filter_by_lua - 2019/02/24 16:03:23 [warn] 26096#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 12: tcp cosocket in timer handler (keep-alive connections) - body_filter_by_lua - 2019/02/24 16:04:08 [warn] 26106#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 13: tcp cosocket in timer handler (keep-alive connections) - set_by_lua - 2019/02/24 16:04:28 [warn] 26110#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: tcp cosocket in timer handler (keep-alive connections) - 2019/02/24 16:04:47 [warn] 26114#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: globals are shared - 2019/02/24 16:04:56 [warn] 26116#0: *2 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 10: tcp cosocket in timer handler (keep-alive connections) - body_filter_by_lua - 2019/02/24 16:08:07 [warn] 26185#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 8: tcp cosocket in timer handler (keep-alive connections) - log_by_lua - 2019/02/24 16:08:26 [warn] 26189#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 9: tcp cosocket in timer handler (keep-alive connections) - header_filter_by_lua - 2019/02/24 16:08:31 [warn] 26190#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 11: tcp cosocket in timer handler (keep-alive connections) - set_by_lua - 2019/02/24 16:08:44 [warn] 26193#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 4: tcp cosocket in timer handler (keep-alive connections) - 2019/02/24 16:08:58 [warn] 26196#0: *2 [lua] _G write guard:12: writing a global lua variable ('test') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: kill pending resolver - 2019/02/24 16:23:33 [alert] 26552#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
TEST 3: kill pending resolver - 2019/02/24 16:23:34 [alert] 26552#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
TEST 6: concurrent operations while resolving - 2019/02/24 16:23:46 [alert] 26556#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
TEST 6: concurrent operations while resolving - 2019/02/24 16:23:48 [alert] 26556#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
killing the child process 26564 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 26565 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 16: unsupported ssl protocol - 2019/02/24 16:26:50 [crit] 26586#0: *1 SSL_do_handshake() failed (SSL: error:141640BF:SSL routines:tls_construct_client_hello:no protocols available), client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"
TEST 16: unsupported ssl protocol - 2019/02/24 16:26:51 [crit] 26586#0: *4 SSL_do_handshake() failed (SSL: error:141640BF:SSL routines:tls_construct_client_hello:no protocols available), client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", host: \"localhost\"
TEST 24: inline Lua code cache should not mess up across different phases - 2019/02/24 16:29:56 [crit] 26627#0: *1 connect() to 0.0.0.1:80 failed (22: Invalid argument) while connecting to upstream, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", subrequest: \"/proxy\", upstream: \"http://0.0.0.1:80/proxy\", host: \"localhost\"
TEST 24: inline Lua code cache should not mess up across different phases - 2019/02/24 16:29:58 [crit] 26627#0: *12 connect() to 0.0.0.1:80 failed (22: Invalid argument) while connecting to upstream, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", subrequest: \"/proxy\", upstream: \"http://0.0.0.1:80/proxy\", host: \"localhost\"
TEST 14: missing } - 2019/02/24 16:30:43 [emerg] 26644#0: \"events\" directive is not allowed here in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:56 at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Socket.pm line 1341.
TEST 14: missing } - 2019/02/24 16:30:43 [emerg] 26646#0: \"events\" directive is not allowed here in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:56 at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Socket.pm line 1341.
TEST 12: code cache off - 2019/02/24 16:32:11 [alert] 26715#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:27
TEST 13: lua subrequests - 2019/02/24 16:32:40 [alert] 26720#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:25
TEST 14: keep global variable in ssl_session_(store|fetch)_by_lua when OpenResty LuaJIT is used - 2019/02/24 16:40:34 [warn] 26791#0: *4 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: keep global variable in ssl_session_(store|fetch)_by_lua when OpenResty LuaJIT is used - 2019/02/24 16:40:35 [warn] 26791#0: *8 [lua] _G write guard:12: __newindex(): writing a global lua variable ('bar') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: lua code cache off - 2019/02/24 16:45:28 [alert] 26883#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:25
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:04 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:05 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:06 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:07 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:08 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:09 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:10 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:11 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:12 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:13 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:14 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:15 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:16 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:17 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:18 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 8: respect lua_max_running_timers - 2019/02/24 16:51:19 [alert] 26950#0: 9 lua_max_running_timers are not enough
TEST 9: lua_code_cache off - 2019/02/24 16:51:28 [alert] 26952#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:25
TEST 2: shared global env - 2019/02/24 16:51:37 [warn] 26953#0: *2 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: timer + reload (lua code cache off) - 2019/02/24 16:51:57 [alert] 26959#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:25
TEST 2: timer + reload (lua code cache off) - 2019/02/24 16:51:58 [alert] 26959#0: lua_code_cache is off; this will hurt performance in /home/ec2-user/git/lua-nginx-module/t/servroot/conf/nginx.conf:25
TEST 4: content_by_lua - 2019/02/24 16:54:09 [warn] 26992#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 8: ssl_certificate_by_lua - 2019/02/24 16:54:14 [warn] 26993#0: *4 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 6: body_filter_by_lua - 2019/02/24 16:54:24 [warn] 27014#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 5: header_filter_by_lua - 2019/02/24 16:54:28 [warn] 27015#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: access_by_lua - 2019/02/24 16:54:32 [warn] 27016#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 2: rewrite_by_lua - 2019/02/24 16:54:40 [warn] 27018#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: set_by_lua - 2019/02/24 16:54:44 [warn] 27019#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 9: timer - 2019/02/24 16:54:49 [warn] 27020#0: *2 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 15: balancer_by_lua - 2019/02/24 16:54:53 [warn] 27021#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 7: log_by_lua - 2019/02/24 16:55:03 [warn] 27023#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 14: uthread - 2019/02/24 16:55:06 [warn] 27024#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('foo') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables

Go back to the index page.