unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Miguel Arruga Vivas <rosen644835@gmail.com>
Cc: 37860@debbugs.gnu.org
Subject: bug#37860: qemu-4.1.0 build failure
Date: Sun, 3 Nov 2019 19:01:57 +0100	[thread overview]
Message-ID: <20191103190157.62b84be5@scratchpost.org> (raw)
In-Reply-To: <20191103012739.128b8114@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

Hi,

On Sun, 3 Nov 2019 01:27:49 +0100
Miguel Arruga Vivas <rosen644835@gmail.com> wrote:

> I've hit the same error five times in a row too.  The test seems to
> depend on the order of notifications between two inotify queues (one
> open on the folder and the other one open on the file name).  I don't
> know any easy way to fix it, so I propose to comment it out before
> check phase as in the attached patch.  What do you think?

Sounds like a good idea.

Could you also report a bug upstream at https://bugs.launchpad.net/qemu/ ?

I ask you to do it so that you are credited as the discoverer of the cause of
the bug.

If you do it, please amend your patch to guix to include a link to that report,
I'll be happy to commit it to guix.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-11-03 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 21:39 bug#37860: qemu-4.1.0 build failure Danny Milosavljevic
2019-10-21 21:48 ` Danny Milosavljevic
2019-11-03  0:27   ` Miguel Arruga Vivas
2019-11-03 16:24     ` Marius Bakke
2019-11-03 18:01     ` Danny Milosavljevic [this message]
2019-11-08 13:56       ` bug#37860: [PATCH v2] gnu: qemu: Add upstream patch for failing test Miguel Arruga Vivas
2019-11-10 21:20         ` Marius Bakke

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191103190157.62b84be5@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=37860@debbugs.gnu.org \
    --cc=rosen644835@gmail.com \
    /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/guix.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).