You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ravi/lua-tests
Dibyendu Majumdar 9d65c41a3b
issue #169 temp change to test case
4 years ago
..
libs rename lua tests folder (version identifier removed) 9 years ago
ltests issue #119 7 years ago
README.rst Update README.rst 6 years ago
all.lua issue #141 amend tests to make them work reasonably 6 years ago
api.lua issue #119 7 years ago
attrib.lua issue #119 7 years ago
big.lua issue #119 7 years ago
bitwise.lua issue #119 7 years ago
calls.lua issue #119 7 years ago
closure.lua issue #119 7 years ago
code.lua issue #157 more renaming of bytecodes 6 years ago
constructs.lua issue #141 amend tests to make them work reasonably 6 years ago
coroutine.lua issue #119 7 years ago
db.lua issue #119 7 years ago
errors.lua issue #158 fix test failure 6 years ago
events.lua issue #119 7 years ago
files.lua issue #119 7 years ago
gc.lua issue #119 7 years ago
goto.lua issue #119 7 years ago
literals.lua issue #119 7 years ago
locals.lua issue #119 7 years ago
main.lua issue #119 7 years ago
math.lua issue #158 fix test failure 6 years ago
nextvar.lua issue #169 temp change to test case 4 years ago
pm.lua issue #119 7 years ago
run_tests.sh rename lua tests folder (version identifier removed) 9 years ago
run_travis_tests.sh make travis tests run faster by running a subset 7 years ago
sort.lua issue #119 7 years ago
strings.lua issue #119 7 years ago
tpack.lua issue #119 7 years ago
utf8.lua issue #119 7 years ago
vararg.lua issue #119 7 years ago
verybig.lua issue #119 7 years ago

README.rst

Lua 5.3.x Tests

===============

This folder contains a copy of the Lua 5.3 tests, amended slightly for Ravi. The changes are to skip some
tests that fail in Ravi due to lack of support for certain features of Lua - e.g. recursion limit for tail calls,
or other limits such as number of variables.

Notes
-----
* The Lua 'ltests' library is included in Ravi in Debug builds.
* The tests may crash on Windows 64-bit environment when JIT mode is enabled; this appears to be due to lack of
support for Windows (64-bit) stack unwinding in the JIT backends. See issue #30. The 32-bit build does not have this
issue.
* In JIT mode the tests take much longer to run, especially if full JIT is switched on. This is because the tests
generate a lot of small Lua functions dynamically - in thousands - and all the time is spent in JIT compiling
these functions.