tarantool / tarantool / 15305

83%

master: 87%

push

travis-ci

<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/3a851430a19cb78fe5b93736cf96dbe4a8878a7e">3a851430a<a href="https://github.com/tarantool/tarantool/commit/3a851430a19cb78fe5b93736cf96dbe4a8878a7e">&quot;&gt;Fix tarantool -e &amp;quot;os.exit()&amp;quot; hang

After the patch which made os.exit() execute on_shutdown triggers
(see commit </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/6dc4c8d7b5b40d66fe0451ef4d1f4bdf4d2cf60e">6dc4c8d7b</a>">6dc4c8d7b</a><a href="https://github.com/tarantool/tarantool/commit/3a851430a19cb78fe5b93736cf96dbe4a8878a7e">) we relied
on on_shutdown triggers to break the ev_loop and exit tarantool.
Hovewer, there is an auxiliary event loop which is run in
tarantool_lua_run_script() to reschedule the fiber executing chunks
of code passed by -e option and executing interactive mode.
This event loop is started only to execute interactive mode, and
doesn&#39;t exist during execution of -e chunks. Make sure we don't start
it if os.exit() was already executed in one of the chunks.

Closes #3966

64686 of 78210 relevant lines covered (82.71%)

2742232.58 hits per line