From: John Snow <jsnow@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: Failing QEMU iotests
Date: Wed, 17 Nov 2021 14:59:18 -0500 [thread overview]
Message-ID: <CAFn=p-YSYuQeMhiipjSFmWEuCTS3hbAwHg0SK87jfx7qLZoXdg@mail.gmail.com> (raw)
In-Reply-To: <f9015aa2-e513-b760-6579-5457fff0e969@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3662 bytes --]
On Wed, Nov 17, 2021 at 2:45 PM Thomas Huth <thuth@redhat.com> wrote:
> On 17/11/2021 19.13, John Snow wrote:
> >
> >
> > On Wed, Nov 17, 2021 at 5:07 AM Thomas Huth <thuth@redhat.com
> > <mailto:thuth@redhat.com>> wrote:
> >
> >
> > Hi!
> >
> > I think it has been working fine for me a couple of weeks ago,
> > but when I now run:
> >
> > make check SPEED=slow
> >
> > I'm getting a couple of failing iotests... not sure whether
> > these are known issues already, so I thought I'd summarize them
> > here:
> >
> > *** First one is 045 in raw mode: ***
> >
> > TEST iotest-raw: 045 [fail]
> > QEMU --
> >
> "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-system-x86_64"
> > -nodefaults -display none -accel qtest
> > QEMU_IMG --
> > "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-img"
> > QEMU_IO --
> > "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-io" --cache
> > writeback --aio threads -f raw
> > QEMU_NBD --
> > "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-nbd"
> > IMGFMT -- raw
> > IMGPROTO -- file
> > PLATFORM -- Linux/x86_64 thuth 4.18.0-305.19.1.el8_4.x86_64
> > TEST_DIR --
> /home/thuth/tmp/qemu-build/tests/qemu-iotests/scratch
> > SOCK_DIR -- /tmp/tmphlexdrlt
> > GDB_OPTIONS --
> > VALGRIND_QEMU --
> > PRINT_QEMU_OUTPUT --
> >
> > --- /home/thuth/devel/qemu/tests/qemu-iotests/045.out
> > +++ 045.out.bad
> > @@ -1,5 +1,77 @@
> > -...........
> > +......EE.EE <http://EE.EE>
> >
> +======================================================================
> > +ERROR: test_add_fd (__main__.TestSCMFd)
> >
> +----------------------------------------------------------------------
> > +Traceback (most recent call last):
> > + File "/home/thuth/devel/qemu/tests/qemu-iotests/045", line 148, in
> > test_add_fd
> > + self._send_fd_by_SCM()
> > + File "/home/thuth/devel/qemu/tests/qemu-iotests/045", line 144, in
> > _send_fd_by_SCM
> > + ret = self.vm.send_fd_scm(file_path=image0)
> > + File "/home/thuth/devel/qemu/python/qemu/machine/machine.py", line
> > 229, in send_fd_scm
> > + self._qmp.send_fd_scm(fd)
> > + File "/home/thuth/devel/qemu/python/qemu/aqmp/legacy.py", line
> 138,
> > in send_fd_scm
> > + self._aqmp.send_fd_scm(fd)
> > + File "/home/thuth/devel/qemu/python/qemu/aqmp/protocol.py", line
> 149,
> > in _wrapper
> > + return func(proto, *args, **kwargs)
> > + File "/home/thuth/devel/qemu/python/qemu/aqmp/qmp_client.py", line
> > 644, in send_fd_scm
> > + sock = sock._sock # pylint: disable=protected-access
> > +AttributeError: 'socket' object has no attribute '_sock'
> >
> >
> > Well, that's not good.
> >
> > Can you tell me some details about what system produced this failure?
> > The python version used to run the test would be good, as well as distro
> > release, kernel version, etc.
> >
> > If you can reproduce it, I might want to give you a test branch of the
> > python code to produce some extra debugging information to help me
> > understand what's gone wrong here. Get in touch on IRC when you have
> some
> > spare time if you'd like to interactively debug it.
>
> As you likely saw in Hanna's mail a little bit later, the problem was the
> old version of pylint. I did still have version 2.2 installed - after
> upgrading, the problem went away.
>
>
upgrading pylint made *this* problem in *045* go away and not just the
failure in *297*, are you positive?
[-- Attachment #2: Type: text/html, Size: 5108 bytes --]
next prev parent reply other threads:[~2021-11-17 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:07 Failing QEMU iotests Thomas Huth
2021-11-17 10:59 ` Hanna Reitz
2021-11-17 12:50 ` Thomas Huth
2021-11-17 14:46 ` Daniel P. Berrangé
2021-11-17 18:06 ` John Snow
2021-11-17 18:13 ` John Snow
2021-11-17 19:45 ` Thomas Huth
2021-11-17 19:59 ` John Snow [this message]
2021-11-17 21:32 ` Thomas Huth
2021-11-17 22:25 ` John Snow
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='CAFn=p-YSYuQeMhiipjSFmWEuCTS3hbAwHg0SK87jfx7qLZoXdg@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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).