netty5/resolver-dns/src/test/java/io/netty/resolver/dns
Norman Maurer dbd2282abe DnsNameResolver should log in trace level if notification of the promise fails (#9022)
Motivation:

During investigating some other bug I noticed that we log with warn level if we fail to notify the promise due the fact that it is already full-filled. This is not correct and missleading as there is nothing wrong with it in general. A promise may already been fullfilled because we did multiple queries and one of these was successful.

Modifications:

- Change log level to trace
- Add unit test which before did log with warn level but now does with trace level.

Result:

Less missleading noise in the log.
2019-04-10 07:14:18 +02:00
..
DefaultAuthoritativeDnsServerCacheTest.java migrate java8: use lambda and method reference (#8781) 2019-01-29 14:06:05 +01:00
DefaultDnsCacheTest.java migrate java8: use lambda and method reference (#8781) 2019-01-29 14:06:05 +01:00
DefaultDnsCnameCacheTest.java migrate java8: use lambda and method reference (#8781) 2019-01-29 14:06:05 +01:00
DnsNameResolverClientSubnetTest.java remove unused import statement (#8792) 2019-01-28 16:50:15 +01:00
DnsNameResolverTest.java DnsNameResolver should log in trace level if notification of the promise fails (#9022) 2019-04-10 07:14:18 +02:00
DnsServerAddressesTest.java Java 8 migration: Use diamond operator (#8749) 2019-01-22 16:07:26 +01:00
NameServerComparatorTest.java Java 8 migration: Use diamond operator (#8749) 2019-01-22 16:07:26 +01:00
SearchDomainTest.java migrate java8 (#8779) 2019-01-28 05:55:30 +01:00
TestDnsServer.java DnsNameResolver should log in trace level if notification of the promise fails (#9022) 2019-04-10 07:14:18 +02:00
UnixResolverDnsServerAddressStreamProviderTest.java Correctly parse /etc/resolv.conf when contain multiple entries for searchdomain. (#8351) 2018-10-12 05:00:32 +02:00