aboutsummaryrefslogtreecommitdiff
path: root/test/functional/eval/timer_spec.lua
Commit message (Collapse)AuthorAge
* test: adjust time-sensitive tests (#9220)Justin M. Keyes2018-11-10
| | | | | | | | | | | | | - window_split_tab_spec.lua: Put cursor at bottom of :terminal buffer so that it follows output. - inccommand_spec.lua: Increase timeout to allow 2nd retry. - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms.
* test/timer_spec: relax lower-boundJustin M. Keyes2018-11-05
| | | | | | | | | | | | | Test is unreliable on macOS 10.13. The lower-bound isn't central to the purpose of the test, so just relax it. ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms. related: #6829
* tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|
* test: adjust timer testsJustin M. Keyes2018-10-13
| | | | | Timer tests are less reliable on Travis CI macOS 10.12 (most egregious). Also somewhat on 10.13.
* tests: call getchar(1) in timer callbackJan Edmund Lazo2018-09-04
| | | | Test changes from 8.0.1020 and 8.0.1048.
* functests: Replace execute with either command or feed_commandZyX2017-04-09
| | | | | | | | | | Hope this will make people using feed_command less likely: this hides bugs. Already found at least two: 1. msgpackparse() will show internal error: hash_add() in case of duplicate keys, though it will still work correctly. Currently silenced. 2. ttimeoutlen was spelled incorrectly, resulting in option not being set when expected. Test was still functioning somehow though. Currently fixed.
* functests: Try sleeping a bit moreZyX2017-03-29
|
* test/timer_spec.lua: Relax expected count.Justin M. Keyes2017-01-19
| | | | | | Test sometimes fails on AppVeyor (Windows). 300/50=6, but there could be environment factors that miss the timer interval on the "edges". timer_start() does not have such a hard requirement.
* events: allow event processing in getchar()Björn Linse2016-10-15
| | | | | | this is consistent with vim, and is necessary for plugins that implement their own input modes using "getchar()" and still want to do async event processing.
* tests: don't ignore highlights in various testsBjörn Linse2016-08-14
|
* timers: do not crash after processing events in the handlerBjörn Linse2016-08-10
|
* timers: make repeat=0 work one-shot (consistent with vim)Björn Linse2016-06-29
|
* timers: make timers work with zero timeoutBjörn Linse2016-06-29
|
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
* cmdline: Redraw the cmdline after processing eventsBjörn Linse2016-05-24
| | | | | | | vim-patch:7.4.1603 TODO(bfredl): if we allow events in HITRETURN and ASKMORE states, we need to add the necessary redraws as well.
* eval: implement timers. vim-patch: 7.4.1578, 7.4.1831Björn Linse2016-05-24
For the moment, timers are triggered during sleep, but not in wait-for-input modes, like press-RETURN or f_getchar()
generated by cgit (git 2.34.1) at 2025-05-10 05:39:25 +0000