Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.5

Operating System version: win10

Java version: 1.8

Pls. provide [GitHub address] to reproduce this issue.

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.apache.dubbo.rpc.RpcException: Failed to invoke remote service: interface com.wenbin.grpc.services.DubboGreeterGrpc$IGreeter, method: sayHello, cause: INTERNAL: Panic! This is a bug!] with root cause

java.lang.AbstractMethodError: io.grpc.netty.NettyChannelBuilder$NettyTransportFactory.newClientTransport(Ljava/net/SocketAddress;Lio/grpc/internal/ClientTransportFactory$ClientTransportOptions;Lio/grpc/ChannelLogger;)Lio/grpc/internal/ConnectionClientTransport;
at io.grpc.internal.CallCredentialsApplyingTransportFactory.newClientTransport(CallCredentialsApplyingTransportFactory.java:49) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.internal.InternalSubchannel.startNewTransport(InternalSubchannel.java:246) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.internal.InternalSubchannel.access$400(InternalSubchannel.java:65) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.internal.InternalSubchannel$2.run(InternalSubchannel.java:196) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.SynchronizationContext.drain(SynchronizationContext.java:95) ~[grpc-api-1.22.1.jar:1.22.1]
at io.grpc.SynchronizationContext.execute(SynchronizationContext.java:127) ~[grpc-api-1.22.1.jar:1.22.1]
at io.grpc.internal.ManagedChannelImpl$NameResolverListener.onResult(ManagedChannelImpl.java:1365) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:311) ~[grpc-core-1.22.1.jar:1.22.1]
at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:213) ~[grpc-core-1.22.1.jar:1.22.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_171]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_171]

Issue 2:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: master branch

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

Travis-cli has a 4MB hard limit of log size [1].

Currently, our Travis log[2] is about 3.98MB, we are almost there.

We can reduce some trivial log in the console output, but keep a full log in the local file.

For example, test case org.apache.dubbo.rpc.validation.�ValidationTest� eats about 1.3MB in travis log. We can start from here.

[1]. https://docs.travis-ci.com/user/common-build-problems/#log-length-exceeded

[2]. https://api.travis-ci.org/v3/job/484750418/log.txt

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!