grpc / grpc-java / 3095 / 1

87%

master: 89%

Pull #1527

travis-ci

<a href="https://github.com/grpc/grpc-java/commit/<a class=hub.com/grpc/grpc-java/commit/bf8e4968e8c64f9fea442a8b5b15577f31b87b66">bf8e4968e<a href="https://github.com/grpc/grpc-java/commit/bf8e4968e8c64f9fea442a8b5b15577f31b87b66">&quot;&gt;Run createTransportRunnable outside of lock.

Because `scheduleConnection()` is run under lock, if we ran
`createTransportRunnable` inside `scheduleConnection()`,
`savedDelayedTransport.setTransport()` will be under lock which violates
the assumption made in https://github.com/grpc/grpc-java/issues/1408 that

&amp;gt; there is an implicit rule today that channel layer will not hold any lock while calling into transport

and had caused deadlock with `InProcessTransport`.

This is a partial back-port of </a><a class="double-link" href="https://github.com/grpc/grpc-java/commit/<a class="double-link" href="https://github.com/grpc/grpc-java/commit/0e14516f5a5cbee5e60e467bfbc48a8a3197ff40">0e14516f5</a>">0e14516f5</a><a href="https://github.com/grpc/grpc-java/commit/bf8e4968e8c64f9fea442a8b5b15577f31b87b66">
from master. A large portion of changes on tests is not ported because
of conflict caused by API changes in master.

5625 of 6450 relevant lines covered (87.21%)

0.87 hits per line