Detailed Test Report for lua-resty-websocket in linux x86_64 (wv)

Summary

Commit	Testing Time	Unexpected Failures	Expected Failures	Files	Tests	Elapsed Time
ff9564c4	2019-02-06 07:45:59 GMT	0	2	3	578	141 sec

LuaJIT 2.1.0-beta3, commit 0e646b5

(none)

File	Name	Details
cs.t	TEST 10: client recv timeout (timeout option) - response_body - response is expected (repeated req 0, req 0)	@@ -1,2 +1 @@ -failed to receive 1st frame: failed to receive the first 2 bytes: timeout +failed to connect: failed to connect: timeout -2: received: 你好, WebSocket! (text) '
cs.t	TEST 10: client recv timeout (timeout option) - pattern "lua tcp socket read timed out" should match a line in error.log (req 0)

TEST 2: module size of resty.websocket.client - 2019/02/06 10:15:37 [warn] 24058#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('n') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 3: module size of resty.websocket.server - 2019/02/06 10:15:39 [warn] 24059#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('n') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
TEST 1: module size of resty.websocket.protocol - 2019/02/06 10:15:41 [warn] 24060#0: *1 [lua] _G write guard:12: __newindex(): writing a global lua variable ('n') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
killing the child process 24075 with force... at /home/ec2-user/git/lua-resty-websocket/../test-nginx/lib/Test/Nginx/Util.pm line 606.
killing the child process 24104 with force... at /home/ec2-user/git/lua-resty-websocket/../test-nginx/lib/Test/Nginx/Util.pm line 606.
TEST 17: exceeding the default 65535 max frame len limit (65536 bytes) - HTTP response read failure: Connection reset by peer at /home/ec2-user/git/lua-resty-websocket/../test-nginx/lib/Test/Nginx/Socket.pm line 2165.