<div dir="ltr">On Wed, Jan 15, 2014 at 10:54 PM, Alexey Proskuryakov <span dir="ltr"><<a href="mailto:ap@webkit.org" target="_blank">ap@webkit.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>(re-sent from a correct address)</div>
<div><br></div><div>I think that it's good to try not dumping build failures into comments right away, and to see what happens.</div><div class="im"><div><br></div><div>As for not showing style bot failures, it seems almost certain that this will make them substantially more annoying to work with. Can you describe the workflow for patch author and reviewer to deal with style bot warnings when they are not inline? Manually finding relevant lines by number can't work.</div>
<div><br></div><div>I agree with Tim that dumping all tested paths along with style warnings is silly. How hard would it be it to get rid of that?</div></div></div></blockquote><div><br></div><div>The workflow is to click on the bubble to see the style errors. e.g.</div>
<div><a href="https://webkit-queues.appspot.com/results/6544662978363392">https://webkit-queues.appspot.com/results/6544662978363392</a><br></div><div><br></div><div>- R. Niwa</div><div><br></div></div></div></div>