2525
90%
master: %

Ran 21 Nov 2016 10:07PM UTC

Jobs 2

Files 110

Run time 2min

Badge

Embed ▾

pending completion

Build # 2525

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

[PeerList][Part 10] Move PeerSubscriber management functions into Peer (#443)

Summary: Due to a potential deadlock situation when a notification
action occurs in the Agent Lock at the same time an Add/Remove occurs in
the PeerList we needed to move the location of PeerSubscription
management into the Peer level. This means that Notifications for peers
will not be entirely threadsafe, but that should be ok. Since the only
actions that should affect the Peer's subscribers(lists) are Retain/Releases
(which should be triggered by the lists) most inconsistency situations
can safely be ignored (event after a release) or won't happen fast
enough to matter (If an action occurs on a peer while you are retaining
it, it won't matter because you're going to check it's state at the end
of the retaining anyway)

In the process of doing this I reworked the hostport.Peer tests, but,
only removed a couple of tests from the Agent tests, I'll look into
fixing the agent tests later, but since there was no new functionality
in the agent I didn't see a need for rewriting the tests yet.

Run Details

5241 of 5852 relevant lines covered (89.56%)

1.89 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
3	2525.3 (TYPE=test)	21 Nov 2016 10:07PM UTC	0	89.56	Travis Job 2525.3
4	2525.4 (TYPE=test)	21 Nov 2016 10:09PM UTC	0	89.56	Travis Job 2525.4

Source Files on build 2525

Detailed source file information is not available for this build.

yarpc / yarpc-go / 2525
90%
master: %

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 2525

yarpc / yarpc-go / 2525 90% master: %

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 2525

yarpc / yarpc-go / 2525
90%
master: %

README BADGES
x