Re: [PATCH 5/5] travis.yml: Compile on arm64, too

[Daniel P . Berrangé]

On Thu, Oct 10, 2019 at 01:57:11PM +0200, Thomas Huth wrote:
> On 10/10/2019 12.58, Daniel P. Berrangé wrote:
> > On Wed, Oct 09, 2019 at 07:07:01PM +0200, Thomas Huth wrote:
> >> Travis now features an arm64 build host, so let's check compilation
> >> there, too.
> >>
> >> Unfortunately, there are some quirks:
> >> - block/ssh.c does not compile properly in this environment, so we have
> >>   to use --disable-libssh until that problem is fixed.
> >> - test-util-filemonitor fails, so we can not run the unit tests there
> > 
> > Do you have any more info on this failure ?
> > 
> > Running tests with FILEMONITOR_DEBUG=1 env variable set will make
> > it print more info
> 
> Here you go:
> 
> https://travis-ci.com/huth/qemu/jobs/244168910#L5775
> 
> Quoting:
> 
> "
> Add watch /tmp/test-util-filemonitor-PH0B9Z (null)
> Watch ID 100000000
> Add watch /tmp/test-util-filemonitor-PH0B9Z one.txt
> Watch ID 100000001
> Add watch /tmp/test-util-filemonitor-PH0B9Z two.txt
> Watch ID 100000002
> Create /tmp/test-util-filemonitor-PH0B9Z/one.txt
> Event id=100000000 event=0 file=one.txt
> Queue event id 100000000 event 0 file one.txt
> Queue event id 100000001 event 0 file one.txt
> Event id=100000001 event=0 file=one.txt
> Create /tmp/test-util-filemonitor-PH0B9Z/two.txt
> Queue event id 100000000 event 0 file two.txt
> Queue event id 100000002 event 0 file two.txt
> Event id=100000000 event=0 file=two.txt
> Event id=100000002 event=0 file=two.txt
> Create /tmp/test-util-filemonitor-PH0B9Z/three.txt
> Queue event id 100000000 event 0 file three.txt
> Event id=100000000 event=0 file=three.txt
> Unlink /tmp/test-util-filemonitor-PH0B9Z/three.txt
> Queue event id 100000000 event 2 file three.txt
> Event id=100000000 event=2 file=three.txt
> Rename /tmp/test-util-filemonitor-PH0B9Z/one.txt ->
> /tmp/test-util-filemonitor-PH0B9Z/two.txt
> Queue event id 100000000 event 2 file one.txt
> Queue event id 100000001 event 2 file one.txt
> Queue event id 100000000 event 0 file two.txt
> Queue event id 100000002 event 0 file 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-PH0B9Z/two.txt
> Queue event id 100000000 event 1 file two.txt
> Queue event id 100000002 event 1 file two.txt
> Event id=100000000 event=1 file=two.txt
> Event id=100000002 event=1 file=two.txt
> Touch /tmp/test-util-filemonitor-PH0B9Z/two.txt
> Event id=100000000 event=3 file=two.txt
> Queue event id 100000000 event 3 file two.txt
> Queue event id 100000002 event 3 file two.txt
> Event id=100000002 event=3 file=two.txt
> Del watch /tmp/test-util-filemonitor-PH0B9Z 100000001
> Add watch /tmp/test-util-filemonitor-PH0B9Z one.txt
> Watch ID 100000003
> Create /tmp/test-util-filemonitor-PH0B9Z/one.txt
> Queue event id 100000000 event 0 file one.txt
> Event id=100000000 event=0 file=one.txt
> Queue event id 100000003 event 0 file one.txt
> Event id=100000003 event=0 file=one.txt
> Del watch /tmp/test-util-filemonitor-PH0B9Z 100000003
> Unlink /tmp/test-util-filemonitor-PH0B9Z/one.txt
> Queue event id 100000000 event 2 file one.txt
> Event id=100000000 event=2 file=one.txt
> Mkdir /tmp/test-util-filemonitor-PH0B9Z/fish
> Queue event id 100000000 event 0 file fish
> Event id=100000000 event=0 file=fish
> Add watch /tmp/test-util-filemonitor-PH0B9Z fish/
> Watch ID 200000000
> Add watch /tmp/test-util-filemonitor-PH0B9Z fish/one.txt
> Watch ID 200000001
> Create /tmp/test-util-filemonitor-PH0B9Z/fish/one.txt
> Queue event id 200000000 event 0 file one.txt
> Queue event id 200000001 event 0 file one.txt
> Event id=200000000 event=0 file=one.txt
> Event id=200000001 event=0 file=one.txt
> Del watch /tmp/test-util-filemonitor-PH0B9Z 200000001
> Rename /tmp/test-util-filemonitor-PH0B9Z/fish/one.txt ->
> /tmp/test-util-filemonitor-PH0B9Z/two.txt
> Queue event id 200000000 event 2 file one.txt
> Event id=200000000 event=2 file=one.txt
> Queue event id 100000000 event 0 file two.txt
> Event id=100000000 event=0 file=two.txt
> Event id=100000002 event=0 file=two.txt
> Queue event id 100000002 event 0 file two.txt
> Rmdir /tmp/test-util-filemonitor-PH0B9Z/fish
> Queue event id 100000000 event 2 file fish
> Event id=200000000 event=4 file=
> Missing event watch id 200000000 event 4 file
> **

This is really strange behaviour.  I've done some further test builds
on travis with various extra debug info & AFAICT, inotify is not
working correctly on the host - it is never emitting one of the events
that it should. Could be some wierd bug related to the filesystem
overlay setup used for the container env in travis I guess.

I'm not sure what todo here. I can't see an obvious trait that I can
use to identify a broken setup, in order to auto-skip the test. Might
just need to build without the inotify support somehow.

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 :|