(This page was automatically generated by the tools in the opsboy project on 10:07:06 03-Nov-2020 GMT.)

Detailed Test Report for ngx_lua in linux i386 (v)

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 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 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

Go back to the index page.