3
83%
master: 88%

Ran 08 Jun 2018 06:58PM UTC

Files 301

Run time 2min

Badge

Embed ▾

Committed 08 Jun 2018 05:01PM UTC coverage: 81.8% (-0.08%) from 81.883%

Job # TARGET=coverage

Build Type

push

travis-ci

Committed by

kostja

Commit Message

netbox: introduce iterable future objects

Netbox has two major ways to execute a request: sync and async.
During execution of any a server can send multiplie responses via
IPROTO_CHUNK. And the execution ways differ in how to handle the
chunks (called messages or pushes).

For a sync request a one can specify on_push callback and its
on_push_ctx argument called on each message.

When a request is async a user has a future object only, and can
not specify any callbacks. To get the pushed messages a one must
iterate over future object like this:
for i, message in future:pairs(one_iteration_timeout) do
...
end
Or ignore messages just calling future:wait_result(). Anyway
messages are not deleted, so a one can iterate over future object
again and again.

Follow up #2677

Coverage Stats

39440 of 48215 relevant lines covered (81.8%)

902675.5 hits per line

tarantool / tarantool / 12462 / 3
83%
master: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 12462.3 (TARGET=coverage)

tarantool / tarantool / 12462 / 3 83% master: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 12462.3 (TARGET=coverage)

tarantool / tarantool / 12462 / 3
83%
master: 88%

README BADGES
x