[Bug 76153] [HSW-M Bisected]multiple small screen shows while running testdisplay -f / fastboot=1 pfit bug
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Sep 29 02:52:14 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=76153
Imre Deak <imre.deak at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Imre Deak <imre.deak at intel.com> ---
(In reply to comment #16)
> (In reply to comment #15)
> > Hi Gordon,
> >
> > Reverting the bisected commit is the best way to make sure the bisect result
> > makes sense. git bisect often ends up in a commit that is not the culprit
> > and knowing if a git revert fixes the issues is a definitive way to be sure.
> >
> > I'd argue that should be the last step in the bisect script, give this info.
> > Sometimes a git revert is not possible or easy though, in which case we
> > can't do that.
>
> Damien, I fully agree with you that reverting the bisected commit is the
> best way to ensure the bisect result (although it doesn't always apply).
>
> But in this case, I don't think Imre is doubting the bisect result.
> Instead, the bug has been fixed, and he wants to know which commit fixes
> the bug. I'd check if this is really necessary as it won't be trivial
> effort (as the test is not automated so auto-bisect won't help here).
Yes, I wanted to know which commit fixed the issue. But I realize that at this
point it's not worth the effort: the bug was reported too long time ago and
based on comment 17, the bisect result isn't useful any more (either because
the bisect result wasn't correct in the first place or something above the
kernel fixed/hid the bug). Assuming this fixed now.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140929/15e99718/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list