<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Random radeonsi crashes with mesa 10.3.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=85647#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Random radeonsi crashes with mesa 10.3.x" href="https://bugs.freedesktop.org/show_bug.cgi?id=85647">bug 85647</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=85647#c7">comment #7</a>) > That doesn't make it impossible, it just means you need patience. Take your > time, and make sure you test each commit for at least as long (preferably > longer, to account for variation) as it's ever taken for the problem to > occur before declaring it good. On the bright side, when the problem occurs > quickly, you know that commit is bad and can move on to the next one. On another bright side, when the problem doesn't occur for a long time, you can enjoy the lack of complaints about it from your son. :) However, it's very important that you don't declare a commit good which would have exhibited the problem after more testing, otherwise the bisection will give the wrong result.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>