(This page was automatically generated by the tools in the opsboy project on 18:49:44 05-Jul-2020 GMT.)

Detailed Test Report for lua-resty-core in linux i386 (r)

Summary

Commit Testing Time Unexpected
Failures
Expected
Failures
Files Tests Elapsed Time
d36c977a 2019-02-24 06:09:40 GMT 128 133 sec

LuaJIT

LuaJIT 2.1.0-beta3, commit 864c72e

OpenSSL

OpenSSL 1.1.0j 20 Nov 2018

Compilation Errors

Unexpected Failures

File Name Details
balancer-timeout.t TEST 1: set_timeouts - grep_error_log_out (req 0) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 1: set_timeouts - grep_error_log_out (req 1) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 2: set_timeouts (nil connect timeout) - grep_error_log_out (req 0) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 2: set_timeouts (nil connect timeout) - grep_error_log_out (req 1) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 4: set_timeouts (nil read timeout) - grep_error_log_out (req 0) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 4: set_timeouts (nil read timeout) - grep_error_log_out (req 1) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 3: set_timeouts (nil send timeout) - grep_error_log_out (req 0) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer-timeout.t TEST 3: set_timeouts (nil send timeout) - grep_error_log_out (req 1) ''
doesn't match '(?^:\Aevent timer add: \d+: 1234:
event timer add: \d+: 5678:
event timer add: \d+: 7689:
\z)'
balancer.t TEST 11: keepalive after balancer - grep_error_log_out (req 0) @@ -1,5 +0,0 @@
-free keepalive peer: saving connection
-get keepalive peer: using connection
-free keepalive peer: saving connection
-get keepalive peer: using connection
-free keepalive peer: saving connection
'
balancer.t TEST 11: keepalive after balancer - grep_error_log_out (req 1) @@ -1,6 +0,0 @@
-get keepalive peer: using connection
-free keepalive peer: saving connection
-get keepalive peer: using connection
-free keepalive peer: saving connection
-get keepalive peer: using connection
-free keepalive peer: saving connection
'
pipe-stderr.t TEST 20: read stdout as stderr, mix read pattern and stdout/stderr, merge_stderr is true - pattern "(?^:lua pipe spawn process:[0-9A-F]+ pid:\d+ merge_stderr:1 buffer_size:4096)" should match a line in error.log (req 0)
pipe-stderr.t TEST 20: read stdout as stderr, mix read pattern and stdout/stderr, merge_stderr is true - pattern "(?^:lua pipe spawn process:[0-9A-F]+ pid:\d+ merge_stderr:1 buffer_size:4096)" should match a line in error.log (req 1)
pipe-stderr.t TEST 15: read stderr, aborted by uthread kill - pattern "lua pipe read process:" should match a line in error.log (req 0)
pipe-stderr.t TEST 15: read stderr, aborted by uthread kill - pattern "lua pipe proc read stderr cleanup" should match a line in error.log (req 0)
pipe-stderr.t TEST 15: read stderr, aborted by uthread kill - pattern "lua pipe read process:" should match a line in error.log (req 1)
pipe-stderr.t TEST 15: read stderr, aborted by uthread kill - pattern "lua pipe proc read stderr cleanup" should match a line in error.log (req 1)
pipe-stderr.t TEST 14: read stderr, timeout - pattern "lua pipe add timer for reading: 100(ms)" should match a line in error.log (req 0)
pipe-stderr.t TEST 14: read stderr, timeout - pattern "lua pipe add timer for reading: 100(ms)" should match a line in error.log (req 1)
pipe-stdin.t TEST 6: more than one coroutines write - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 0)
pipe-stdin.t TEST 6: more than one coroutines write - pattern "lua pipe write yielding" should match a line in error.log (req 0)
pipe-stdin.t TEST 6: more than one coroutines write - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 1)
pipe-stdin.t TEST 6: more than one coroutines write - pattern "lua pipe write yielding" should match a line in error.log (req 1)
pipe-stdin.t TEST 4: write process, timeout - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 0)
pipe-stdin.t TEST 4: write process, timeout - pattern "lua pipe write yielding" should match a line in error.log (req 0)
pipe-stdin.t TEST 4: write process, timeout - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 1)
pipe-stdin.t TEST 4: write process, timeout - pattern "lua pipe write yielding" should match a line in error.log (req 1)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 0)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe write yielding" should match a line in error.log (req 0)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe proc write cleanup" should match a line in error.log (req 0)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe add timer for writing: 100(ms)" should match a line in error.log (req 1)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe write yielding" should match a line in error.log (req 1)
pipe-stdin.t TEST 7: write process, aborted by uthread kill - pattern "lua pipe proc write cleanup" should match a line in error.log (req 1)
pipe-stdin.t TEST 5: write process, yield and write again - pattern "lua pipe write yielding" should match a line in error.log (req 0)
pipe-stdin.t TEST 5: write process, yield and write again - pattern "lua pipe write yielding" should match a line in error.log (req 1)
pipe-stdin.t TEST 2: write process, bad pipe - pattern "(?^:lua pipe write data error pipe:[0-9A-F]+ \(\d+: Broken pipe\))" should match a line in error.log (req 0)
pipe-stdin.t TEST 2: write process, bad pipe - pattern "(?^:lua pipe write data error pipe:[0-9A-F]+ \(\d+: Broken pipe\))" should match a line in error.log (req 1)
pipe-stdout.t TEST 19: read process, with yield, read more data than preallocated buffer - pattern "lua pipe read yielding" should match a line in error.log (req 0)
pipe-stdout.t TEST 19: read process, with yield, read more data than preallocated buffer - pattern "lua pipe read yielding" should match a line in error.log (req 1)
pipe-stdout.t TEST 26: read process, timeout - pattern "lua pipe add timer for reading: 100(ms)" should match a line in error.log (req 0)
pipe-stdout.t TEST 26: read process, timeout - pattern "lua pipe add timer for reading: 100(ms)" should match a line in error.log (req 1)
pipe-stdout.t TEST 20: read process, with yield, read more partial data than preallocated buffer - pattern "lua pipe read yielding" should match a line in error.log (req 0)
pipe-stdout.t TEST 20: read process, with yield, read more partial data than preallocated buffer - pattern "lua pipe read yielding" should match a line in error.log (req 1)
pipe-stdout.t TEST 27: read process, aborted by uthread kill - pattern "lua pipe read process:" should match a line in error.log (req 0)
pipe-stdout.t TEST 27: read process, aborted by uthread kill - pattern "lua pipe proc read stdout cleanup" should match a line in error.log (req 0)
pipe-stdout.t TEST 27: read process, aborted by uthread kill - pattern "lua pipe read process:" should match a line in error.log (req 1)
pipe-stdout.t TEST 27: read process, aborted by uthread kill - pattern "lua pipe proc read stdout cleanup" should match a line in error.log (req 1)
pipe.t TEST 10: wait process, process exited before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 10: wait process, process exited before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 2: spawn process, with buffer_size option - pattern "(?^:lua pipe spawn process:[0-9A-F]+ pid:\d+ merge_stderr:0 buffer_size:256)" should match a line in error.log (req 0)
pipe.t TEST 2: spawn process, with buffer_size option - pattern "(?^:lua pipe spawn process:[0-9A-F]+ pid:\d+ merge_stderr:0 buffer_size:256)" should match a line in error.log (req 1)
pipe.t TEST 42: return nil plus string 'timeout' when waiting process timed out - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 42: return nil plus string 'timeout' when waiting process timed out - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 3: ensure process is destroyed in GC - pattern "lua pipe destroy process:" should match a line in error.log (req 0)
pipe.t TEST 3: ensure process is destroyed in GC - pattern "lua pipe destroy process:" should match a line in error.log (req 1)
pipe.t TEST 24: shutdown a direction while a coroutine is waiting on it - grep_error_log_out (req 0) @@ -1,4 +0,0 @@
-lua pipe read yielding
-lua pipe read yielding
-lua pipe write yielding
-lua pipe write yielding
'
pipe.t TEST 24: shutdown a direction while a coroutine is waiting on it - grep_error_log_out (req 1) @@ -1,4 +0,0 @@
-lua pipe read yielding
-lua pipe read yielding
-lua pipe write yielding
-lua pipe write yielding
'
pipe.t TEST 37: kill living sub-process when the process instance is collected by GC. - pattern "lua pipe destroy process:" should match a line in error.log (req 0)
pipe.t TEST 37: kill living sub-process when the process instance is collected by GC. - pattern "lua pipe kill process:" should match a line in error.log (req 0)
pipe.t TEST 37: kill living sub-process when the process instance is collected by GC. - pattern "lua pipe destroy process:" should match a line in error.log (req 1)
pipe.t TEST 37: kill living sub-process when the process instance is collected by GC. - pattern "lua pipe kill process:" should match a line in error.log (req 1)
pipe.t TEST 17: wait process, timeout - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 17: wait process, timeout - pattern "lua pipe add timer for waiting: 100(ms)" should match a line in error.log (req 0)
pipe.t TEST 17: wait process, timeout - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 17: wait process, timeout - pattern "lua pipe add timer for waiting: 100(ms)" should match a line in error.log (req 1)
pipe.t TEST 9: wait process, process killed by signal before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 9: wait process, process killed by signal before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 33: wait process, process exited normally after waiting - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 33: wait process, process exited normally after waiting - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 12: wait process, aborted by uthread kill - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 12: wait process, aborted by uthread kill - pattern "lua pipe proc wait cleanup" should match a line in error.log (req 0)
pipe.t TEST 12: wait process, aborted by uthread kill - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t TEST 12: wait process, aborted by uthread kill - pattern "lua pipe proc wait cleanup" should match a line in error.log (req 1)
pipe.t TEST 8: wait process, process exited abnormally before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 0)
pipe.t TEST 8: wait process, process exited abnormally before waiting - pattern "lua pipe wait process:" should match a line in error.log (req 1)
pipe.t # Looks like you planned 286 tests but ran 284. Looks like you failed 28 tests of 284 run.
semaphore.t TEST 29: a light thread that is going to exit is waiting on a semaphore - pattern "http lua semaphore cleanup" should match a line in error.log (req 0)
semaphore.t TEST 29: a light thread that is going to exit is waiting on a semaphore - pattern "http lua semaphore cleanup" should match a line in error.log (req 1)
semaphore.t TEST 33: test semaphore gc - pattern "in lua gc, semaphore" should match a line in error.log (req 0)
semaphore.t TEST 33: test semaphore gc - pattern "in lua gc, semaphore" should match a line in error.log (req 1)
semaphore.t TEST 36: basic semaphore_mm free insert head - pattern "add to free queue head" should match a line in error.log (req 0)
semaphore.t TEST 36: basic semaphore_mm free insert head - pattern "add to free queue head" should match a line in error.log (req 1)
semaphore.t TEST 35: basic semaphore_mm free insert tail - pattern "add to free queue tail" should match a line in error.log (req 0)
semaphore.t TEST 35: basic semaphore_mm free insert tail - pattern "add to free queue tail" should match a line in error.log (req 1)
semaphore.t TEST 37: semaphore_mm free block (load <= 50% & the on the older side) - grep_error_log_out (req 1) got: ''
expected: 'free semaphore block
'
semaphore.t TEST 34: basic semaphore_mm alloc - grep_error_log_out (req 0) got: ''
expected: 'new block, alloc semaphore
'
semaphore.t TEST 34: basic semaphore_mm alloc - grep_error_log_out (req 1) got: ''
expected: 'from head of free queue, alloc semaphore
'
shdict.t TEST 48: exptime uses long type to avoid overflow in expire() + ttl() - response_body - response is expected (repeated req 0, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
shdict.t TEST 48: exptime uses long type to avoid overflow in expire() + ttl() - response_body - response is expected (repeated req 1, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
shdict.t TEST 49: init_ttl uses long type to avoid overflow in incr() + ttl() - response_body - response is expected (repeated req 0, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
shdict.t TEST 49: init_ttl uses long type to avoid overflow in incr() + ttl() - response_body - response is expected (repeated req 1, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
shdict.t TEST 47: exptime uses long type to avoid overflow in set() + ttl() - response_body - response is expected (repeated req 0, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
shdict.t TEST 47: exptime uses long type to avoid overflow in set() + ttl() - response_body - response is expected (repeated req 1, req 0) got: 'ttl: 0
'
expected: 'ttl: 2147483648
'
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
nginx: [emerg] too long parameter "PATH=/home..." started in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:13
Bailout called. Further testing stopped: TEST 4: attempt to resume a corrupted session - Cannot start nginx using command "nginx -p /home/ec2-user/git/lua-resty-core/t/servroot/ -c /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf > /dev/null" (status code 256).

Expected Failures

File Name Details
balancer.t TEST 16: https (keepalive) - status code ok got: '502'
expected: '200'
balancer.t TEST 16: https (keepalive) - response_body - response is expected (repeated req 0, req 0) got: '<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.8 (no pool)</center>
</body>
</html>
'
expected: 'ok'
balancer.t TEST 16: https (keepalive) - pattern "[alert]" should not match any line in error.log but matches line "2019/02/25 19:31:31 [alert] 25907\#25907: *1 ignoring stale global SSL error (SSL: error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html) while SSL handshaking to upstream, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", upstream: \"https://127.0.0.1:1234/back\", host: \"localhost\"" (req 0) 2019/02/25 19:31:31 [crit] 25907\#25907: *1 SSL_do_handshake() failed (SSL: error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html) while SSL handshaking to upstream, client: 127.0.0.1, server: localhost, request: "GET /t HTTP/1.1", upstream: "https://127.0.0.1:1234/back", host: "localhost"
'
balancer.t TEST 16: https (keepalive) - status code ok got: '502'
expected: '200'
balancer.t TEST 16: https (keepalive) - response_body - response is expected (repeated req 1, req 0) got: '<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.8 (no pool)</center>
</body>
</html>
'
expected: 'ok'
balancer.t TEST 17: https (no keepalive) - status code ok got: '502'
expected: '200'
balancer.t TEST 17: https (no keepalive) - response_body - response is expected (repeated req 0, req 0) got: '<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.8 (no pool)</center>
</body>
</html>
'
expected: 'ok'
balancer.t TEST 17: https (no keepalive) - pattern "[alert]" should not match any line in error.log but matches line "2019/02/25 19:31:33 [alert] 25916\#25916: *1 ignoring stale global SSL error (SSL: error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html) while SSL handshaking to upstream, client: 127.0.0.1, server: localhost, request: \"GET /t HTTP/1.1\", upstream: \"https://127.0.0.1:12347/back\", host: \"localhost\"" (req 0) 2019/02/25 19:31:33 [crit] 25916\#25916: *1 SSL_do_handshake() failed (SSL: error:24064064:random number generator:RAND_bytes:PRNG not seeded:You need to read the OpenSSL FAQ, https://www.openssl.org/docs/faq.html) while SSL handshaking to upstream, client: 127.0.0.1, server: localhost, request: "GET /t HTTP/1.1", upstream: "https://127.0.0.1:12347/back", host: "localhost"
'
balancer.t TEST 17: https (no keepalive) - status code ok got: '502'
expected: '200'
balancer.t TEST 17: https (no keepalive) - response_body - response is expected (repeated req 1, req 0) got: '<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.8 (no pool)</center>
</body>
</html>
'
expected: 'ok'
errlog-raw-log.t nginx: [error] hello world from init_by_lua
errlog.t nginx: [emerg] invalid number of arguments in "lua_capture_error_log" directive in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:25
errlog.t nginx: [emerg] invalid capture error log size "3k", minimum size is 4096 in /home/ec2-user/git/lua-resty-core/t/servroot/conf/nginx.conf:25
ocsp.t TEST 15: fail to validate OCSP response - OCSP response returns revoked status - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 15: fail to validate OCSP response - OCSP response returns revoked status - pattern "failed to validate OCSP response: certificate status "revoked" in the OCSP response" should match a line in error.log (req 0)
ocsp.t TEST 15: fail to validate OCSP response - OCSP response returns revoked status - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 15: fail to validate OCSP response - OCSP response returns revoked status - pattern "failed to validate OCSP response: certificate status "revoked" in the OCSP response" should match a line in error.log (req 1)
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - pattern "failed to validate OCSP response: OCSP_basic_verify() failed" should match a line in error.log (req 0)
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 14: fail to validate OCSP response - OCSP response signed by an unknown cert and the OCSP response does not contain the unknown cert - pattern "failed to validate OCSP response: OCSP_basic_verify() failed" should match a line in error.log (req 1)
ocsp.t TEST 2: get OCSP responder (not found) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 2: get OCSP responder (not found) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 2: get OCSP responder (not found) - pattern "OCSP responder not found" should match a line in error.log (req 0)
ocsp.t TEST 2: get OCSP responder (not found) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 2: get OCSP responder (not found) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 2: get OCSP responder (not found) - pattern "OCSP responder not found" should match a line in error.log (req 1)
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - pattern "OCSP response validation ok" should match a line in error.log (req 0)
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 13: validate OCSP response - OCSP response signed by an unknown cert and the OCSP response contains the unknown cert - pattern "OCSP response validation ok" should match a line in error.log (req 1)
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - pattern "failed to get OCSP responder: issuer certificate not next to leaf" should match a line in error.log (req 0)
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 4: get OCSP responder (issuer cert not next to the leaf cert) - pattern "failed to get OCSP responder: issuer certificate not next to leaf" should match a line in error.log (req 1)
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - pattern "failed to create OCSP request: no issuer certificate in chain" should match a line in error.log (req 0)
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 9: create OCSP request (no issuer cert in the chain) - pattern "failed to create OCSP request: no issuer certificate in chain" should match a line in error.log (req 1)
ocsp.t TEST 1: get OCSP responder (good case) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 1: get OCSP responder (good case) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 1: get OCSP responder (good case) - pattern "OCSP url found: http://127.0.0.1:8888/ocsp?foo=1," should match a line in error.log (req 0)
ocsp.t TEST 1: get OCSP responder (good case) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 1: get OCSP responder (good case) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 1: get OCSP responder (good case) - pattern "OCSP url found: http://127.0.0.1:8888/ocsp?foo=1," should match a line in error.log (req 1)
ocsp.t TEST 12: validate good OCSP response - no certs in response - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 12: validate good OCSP response - no certs in response - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 12: validate good OCSP response - no certs in response - pattern "OCSP response validation ok" should match a line in error.log (req 0)
ocsp.t TEST 12: validate good OCSP response - no certs in response - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 12: validate good OCSP response - no certs in response - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 12: validate good OCSP response - no certs in response - pattern "OCSP response validation ok" should match a line in error.log (req 1)
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - pattern "failed to validate OCSP response: no issuer certificate in chain" should match a line in error.log (req 0)
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 11: fail to validate OCSP response - no issuer cert - pattern "failed to validate OCSP response: no issuer certificate in chain" should match a line in error.log (req 1)
ocsp.t TEST 6: create OCSP request (good) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 6: create OCSP request (good) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 6: create OCSP request (good) - pattern "OCSP request created with length 68" should match a line in error.log (req 0)
ocsp.t TEST 6: create OCSP request (good) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 6: create OCSP request (good) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 6: create OCSP request (good) - pattern "OCSP request created with length 68" should match a line in error.log (req 1)
ocsp.t TEST 5: get OCSP responder (truncated) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "OCSP url found: http:/," should match a line in error.log (req 0)
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "still get an error: truncated" should match a line in error.log (req 0)
ocsp.t TEST 5: get OCSP responder (truncated) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "OCSP url found: http:/," should match a line in error.log (req 1)
ocsp.t TEST 5: get OCSP responder (truncated) - pattern "still get an error: truncated" should match a line in error.log (req 1)
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - pattern "failed to get OCSP responder: no issuer certificate in chain" should match a line in error.log (req 0)
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 3: get OCSP responder (no issuer cert at all) - pattern "failed to get OCSP responder: no issuer certificate in chain" should match a line in error.log (req 1)
ocsp.t TEST 8: create OCSP request (empty string cert chain) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 8: create OCSP request (empty string cert chain) - pattern "failed to create OCSP request: d2i_X509_bio() failed" should match a line in error.log (req 0)
ocsp.t TEST 8: create OCSP request (empty string cert chain) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 8: create OCSP request (empty string cert chain) - pattern "failed to create OCSP request: d2i_X509_bio() failed" should match a line in error.log (req 1)
ocsp.t TEST 7: create OCSP request (buffer too small) - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 7: create OCSP request (buffer too small) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 7: create OCSP request (buffer too small) - pattern "failed to create OCSP request: output buffer too small: 68 > 67" should match a line in error.log (req 0)
ocsp.t TEST 7: create OCSP request (buffer too small) - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 7: create OCSP request (buffer too small) - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 7: create OCSP request (buffer too small) - pattern "failed to create OCSP request: output buffer too small: 68 > 67" should match a line in error.log (req 1)
ocsp.t TEST 16: good status req from client - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 16: good status req from client - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 16: good status req from client - pattern "ocsp status resp set ok: nil," should match a line in error.log (req 0)
ocsp.t TEST 16: good status req from client - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 16: good status req from client - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 16: good status req from client - pattern "ocsp status resp set ok: nil," should match a line in error.log (req 1)
ocsp.t TEST 17: no status req from client - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 17: no status req from client - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 17: no status req from client - pattern "ocsp status resp set ok: no status req," should match a line in error.log (req 0)
ocsp.t TEST 17: no status req from client - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 17: no status req from client - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 17: no status req from client - pattern "ocsp status resp set ok: no status req," should match a line in error.log (req 1)
ocsp.t TEST 10: validate good OCSP response - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 10: validate good OCSP response - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 0)
ocsp.t TEST 10: validate good OCSP response - pattern "OCSP response validation ok" should match a line in error.log (req 0)
ocsp.t TEST 10: validate good OCSP response - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
connected: 1
-ssl handshake: userdata
+failed to do SSL handshake: handshake failed
'
ocsp.t TEST 10: validate good OCSP response - pattern "lua ssl server name: "test.com"" should match a line in error.log (req 1)
ocsp.t TEST 10: validate good OCSP response - pattern "OCSP response validation ok" should match a line in error.log (req 1)
pipe-stderr.t TEST 7: read stderr, pattern is read any - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
pipe-stderr.t TEST 7: read stderr, pattern is read any - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
pipe-stdin.t TEST 1: write process - response_body - response is expected (repeated req 0, req 0) @@ -1,4 +1,4 @@
0
5
6
-hello world
+h
'
pipe-stdin.t TEST 1: write process - response_body - response is expected (repeated req 1, req 0) @@ -1,4 +1,4 @@
0
5
6
-hello world
+h
'
pipe-stdin.t TEST 8: write and read process - response_body - response is expected (repeated req 0, req 0) got: 'a
'
expected: 'payload
'
pipe-stdin.t TEST 8: write and read process - response_body - response is expected (repeated req 1, req 0) got: 'a
'
expected: 'payload
'
pipe-stdin.t TEST 9: write process, support table, number and boolean arguments - response_body - response is expected (repeated req 0, req 0) @@ -1,3 +1,3 @@
2
11
-10hello world
+1
'
pipe-stdin.t TEST 9: write process, support table, number and boolean arguments - response_body - response is expected (repeated req 1, req 0) @@ -1,3 +1,3 @@
2
11
-10hello world
+1
'
pipe-stdout.t TEST 11: read process, pattern is read any, with limited, limit smaller than read data - response_body - response is expected (repeated req 0, req 0) @@ -1,3 +1,3 @@
-hell
+h
-o
+e
-world
+l
'
pipe-stdout.t TEST 11: read process, pattern is read any, with limited, limit smaller than read data - response_body - response is expected (repeated req 1, req 0) @@ -1,3 +1,3 @@
-hell
+h
-o
+e
-world
+l
'
pipe-stdout.t TEST 10: read process, pattern is read any, with limited, limit larger than read data - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
pipe-stdout.t TEST 10: read process, pattern is read any, with limited, limit larger than read data - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
pipe-stdout.t TEST 30: user case with read and wait - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1 @@
-ok
exit
'
pipe-stdout.t TEST 30: user case with read and wait - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1 @@
-ok
exit
'
pipe-stdout.t TEST 21: read process, mix read pattern - response_body - response is expected (repeated req 0, req 0) @@ -1,13 +1,13 @@
reading any
-hello
+h
reading 3
-wor
+ell
reading line
-ld
+oworld
reading 2
mo
reading any
-re
-
+r
reading all
+e
data
'
pipe-stdout.t TEST 21: read process, mix read pattern - response_body - response is expected (repeated req 1, req 0) @@ -1,13 +1,13 @@
reading any
-hello
+h
reading 3
-wor
+ell
reading line
-ld
+oworld
reading 2
mo
reading any
-re
-
+r
reading all
+e
data
'
pipe-stdout.t TEST 8: read process, pattern is read any - response_body - response is expected (repeated req 0, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
pipe-stdout.t TEST 8: read process, pattern is read any - response_body - response is expected (repeated req 1, req 0) @@ -1,2 +1,2 @@
-hello
+h
-world
+e
'
re-opt.t TEST 1: default jit_stack_size too small - response_body - response is expected (repeated req 0, req 0) got: 'from: 1
to: 1563
'
expected: 'error: pcre_exec() failed: -27
'
re-opt.t TEST 1: default jit_stack_size too small - response_body - response is expected (repeated req 1, req 0) got: 'from: 1
to: 1563
'
expected: 'error: pcre_exec() failed: -27
'

Warnings

Go back to the index page.