aboutsummaryrefslogtreecommitdiff
path: root/test/unit/eval/decode_spec.lua
Commit message (Collapse)AuthorAge
* unittests: Fix linter errorZyX2017-04-09
|
* unittests: Do not alter p_enc in decode unit testZyX2017-04-08
|
* eval: Split eval.c into smaller filesZyX2017-03-29
|
* unittests: Fix linter errorsZyX2017-03-11
|
* unittests: Do not import libnvim or headers in main processZyX2017-03-11
| | | Slows down unit tests much, but gets rid of as much preserved state as possible.
* unittests: Check core dumps in after_each, like in functestsZyX2017-03-11
|
* unittests: Run all unit tests in their own processesZyX2017-03-11
| | | | | | | | | | | | | | | Used sed -r -i -e '/ helpers =/ s/$/\nlocal itp = helpers.gen_itp(it)/; s/^(\s*)it\(/\1itp(/' test/unit/**/*_spec.lua to alter all tests. Locally they all run fine now. Reasoning: 1. General: state from one test should not affect other tests. 2. Local: travis build is failing with something which may be an output of garbage collector. This should prevent state of the garbage collector from interferring as well.
* build: Target luacheck HEAD.Justin M. Keyes2016-11-17
| | | | | | | | | | | | https://github.com/mpeterv/luacheck/pull/81#issuecomment-261099606 > If you really want to use bleeding-edge version you should get the > rockspec from master branch, not a fixed commit ... > The correct way to install from a specific commit is cloning that > commit and running "luarocks make" from project directory. The reason > is that running "install" or "build" on an scm rockspec fetches > sources from master but uses build description from the rockspec > itself, which may be outdated.
* functests: Replace \xXX escapes with \DDD in lua codeZyX2016-04-18
|
* eval/decode: Do not overflow when parsing `-`ZyX2016-04-18
| | | Also makes if’s less nested.
* eval/decode: Make sure that error messages do not cause overflowZyX2016-04-18
|
* eval/decode: Make sure that parsing strings does not overflowZyX2016-04-18
|
* eval/decode: Avoid overflow when parsing incomplete null/true/falseZyX2016-04-18
Note: second test does not crash or produce asan errors, even though it should.