On Fri, Apr 21, 2017 at 02:31:44PM -0400, Mark H Weaver wrote:
> Leo Famulari <leo@famulari.name> writes:
> > On Thu, Apr 20, 2017 at 09:06:51PM -0400, Mark H Weaver wrote:
> >>   FAIL: grub_cmd_set_date
> >>   =======================
> >
> >> Has anyone else seen this?
> >
> > I just ran the build 5 times on my x86_64 machine, and it failed this
> > test 1/5 times.
> >
> > We could try patching the test file with 'set -x' to trace the execution
> > of the script and see exactly what goes wrong.
> 
> Of course it would be good to investigate, but for now, here is the
> patch that I used to disable that one test.

> From 3ea154ed0dff96c348a0ee5a3a45678fc8a1dfb5 Mon Sep 17 00:00:00 2001
> From: Mark H Weaver <mhw@netris.org>
> Date: Thu, 20 Apr 2017 21:14:45 -0400
> Subject: [PATCH] DRAFT: gnu: grub: Disable failing test.
> 
> * gnu/packages/bootloaders.scm (grub)[arguments]: Add 'disable-failing-test'
> phase.

Okay, sounds good. Can you forward this report to <bug-grub@gnu.org>?

By the way, I'm testing the latest release of grub, 2.02~rc2, and this
test is flaky there, too.