1
73%
master: 79%

Ran 13 Nov 2019 09:28AM UTC

Files 100

Run time 4s

Badge

Committed 13 Nov 2019 08:49AM UTC coverage: 73.394%. First build

Job # COVERAGE=yes TEST_PYTHON=yes PYTHON=python3 CC="gcc" TEST_CXX=yes CXX="g++" RECVMMSG=yes SENDMMSG=yes EVENTFD=yes IBV=yes PCAP=yes

Build Type

push

travis-ci

Committed by

bmerry

Commit Message

When a completion channel is ready, consume all events from it.

This has two effects:
- If epoll spuriously indicates that there is an event to read, it
  prevents the worker thread throwing an exception. This seems to happen
  when using a thread pool with multiple threads. I haven't yet
  determined if that's a bug in Boost.Asio, in the Mellanox drivers, or
  is just expected.
- If a notification is requested, but then new completion queue entries
  are observed before waiting for the notification, it's possible for
  the notification to just lurk in the queue and later cause an
  unnecessary wakeup. I don't know if that can actually happen (it's
  unclear from the documentation whether a second notification request
  will cause a second notification in the completion channel), but we're
  now better protected against it.

Run Details

3051 of 4157 relevant lines covered (73.39%)

138514.24 hits per line

Source Files on job 811.1 (COVERAGE=yes TEST_PYTHON=yes PYTHON=python3 CC="gcc" TEST_CXX=yes CXX="g++" RECVMMSG=yes SENDMMSG=yes EVENTFD=yes IBV=yes PCAP=yes)

ska-sa / spead2 / 811 / 1
73%
master: 79%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 811.1 (COVERAGE=yes TEST_PYTHON=yes PYTHON=python3 CC="gcc" TEST_CXX=yes CXX="g++" RECVMMSG=yes SENDMMSG=yes EVENTFD=yes IBV=yes PCAP=yes)

ska-sa / spead2 / 811 / 1 73% master: 79%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 811.1 (COVERAGE=yes TEST_PYTHON=yes PYTHON=python3 CC="gcc" TEST_CXX=yes CXX="g++" RECVMMSG=yes SENDMMSG=yes EVENTFD=yes IBV=yes PCAP=yes)

ska-sa / spead2 / 811 / 1
73%
master: 79%

README BADGES
x