Detailed Test Report for ngx_lua in linux i386 (v)

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	30	70	199	20499	9356 sec

LuaJIT

LuaJIT 2.1.0-beta3, commit 864c72e

OpenSSL

OpenSSL 1.1.0j 20 Nov 2018

Compilation Errors

Unexpected Failures

File	Name	Details
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 17:35:46 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 17:35:46 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 '
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 '
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 18:27:57 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 18:27:57 GMT '
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 '
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 19:13:55 GMT '
145-shdict-list.t	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	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 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 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 19:28:09 [error] 5989\#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 19:28:09 [debug] 5989\#0: 1 lua tcp socket handle write error 2019/02/24 19:28:09 [debug] 5989\#0: 1 lua tcp socket waking up the current request 2019/02/24 19:28:09 [debug] 5989\#0: 1 lua tcp operation done, resuming lua thread 2019/02/24 19:28:09 [debug] 5989\#0: 1 lua tcp socket calling prepare retvals handler 081528F6, u:049DA7E8 2019/02/24 19:28:09 [debug] 5989\#0: 1 lua tcp socket send return value handler 2019/02/24 19:28:09 [debug] 5989\#0: 1 poll del event: fd:8 ev:4 2019/02/24 19:28:09 [debug] 5989\#0: 1 poll del index: 3 2019/02/24 19:28:09 [debug] 5989\#0: 1 delete posted event 049D5CC0 2019/02/24 19:28:09 [debug] 5989\#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 19:28:32 [error] 5993\#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 19:28:32 [debug] 5993\#0: 1 lua tcp socket handle write error 2019/02/24 19:28:32 [debug] 5993\#0: 1 lua tcp socket waking up the current request 2019/02/24 19:28:32 [debug] 5993\#0: 1 lua tcp operation done, resuming lua thread 2019/02/24 19:28:32 [debug] 5993\#0: 1 lua tcp socket calling prepare retvals handler 081528F6, u:049DB8E0 2019/02/24 19:28:32 [debug] 5993\#0: 1 lua tcp socket send return value handler 2019/02/24 19:28:32 [debug] 5993\#0: 1 poll del event: fd:8 ev:4 2019/02/24 19:28:32 [debug] 5993\#0: 1 poll del index: 3 2019/02/24 19:28:32 [debug] 5993\#0: 1 delete posted event 049D68D0 2019/02/24 19:28:32 [debug] 5993\#0: *1 lua run thread, top:8 c:1 '
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 2: error in init after HUP (master still alive, worker process still the same as before) - pattern "failed to init" 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)
151-initby-hup.t	TEST 5: error in init after HUP, not reloaded but foo have changed. - pattern "failed to init" should match a line in error.log (req 0)
151-initby-hup.t	TEST 6: no error in init again, reload success and foo still have changed. - pattern "[error]" should not match any line in error.log but matches line "2019/02/24 19:29:10 [error] 6036\#0: init_by_lua error: init_by_lua:5: failed to init" (req 0)	stack traceback: [C]: in function 'error' init_by_lua:5: in main chunk 2019/02/24 19:29:11 [notice] 6036\#0: using the "epoll" event method 2019/02/24 19:29:11 [notice] 6036\#0: start worker processes 2019/02/24 19:29:11 [debug] 6036\#0: channel 4:5 2019/02/24 19:29:11 [notice] 6036\#0: start worker process 6092 2019/02/24 19:29:11 [debug] 6036\#0: pass channel s:1 pid:6092 fd:4 to s:0 pid:6069 fd:3 2019/02/24 19:29:11 [debug] 6092\#0: malloc: 05442850:12 '
157-socket-keepalive-hup.t	TEST 1: exiting - pattern "timer prematurely expired: true" should match a line in error.log (req 0)
157-socket-keepalive-hup.t	TEST 1: exiting - pattern "setkeepalive successfully" should match a line in error.log (req 0)
157-socket-keepalive-hup.t	TEST 1: exiting - pattern "lua tcp socket set keepalive while process exiting, closing connection" should match a line in error.log (req 0)

Expected Failures

