All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: marcandre.lureau@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [Fail] tests/test-util-filemonitor fails
Date: Fri, 9 Aug 2019 10:12:14 +0100	[thread overview]
Message-ID: <20190809091214.GD13660@redhat.com> (raw)
In-Reply-To: <20190809000609.GA4201@richard>

On Fri, Aug 09, 2019 at 08:06:09AM +0800, Wei Yang wrote:
> On Thu, Aug 08, 2019 at 10:22:13AM +0100, Daniel P. Berrangé wrote:
> >On Thu, Aug 08, 2019 at 04:46:53PM +0800, Wei Yang wrote:
> >> On Thu, Aug 08, 2019 at 09:02:29AM +0100, Daniel P. Berrangé wrote:
> >> >On Thu, Aug 08, 2019 at 10:07:23AM +0800, Wei Yang wrote:
> >> >> Current qemu fails tests/test-util-filemonitor.
> >> >
> >> >You'll need to provide more info. The test works for me and passes in all
> >> >the QEMU CI environments.
> >> >
> >> 
> >> The error message from my side is:
> >> 
> >> /util/filemonitor: Expected watch id 200000000 but got 100000000
> >> **
> >> ERROR:tests/test-util-filemonitor.c:665:test_file_monitor_events: assertion failed: (err == 0)
> >> 
> >> What else you'd prefer to have?
> >
> >Can you set the  "FILEMONITOR_DEBUG=1" env variable before running
> >the test - it will print out lots more info
> >
> 
> Here is the output with more info.
> 
>     $ FILEMONITOR_DEBUG=1 QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 tests/test-util-filemonitor

>     Rmdir /tmp/test-util-filemonitor-151B6Z/fish
>     Event id=200000000 event=4 file=
>     Expected watch id 200000000 but got 100000000
>     **

Ok, so the kernel is sending the events in an unexpected order

>     ERROR:tests/test-util-filemonitor.c:665:test_file_monitor_events: assertion failed: (err == 0)
>     Aborted (core dumped)
> 
> 
> >Also what operating system are you using, and what kernel version
> >
> 
> OS: Ubuntu 18.04.2 LTS
> Kernel: I built the kernel whose last commit is bed38c3e2dca.

Does it work if you use the normal LTS kernel package instead.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  reply	other threads:[~2019-08-09  9:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  2:07 [Qemu-devel] [Fail] tests/test-util-filemonitor fails Wei Yang
2019-08-08  8:02 ` Daniel P. Berrangé
2019-08-08  8:46   ` Wei Yang
2019-08-08  9:22     ` Daniel P. Berrangé
2019-08-09  0:06       ` Wei Yang
2019-08-09  9:12         ` Daniel P. Berrangé [this message]
2019-08-12  0:49           ` Wei Yang
2019-11-04 19:35           ` Miguel Arruga Vivas
2019-11-05  9:54             ` Daniel P. Berrangé
2019-11-08  8:52               ` Miguel Arruga Vivas

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=20190809091214.GD13660@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richardw.yang@linux.intel.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.
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.