tarantool / tarantool / 17754

83%

master: 88%

push

travis-ci

<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/a7d003a354d75b6ff8e4831f9ec4b7c985bdcf84">a7d003a35<a href="https://github.com/tarantool/tarantool/commit/a7d003a354d75b6ff8e4831f9ec4b7c985bdcf84">&quot;&gt;test: fix net.box occasional failure. Again

The test regarding logging corrupted rows failed occasionally with
```
[016]  test_run:grep_log(&amp;#39;default&amp;#39;, &amp;#39;Got a corrupted row.*&amp;#39;)
[016]  ---
[016] -- &amp;#39;Got a corrupted row:&amp;#39;
[016] +- null
[016]  ...
```
The logs then had
```
[010] 2019-07-06 19:36:16.857 [13046] iproto sio.c:261 !&amp;gt; SystemError writev(1),
called on fd 23, aka unix/:(socket), peer of unix/:(socket): Broken pipe
```
instead of the expected message.

This happened, because we closed a socket before tarantool could write a
greeting to the client, the connection was then closed, and execution
never got to processing the malformed request and thus printing the
desired message to the log.

To fix this, actually read the greeting prior to writing new data and
closing the socket.

Follow-up #4273

(cherry picked from commit </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/eb0cc50ca2773559bb9d25147a786a6786658b78">eb0cc50ca</a>">eb0cc50ca</a><a href="https://github.com/tarantool/tarantool/commit/a7d003a354d75b6ff8e4831f9ec4b7c985bdcf84">)

41597 of 50415 relevant lines covered (82.51%)

843006.5 hits per line