From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 29984-done@debbugs.gnu.org
Subject: bug#29984: core-updates: GRUB test failures
Date: Mon, 29 Jan 2018 14:51:01 +0100 [thread overview]
Message-ID: <87inbkojsq.fsf@gnu.org> (raw)
In-Reply-To: <87lgggc18s.fsf@netris.org> (Mark H. Weaver's message of "Mon, 29 Jan 2018 07:12:35 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Mon, Jan 08, 2018 at 11:56:47AM +0100, Ludovic Courtès wrote:
>>> Leo Famulari <leo@famulari.name> skribis:
>>>
>>> > On Thu, Jan 04, 2018 at 03:05:11PM -0500, Leo Famulari wrote:
>>> >> FAIL: grub_func_test
>>> >
>>> > I saved the failed build tree to get at this test's log. The full
>>> > contents of the log are this line:
>>> >
>>> > Functional test failure:
>>>
>>> Nice. What does upstream say? :-)
>>
>> I'm working on this today; I'll send them a bug report soon.
>>
>> I'm going to try skipping the tests to see if this GRUB can boot a
>> system, and I'm also going to try running the tests on the latest commit
>> from the upstream Git repo.
>
> I believe this is now fixed, by commit
> 0a2a70539bdf42d59c9be5fcbc88a1c14743303a on core-updates.
>
> The problem turned out to be that GRUB's build system couldn't find
> 'freetype', because 'pkg-config' was missing from the build environment.
> This disabled font generation, as I discovered when I booted into a
> core-updates system and found that GRUB was unable to find its font.
>
> After I fixed that problem, I was pleased to find that the test suite
> started succeeding again as well :)
Oh, good catch!
Looks like ‘core-updates’ is getting close to ready…
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-01-29 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 20:01 bug#29984: core-updates: GRUB tests hang after file_filter_test Leo Famulari
2018-01-04 20:05 ` bug#29984: core-updates: GRUB test failures Leo Famulari
2018-01-04 21:53 ` Leo Famulari
2018-01-08 10:56 ` Ludovic Courtès
2018-01-24 22:22 ` Leo Famulari
2018-01-29 12:12 ` Mark H Weaver
2018-01-29 13:51 ` Ludovic Courtès [this message]
2018-01-29 21:25 ` Leo Famulari
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=87inbkojsq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29984-done@debbugs.gnu.org \
--cc=mhw@netris.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.