# testing : code for /modules/lua/setheaders.lua
# expected: 200
# received: '500'
not ok 49
# testing : response content for /modules/lua/setheaders.lua
# expected: ''
# received: '<h3>Error!</h3>
# <pre>...httpd-test/framework/t/htdocs/modules/lua/setheaders.lua:4: attempt
to index a nil value (global \'apr_table\')</pre>
# '
not ok 50
ok 51 # skip
# 'X-Header' header value is 'yes' (expected 'yes')
# 'X-Host' header value is 'localhost:8529' (expected 'localhost:8529')
# 'X-Compat' header value is '<unset>' (expected 'compat')
not ok 52
# Failed test 49 in t/modules/lua.t at line 52 fail #13
# Failed test 50 in t/modules/lua.t at line 53 fail #13
# Failed test 52 in t/modules/lua.t at line 72
Failed 3/52 subtests
(less 24 skipped subtests: 25 okay)
> On Jul 6, 2017, at 8:16 AM, Jim Jagielski <j...@jagunet.com> wrote:
>
> The biggest issue, for me, is that currently the
> test framework returns loads of errors on mod_lua;
> either we "fix" mod_lua or we "fix" the tests but having
> it the way it is now is kinda wonky :-)
