4337
76%

Ran 08 Oct 2018 04:21PM UTC

Jobs 1

Files 267

Run time 14s

Badge

Embed ▾

pending completion

Build # 4337

Build Type

push

travis-ci

Committed by

bluca

Commit Message

Problem: The flag that indicates the next expected message gets set even if the send fails (#3270)

* ZMQ_DGRAM: flip more flag after successful send

In the dgram socket we have a flag that indicates the next expected message type to ensure that always a pair of "address" + "body" messages gets sent. The first one MUST have the sendmore flag, the second MUST NOT.

In case the message does not get sent because of HWM full, then the function returns EAGAIN as it should. But unfortunately the next expected message type-flag gets flipped as well. When the socket_base::send function now tries to resend the message, it became the wrong message type... If you don't stop sending pairs of messages here (like me) then the next message that gets through will be of the wrong type, which in turn crashes the udp_engine function as described in #3268

Run Details

9984 of 12387 relevant lines covered (80.6%)

51952.12 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
8	4337.8 (BUILD_TYPE=coverage CURVE=tweetnacl DRAFT=enabled)	08 Oct 2018 04:21PM UTC	0	80.6	Travis Job 4337.8

Source Files on build 4337

Detailed source file information is not available for this build.

zeromq / libzmq / 4337
76%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 4337

zeromq / libzmq / 4337 76%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 4337

zeromq / libzmq / 4337
76%

README BADGES
x