qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 'make check-unit' breakage on s390x host
Date: Thu, 22 Aug 2019 18:01:07 +0200	[thread overview]
Message-ID: <20190822180107.062450ad.cohuck@redhat.com> (raw)
In-Reply-To: <20190822155513.GY3267@redhat.com>

On Thu, 22 Aug 2019 16:55:13 +0100
Daniel P. Berrangé <berrange@redhat.com> wrote:

> On Thu, Aug 22, 2019 at 05:44:47PM +0200, Cornelia Huck wrote:
> > I just noticed a breakage with 'make check-unit' when running on an
> > s390x host (on my laptop, it runs fine; haven't tried other
> > architectures). This happens with current master, but I managed to
> > track the original breakage down to
> > 
> > commit ff3dc8fefe953fd3650279e064bf63b212c5699a
> > Author: Daniel P. Berrangé <berrange@redhat.com>
> > Date:   Wed Mar 13 17:36:18 2019 +0000
> > 
> >     filemon: ensure watch IDs are unique to QFileMonitor scope  
> 
> [snip]
> 
> > I can try to collect extra info if you tell me what would be helpful.  
> 
> I'm betting you updated to kernel 5.3

Yeah, indeed... I would have been surprised if it were s390x-specific :)

> 
>   https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg04349.html
> 
> Just waiting for a Reviewed-by on that patch in order to send a PR....

I'll take a look, but can't promise anything (first time looking at
that code path...)

> 
> Regards,
> Daniel



      reply	other threads:[~2019-08-22 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 15:44 [Qemu-devel] 'make check-unit' breakage on s390x host Cornelia Huck
2019-08-22 15:55 ` Daniel P. Berrangé
2019-08-22 16:01   ` Cornelia Huck [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=20190822180107.062450ad.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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).