commit | 0ad80e971257a5628b1fedd28001cd1e4b6407bb | [log] [tgz] |
---|---|---|
author | Bernie Innocenti <codewiz@google.com> | Thu Jan 23 22:20:44 2020 +0900 |
committer | Bernie Innocenti <codewiz@google.com> | Fri Jan 24 15:38:42 2020 +0900 |
tree | 85a6de05443a99e1d396a7a7819c98839c145db3 | |
parent | 10a902831e48dd3d3e3ced7620f384f3476d7dd6 [diff] |
Make TlsBypass and PrefixDiscoveryBypassTls non-flaky The problem was caused by a race between the test code calling DnsTlsFrontend::clearQueries() after receiving the query response, but before the server had actually incremented the query count. Using an atomic<int> for the counter doesn't help us here. A more robust synchronization would involve a mutex and a condition variable, similar to how DnsMetricsListener::waitForPrivateDnsValidation() does it. Change-Id: Id78180f1e168d8385b5f0d711106adee35f146ee
This code uses LOG(X) for logging. Log levels are VERBOSE,DEBUG,INFO,WARNING and ERROR. The default setting is WARNING and logs relate to WARNING and ERROR will be shown. If you want to enable the DEBUG level logs, using following command. adb shell service call dnsresolver 10 i32 1 VERBOSE 0 DEBUG 1 INFO 2 WARNING 3 ERROR 4 Verbose resolver logs could contain PII -- do NOT enable in production builds.