From: Wei Yang <richardw.yang@linux.intel.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: marcandre.lureau@redhat.com,
Wei Yang <richardw.yang@linux.intel.com>,
dgilbert@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Fail] tests/test-util-filemonitor fails
Date: Fri, 9 Aug 2019 08:06:09 +0800 [thread overview]
Message-ID: <20190809000609.GA4201@richard> (raw)
In-Reply-To: <20190808092213.GB2534@redhat.com>
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
/util/filemonitor: Add watch /tmp/test-util-filemonitor-151B6Z (null)
Watch ID 100000000
Add watch /tmp/test-util-filemonitor-151B6Z one.txt
Watch ID 100000001
Add watch /tmp/test-util-filemonitor-151B6Z two.txt
Watch ID 100000002
Create /tmp/test-util-filemonitor-151B6Z/one.txt
Event id=100000000 event=0 file=one.txt
Event id=100000001 event=0 file=one.txt
Create /tmp/test-util-filemonitor-151B6Z/two.txt
Event id=100000000 event=0 file=two.txt
Event id=100000002 event=0 file=two.txt
Create /tmp/test-util-filemonitor-151B6Z/three.txt
Event id=100000000 event=0 file=three.txt
Unlink /tmp/test-util-filemonitor-151B6Z/three.txt
Event id=100000000 event=2 file=three.txt
Rename /tmp/test-util-filemonitor-151B6Z/one.txt -> /tmp/test-util-filemonitor-151B6Z/two.txt
Event id=100000000 event=2 file=one.txt
Event id=100000001 event=2 file=one.txt
Event id=100000000 event=0 file=two.txt
Event id=100000002 event=0 file=two.txt
Append /tmp/test-util-filemonitor-151B6Z/two.txt
Event id=100000000 event=1 file=two.txt
Event id=100000002 event=1 file=two.txt
Touch /tmp/test-util-filemonitor-151B6Z/two.txt
Event id=100000000 event=3 file=two.txt
Event id=100000002 event=3 file=two.txt
Del watch /tmp/test-util-filemonitor-151B6Z 100000001
Add watch /tmp/test-util-filemonitor-151B6Z one.txt
Watch ID 100000003
Create /tmp/test-util-filemonitor-151B6Z/one.txt
Event id=100000000 event=0 file=one.txt
Event id=100000003 event=0 file=one.txt
Del watch /tmp/test-util-filemonitor-151B6Z 100000003
Unlink /tmp/test-util-filemonitor-151B6Z/one.txt
Event id=100000000 event=2 file=one.txt
Mkdir /tmp/test-util-filemonitor-151B6Z/fish
Event id=100000000 event=0 file=fish
Add watch /tmp/test-util-filemonitor-151B6Z fish/
Watch ID 200000000
Add watch /tmp/test-util-filemonitor-151B6Z fish/one.txt
Watch ID 200000001
Create /tmp/test-util-filemonitor-151B6Z/fish/one.txt
Event id=200000000 event=0 file=one.txt
Event id=200000001 event=0 file=one.txt
Del watch /tmp/test-util-filemonitor-151B6Z 200000001
Rename /tmp/test-util-filemonitor-151B6Z/fish/one.txt -> /tmp/test-util-filemonitor-151B6Z/two.txt
Event id=200000000 event=2 file=one.txt
Event id=100000000 event=0 file=two.txt
Event id=100000002 event=0 file=two.txt
Rmdir /tmp/test-util-filemonitor-151B6Z/fish
Event id=200000000 event=4 file=
Expected watch id 200000000 but got 100000000
**
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.
>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 :|
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-08-09 0:07 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 [this message]
2019-08-09 9:12 ` Daniel P. Berrangé
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=20190809000609.GA4201@richard \
--to=richardw.yang@linux.intel.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@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).