1
88%
dev: 88%

Ran 02 Jun 2016 11:24PM UTC

Files 42

Run time 3s

Badge

Embed ▾

Committed 02 Jun 2016 11:21PM UTC coverage: 86.224% (+0.9%) from 85.316%

Job # TEST_TIMEOUT_SCALE=20

Build Type

push

travis-ci

Committed by

prashantv

Commit Message

Fix channel close not checking state under write lock

It's possible for multiple connections to close and trigger
connectionCloseStateChange from multiple goroutines.

This could lead to:

G1: C1 closes, and runs connectionCloseStateChange
G1: Finds minState connectionInboundClosed
G1: updateTo = ChannelInboundClosed
<g1 scheduled off before it completes>
G2: C2 closes, and runs connectionCloseStateChange
G2: Finds minState connectionClosed
G2: updateTo = ChannelClosed
G2: Updates channel state to ChannelClosed
<g1 is rescheduled>
G1: Grabs state lock, and sets state to ChannelInboundClosed

Since all connections are closed, the channel will be stuck in
ChannelInboundClosed.

We should be checking that the decision we made is not stale by
comparing the state matches what we had before the lock when making
the change.

Run Details

3749 of 4348 relevant lines covered (86.22%)

2825.56 hits per line

uber / tchannel-go / 1988 / 1
88%
dev: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1988.1 (TEST_TIMEOUT_SCALE=20)

uber / tchannel-go / 1988 / 1 88% dev: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1988.1 (TEST_TIMEOUT_SCALE=20)

uber / tchannel-go / 1988 / 1
88%
dev: 88%

README BADGES
x