File	Name	Details
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
086-init-by.t	nginx: [error]	init_by_lua error: init_by_lua:2: failed to init
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 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 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 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 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 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 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 1)
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)
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 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 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 1: single timer - pattern "lua abort pending timers" should match a line in error.log (req 0)
109-timer-hup.t	TEST 1: single timer - pattern "lua ngx.timer expired" should match a line in error.log (req 0)
109-timer-hup.t	TEST 1: single timer - pattern "http lua close fake http connection" should match a line in error.log (req 0)
109-timer-hup.t	TEST 1: single timer - pattern "in callback: hello, 1" should match a line in error.log (req 0)
109-timer-hup.t	TEST 1: single timer - pattern "timer prematurely expired: true" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "lua abort pending timers" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "lua ngx.timer expired" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "http lua close fake http connection" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "f: timer prematurely expired: true" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "f: registered a new timer after reload" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "f: exiting=true" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "g: timer prematurely expired: false" should match a line in error.log (req 0)
109-timer-hup.t	TEST 4: trying to add new timer after HUP reload - pattern "g: exiting=true" should match a line in error.log (req 0)
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 '
109-timer-hup.t	TEST 6: HUP reload should abort pending timers (coroutine + cosocket) - grep_error_log_out (req 1)	got: 'lua found 2 pending timers ' expected: 'lua found 1 pending timers '
109-timer-hup.t	TEST 2: multiple timers - pattern "lua abort pending timers" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "lua ngx.timer expired" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "http lua close fake http connection" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 1!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 2!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 3!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 4!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 5!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 6!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 7!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 8!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 9!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "in callback: hello, 10!" should match a line in error.log (req 0)
109-timer-hup.t	TEST 2: multiple timers - pattern "timer prematurely expired: true" should match a line in error.log (req 0)
109-timer-hup.t	TEST 7: HUP reload should abort pending timers (fuzz test) - grep_error_log_out (req 0)	got: '' 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 8177 pending timers ' expected: 'lua found 8191 pending timers '
109-timer-hup.t	TEST 3: trying to add new timer after HUP reload - pattern "lua abort pending timers" should match a line in error.log (req 0)
109-timer-hup.t	TEST 3: trying to add new timer after HUP reload - pattern "lua ngx.timer expired" should match a line in error.log (req 0)
109-timer-hup.t	TEST 3: trying to add new timer after HUP reload - pattern "http lua close fake http connection" should match a line in error.log (req 0)
109-timer-hup.t	TEST 3: trying to add new timer after HUP reload - pattern "timer prematurely expired: true" should match a line in error.log (req 0)
109-timer-hup.t	TEST 3: trying to add new timer after HUP reload - pattern "failed to register a new timer after reload: process exiting, context: ngx.timer" should match a line in error.log (req 0)
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 ' Looks like you failed 1 test of 39.
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
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
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
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 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)
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 1)
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 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 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 '

Warnings

