From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/02: gnu: qemu: Update to 2.9.0 [security fixes].
Date: Fri, 21 Apr 2017 15:02:40 -0400 [thread overview]
Message-ID: <20170421190240.GA26110@jasmine> (raw)
In-Reply-To: <8737d1zk6n.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-04-21 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170420182405.2682.82446@vcs0.savannah.gnu.org>
[not found] ` <20170420182405.ED2D520740@vcs0.savannah.gnu.org>
2017-04-21 1:06 ` 01/02: gnu: qemu: Update to 2.9.0 [security fixes] Mark H Weaver
2017-04-21 17:37 ` Leo Famulari
2017-04-21 18:31 ` Mark H Weaver
2017-04-21 19:02 ` Leo Famulari [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=20170421190240.GA26110@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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.