Comment # 8
on bug 85647
from Michel Dänzer
(In reply to Michel Dänzer from comment #7) > 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.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
