ska-sa / spead2 / 818

73%

master: 79%

Pull #83

travis-ci

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.

7 of 7 new or added lines in 3 files covered. (100.0%)

3052 of 4157 relevant lines covered (73.42%)

138519.97 hits per line