From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Bisecting display bugs
Date: Mon, 11 Jul 2016 03:40:26 +0200 [thread overview]
Message-ID: <8737nhc5px.fsf@wanadoo.es> (raw)
In-Reply-To: 5782E073.6000505@gmail.com
Clément Pit--Claudel <clement.pit@gmail.com> 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.
next prev parent reply other threads:[~2016-07-11 1:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 23:55 Bisecting display bugs Clément Pit--Claudel
2016-07-11 1:40 ` Óscar Fuentes [this message]
2016-07-11 14:22 ` Eli Zaretskii
2016-07-11 17:46 ` Óscar Fuentes
2016-07-11 17:54 ` Eli Zaretskii
2016-07-11 18:05 ` Óscar Fuentes
2016-07-22 18:55 ` Clément Pit--Claudel
2016-07-23 8:51 ` Eli Zaretskii
2016-07-23 13:22 ` Clément Pit--Claudel
2017-04-16 15:04 ` Clément Pit--Claudel
2017-04-16 15:32 ` Noam Postavsky
2017-04-16 20:57 ` Clément Pit-Claudel
2017-04-17 13:13 ` Herring, Davis
2017-04-17 13:43 ` Teemu Likonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737nhc5px.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).