<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Cool, I'll work up a patch for this.<div class=""><br class=""></div><div class="">And thanks for commenting on PR<span style="color: rgba(0, 0, 0, 0.85098); font-family: 'Helvetica Neue';" class="">36494, I'm testing a fix out right now :).</span></div><div class=""><font color="rgba(0, 0, 0, 0.85098)" face="Helvetica Neue" class=""><br class=""></font></div><div class=""><font color="rgba(0, 0, 0, 0.85098)" face="Helvetica Neue" class="">vedant</font></div><div class=""><font color="rgba(0, 0, 0, 0.85098)" face="Helvetica Neue" class=""><br class=""></font><div style=""><blockquote type="cite" class=""><div class="">On Feb 23, 2018, at 3:35 PM, Pavel Labath <<a href="mailto:labath@google.com" class="">labath@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 23 February 2018 at 15:17, Vedant Kumar <<a href="mailto:vsk@apple.com" class="">vsk@apple.com</a>> wrote:<br class=""><blockquote type="cite" class="">Second, TestClient::SendMessage is generating quite a lot of "INFO" output which clutters up the terminal. Pavel, would you mind if I removed this logging?<br class=""><br class=""></blockquote><br class="">Yeah, we should probably do that. The idea here was that the packet<br class="">log would provide you with additional context for the situation when<br class="">the test fails, but it *is* very verbose. I'll have to come up with a<br class="">better solution for error reporting here.<br class=""></div></div></blockquote></div><br class=""></div></body></html>