From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: video_checksum.c test failure
Date: Wed, 27 Jul 2016 07:36:57 +0300 [thread overview]
Message-ID: <58541ba0-a177-f01c-a237-47827ffc4938@gmail.com> (raw)
In-Reply-To: <87oa61lmwq.fsf@gnu.org>
13.07.2016 15:53, Ludovic Courtès пишет:
> Hello!
>
> With 2.02~beta3 we’re experiencing the same test failure as described at
> <https://lists.gnu.org/archive/html/grub-devel/2013-11/msg00242.html>.
> This is in an environment that contains a bunch of UTF-8 locales and has
> LC_ALL=en_US.utf8, FWIW.
>
> Any idea about what could be missing from our build environment, or
> additional info we could provide to investigate?
>
It verifies exact content of video memory, which in particular depends
on exact fonts used as source of GRUB fonts (of course there could also
be some locale mismatch). So I am afraid this test can pass only on the
system used to generate this video memory content. I think we simply
should disable this test by default.
prev parent reply other threads:[~2016-07-27 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 12:53 video_checksum.c test failure Ludovic Courtès
2016-07-27 4:36 ` Andrei Borzenkov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58541ba0-a177-f01c-a237-47827ffc4938@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=janneke@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.
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 NNTP newsgroup(s).