1
89%
master: 89%

Ran 10 Dec 2018 06:38PM UTC

Files 254

Run time 45s

Badge

Embed ▾

Committed 10 Dec 2018 06:18PM UTC coverage: 87.016% (+0.006%) from 87.01%

Job # 12388.1

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

core: add LoadBalancer.canHandleEmptyAddressListFromNameResolution() (#5148)

Currently ManagedChannelImpl will interpret empty address list from
NameResolver as an error, and LoadBalancer will NEVER receive an empty
list from handleResolvedAddressGroups().  There is a case in the
request-routing design where a LoadBalancer only receives service
config with which it constructs children NameResolver/LoadBalancer
pairs, thus no address is expected at this level.

canHandleEmptyAddressListFromNameResolution() is a signal to Channel
(and to the parent LoadBalancer in case of hierachical LoadBalancers)
about whether it accepts empty address lists.  The default is false,
which is the current behavior.

The logic is currently duplicated in ManagedChannelImpl and
AutoConfiguredLoadBalancer.  The one in ManagedChannelImpl will be
removed once we delete ManagedChannelBuilder.loadBalancerFactory() as
AutoConfiguredLoadBalancer will always be the top-level LoadBalancer
by then.

Coverage Stats

13792 of 15850 relevant lines covered (87.02%)

0.87 hits per line

grpc / grpc-java / 12388 / 1
89%
master: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 12388.1

grpc / grpc-java / 12388 / 1 89% master: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 12388.1

grpc / grpc-java / 12388 / 1
89%
master: 89%

README BADGES
x