TEST 38: user modules using ngx.arg - 2019/02/24 16:58:32 [warn] 2303#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 37: globals are shared in all requests. - 2019/02/24 16:58:52 [warn] 2310#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: sanity - 2019/02/24 17:02:25 [warn] 2401#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 27: globals sharing by using _G (set_by_lua*) - 2019/02/24 17:08:30 [warn] 2552#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 29: globals sharing by using _G (header_filter_by_lua*) - 2019/02/24 17:09:14 [warn] 2566#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 17:09:29 [warn] 2571#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 17:09:32 [warn] 2572#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 17:09:36 [warn] 2573#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 17:09:42 [warn] 2575#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 17:09:41 [alert] 2575#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 17:09:43 [warn] 2575#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 17:09:43 [warn] 2575#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 2745 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2746 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2748 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2749 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2753 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2754 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2790 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2791 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2797 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2798 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2823 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2824 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2865 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 2866 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 6: pipelined POST requests - 2019/02/24 17:28:27 [warn] 3012#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: attempt to use the req socket across request boundary - 2019/02/24 17:28:36 [warn] 3015#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 17:28:39 [warn] 3016#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 17:31:43 [warn] 3088#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 17:31:46 [warn] 3089#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 17:32:29 [warn] 3098#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 17:32:36 [warn] 3100#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 17:35:16 [warn] 3151#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 17:35:22 [warn] 3153#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 17:35:43 [warn] 3161#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 17:35:49 [warn] 3163#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 17:35:52 [warn] 3164#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 17:36:07 [warn] 3179#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 17:36:13 [warn] 3185#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 17:36:28 [warn] 3190#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 17:36:34 [warn] 3193#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: code cache explicitly off (affects require) + content_by_lua - 2019/02/24 17:51:44 [warn] 3558#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 17:51:44 [warn] 3558#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 17:51:50 [warn] 3560#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 17:51:50 [warn] 3560#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 14: no clear builtin lib "string" - 2019/02/24 17:51:53 [warn] 3561#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 17:51:53 [warn] 3561#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: code cache explicitly off (affects require) + set_by_lua_file - 2019/02/24 17:51:56 [warn] 3562#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 17:51:56 [warn] 3562#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 7: code cache explicitly off (affects require) + content_by_lua_file - 2019/02/24 17:51:59 [warn] 3563#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 17:52:00 [warn] 3563#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 17:52:11 [warn] 3567#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 17:52:11 [warn] 3567#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 29: cosocket connection pool timeout (after Lua VM destroys) - 2019/02/24 17:52:41 [warn] 3577#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 17:52:41 [warn] 3577#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 17:52:44 [warn] 3578#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: do not skip luarocks - 2019/02/24 17:53:17 [warn] 3588#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 17:53:17 [warn] 3588#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 30: cosocket connection pool timeout (before Lua VM destroys) - 2019/02/24 17:53:20 [warn] 3589#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 17:53:20 [warn] 3589#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 18:02:31 [alert] 3788#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 18:06:20 [warn] 3873#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 18:13:31 [warn] 4038#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 20: cannot survive across request boundary (receive) - 2019/02/24 18:27:41 [warn] 4382#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 18:28:06 [warn] 4390#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 18:28:30 [warn] 4398#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 18:28:43 [warn] 4402#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 18:28:58 [warn] 4407#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 18:29:08 [warn] 4410#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 18:29:48 [warn] 4423#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 18:30:34 [warn] 4440#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 18:30:37 [warn] 4441#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 18:31:11 [warn] 4459#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 18:31:14 [warn] 4460#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 18:31:14 [warn] 4460#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 18:31:18 [warn] 4464#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 18:31:21 [warn] 4465#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 28: ngx.set_uri(uri, true) should break pcall and skip os.execute (all in user module) - 2019/02/24 18:32:28 [warn] 4493#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 18:32:31 [warn] 4494#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: ngx.exit(400) should abort ngx.shared.DICT (get) - 2019/02/24 18:32:34 [warn] 4495#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 18:32:37 [warn] 4496#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 18:32:40 [warn] 4497#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: ngx.exit(400) should abort ngx.say - 2019/02/24 18:32:43 [warn] 4498#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 18:32:45 [warn] 4499#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 18:32:48 [warn] 4500#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 18:32:51 [warn] 4501#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 26: ngx.exec() should break pcall and skip os.execute (all in user module) - 2019/02/24 18:32:54 [warn] 4502#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 18:32:57 [warn] 4503#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 8: ngx.exit(400) should abort ngx.send_headers - 2019/02/24 18:33:00 [warn] 4504#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 18:33:03 [warn] 4505#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 18:33:05 [warn] 4506#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 31: ngx.exec() should skip os.execute (all in user module) - 2019/02/24 18:33:08 [warn] 4507#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 18:33:11 [warn] 4508#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 18:33:14 [warn] 4509#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 18:33:17 [warn] 4510#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 18:33:20 [warn] 4511#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 18:33:23 [warn] 4512#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: ngx.exit(400) should abort ngx.re.match - 2019/02/24 18:33:26 [warn] 4513#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 18:33:28 [warn] 4514#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 18:33:31 [warn] 4515#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 7: ngx.exit(400) should abort ngx.exec - 2019/02/24 18:33:34 [warn] 4516#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 18:33:37 [warn] 4517#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 18:33:40 [warn] 4518#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 18:33:43 [warn] 4519#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 18:33:48 [warn] 4521#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 18:33:51 [warn] 4522#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 18:33:54 [warn] 4523#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: ngx.exit(400) should break xpcall and skip os.execute (all in user module) - 2019/02/24 18:33:57 [warn] 4524#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: attempt to use the req socket across request boundary - 2019/02/24 18:37:07 [warn] 4580#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 18:37:10 [warn] 4581#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 18:37:13 [warn] 4582#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 18:37:50 [warn] 4596#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 18:37:53 [warn] 4597#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 18:38:30 [warn] 4611#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 18:38:36 [warn] 4613#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 18:38:39 [warn] 4614#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 18:38:42 [warn] 4615#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 18:38:45 [warn] 4616#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 18:38:48 [warn] 4617#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 18:38:51 [warn] 4618#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 18:38:54 [warn] 4619#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 18:38:56 [warn] 4620#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 18:38:59 [warn] 4621#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 18:39:05 [warn] 4623#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 18:40:09 [alert] 4645#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
TEST 1: $prefix - 2019/02/24 18:41:38 [warn] 4685#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 2: ${prefix} - 2019/02/24 18:41:41 [warn] 4686#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 18:41:56 [warn] 4693#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 18:45:39 [warn] 4842#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 4: access conflicts of connect() on shared udp objects - 2019/02/24 18:48:49 [warn] 4921#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 18:48:56 [warn] 4923#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 18:49:02 [warn] 4925#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 18:49:22 [warn] 4934#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 18:49:31 [warn] 4937#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 18:49:39 [warn] 4942#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: bad request tries to close - 2019/02/24 18:49:42 [warn] 4943#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: tcp cosocket in timer handler (keep-alive connections) - set_by_lua - 2019/02/24 19:02:43 [warn] 5239#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 19:03:02 [warn] 5245#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 10: tcp cosocket in timer handler (keep-alive connections) - log_by_lua - 2019/02/24 19:03:17 [warn] 5250#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 19:03:55 [warn] 5262#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 12: tcp cosocket in timer handler (keep-alive connections) - body_filter_by_lua - 2019/02/24 19:04:04 [warn] 5265#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 19:04:13 [warn] 5270#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 19:06:13 [warn] 5313#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 19:06:29 [warn] 5318#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 19:06:33 [warn] 5319#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 19:06:36 [warn] 5320#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 10: tcp cosocket in timer handler (keep-alive connections) - body_filter_by_lua - 2019/02/24 19:07:00 [warn] 5327#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
killing the child process 5334 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 3: kill pending resolver - 2019/02/24 19:15:39 [alert] 5709#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
killing the child process 5723 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 5724 with force... at /home/ec2-user/git/lua-nginx-module/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 6: concurrent operations while resolving - 2019/02/24 19:16:37 [alert] 5729#0: send() failed (1: Operation not permitted) while resolving, resolver: 127.0.0.2:12345
TEST 16: unsupported ssl protocol - 2019/02/24 19:18:47 [crit] 5762#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 19:18:47 [crit] 5762#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 14: missing } - 2019/02/24 19:19:10 [emerg] 5782#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 19:19:10 [emerg] 5784#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 24: inline Lua code cache should not mess up across different phases - 2019/02/24 19:19:13 [crit] 5785#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 19:19:14 [crit] 5785#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 13: lua subrequests - 2019/02/24 19:21:01 [alert] 5858#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 12: code cache off - 2019/02/24 19:21:30 [alert] 5868#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 14: keep global variable in ssl_session_(store|fetch)_by_lua when OpenResty LuaJIT is used - 2019/02/24 19:24:48 [warn] 5930#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 19:24:49 [warn] 5930#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 19:28:59 [alert] 6030#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 19:29:22 [alert] 6107#0: 9 lua_max_running_timers are not enough
TEST 9: lua_code_cache off - 2019/02/24 19:29:24 [alert] 6108#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 19:29:39 [warn] 6111#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 19:29:52 [alert] 6122#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 19:29:54 [alert] 6122#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 1: set_by_lua - 2019/02/24 19:31:56 [warn] 6149#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 19:31:59 [warn] 6150#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 19:32:02 [warn] 6151#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 19:32:05 [warn] 6152#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 15: balancer_by_lua - 2019/02/24 19:32:07 [warn] 6153#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 4: content_by_lua - 2019/02/24 19:32:13 [warn] 6155#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 19:32:16 [warn] 6156#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 6: body_filter_by_lua - 2019/02/24 19:32:19 [warn] 6157#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 19:32:22 [warn] 6158#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: uthread - 2019/02/24 19:32:29 [warn] 6160#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 19:32:32 [warn] 6161#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.