[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bisecting display bugs
From: |
Óscar Fuentes |
Subject: |
Re: Bisecting display bugs |
Date: |
Mon, 11 Jul 2016 03:40:26 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Clément Pit--Claudel <address@hidden> writes:
> I've written up notes while bisecting a display bug (#23938) on
> master. Since it didn't seem easy to identify the problem
> automatically from Elisp, I used a small `git bisect run' script that
> automatically captured, cropped, and compared screenshots of Emacs
> against a known-good reference. All in all, things worked nicely: git
> bisect took 4 hours to complete, but it didn't require any interaction
> after starting.
>
> I attached my notes. Is there interest in including them in admin/notes/?
Speaking as someone who painfully bisected Emacs many times (read:
having to visually check good/bad result on each iteration), the part
about comparing the display's image against a good sample is highly
interesting, and not only for hunting display bugs.