1
65%
master: 65%

Ran 03 May 2018 11:18PM UTC

Files 146

Run time 8s

Badge

Embed ▾

Committed 03 May 2018 10:45PM UTC coverage: 53.319% (-0.1%) from 53.425%

Job # RACE=false

Build Type

push

travis-ci

Committed by

Roasbeef

Commit Message

peer: ensure msgConsumer sets the shutdown variable on exit

In this commit, we fix a bug that could at times cause a deadlock when a
peer is attempting to disconnect. The issue was that when a peer goes to
disconnect, it needs to stop any active msgStream instances. The Stop()
method of the msgStream would block until an atomic variable was set to
indicate that the stream had fully exited. However, in the case that we
disconnected lower in the msgConsumer loop, we would never set the
streamShutdown variable, meaning that msgStream.Stop() would never
unblock.

The fix for this is simple: set the streamShutdown variable within the
quit case of the second select statement in the msgConsumer goroutine.

Run Details

22596 of 42379 relevant lines covered (53.32%)

16266.28 hits per line

lightningnetwork / lnd / 3820 / 1
65%
master: 65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3820.1 (RACE=false)

lightningnetwork / lnd / 3820 / 1 65% master: 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3820.1 (RACE=false)

lightningnetwork / lnd / 3820 / 1
65%
master: 65%

README BADGES
x