From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>,
qemu-devel@nongnu.org, farosas@suse.de, philmd@redhat.com,
bcain@quicinc.com, quic_mliebel@quicinc.com
Subject: Re: test_migration.py not working with netcat-traditional
Date: Wed, 19 Mar 2025 10:37:20 +0100 [thread overview]
Message-ID: <6220a804-0442-4270-8326-b4573d68c9db@redhat.com> (raw)
In-Reply-To: <Z9qGwgEvRHJQt1rJ@redhat.com>
On 19/03/2025 09.57, Daniel P. Berrangé wrote:
> On Wed, Mar 19, 2025 at 08:49:53AM +0100, Thomas Huth wrote:
>> On 18/03/2025 22.13, Matheus Tavares Bernardino wrote:
>>> Hi,
>>>
>>> tests/functional/test_migration.py says "The test works for both
>>> netcat-traditional and netcat-openbsd packages." But when I run it for
>>> qemu-system-aarch64 on an Ubuntu 22.04 container with netcat-traditional
>>> installed, I get the following error:
>>>
>>> TAP version 13
>>> Traceback (most recent call last):
>>> File "/pwd/tests/functional/test_migration.py", line 97, in test_migration_with_exec
>>> self.do_migrate(dest_uri, src_uri)
>>> File "/pwd/tests/functional/test_migration.py", line 72, in do_migrate
>>> self.assert_migration(source_vm, dest_vm)
>>> File "/pwd/tests/functional/test_migration.py", line 40, in assert_migration
>>> self.assertEqual(src_vm.cmd('query-migrate')['status'], 'completed')
>>> AssertionError: 'failed' != 'completed'
>>> - failed
>>> + completed
>>>
>>> not ok 1 test_migration.MigrationTest.test_migration_with_exec
>>> ok 2 test_migration.MigrationTest.test_migration_with_tcp_localhost
>>> ok 3 test_migration.MigrationTest.test_migration_with_unix
>>> 1..3
>>>
>>> With netcat-openbsd (the default), it runs fine. Perhaps the test is no
>>> longer compatible with netcat-traditional?
>>>
>>> QEMU was configured and built with:
>>> ../configure --without-default-features --target-list=aarch64-softmmu
>>
>> For me it works with both flavors of "nc", the ncat and the netcat one...
>> but I'm also running on Fedora.
>
> There are three flavour os 'nc' - the traditional netcat, openbsd netcat
> and nmap netcat.
Oh, there is even a third one? ... TIL, I wasn't aware of that yet.
> IMHO rather than debug differences in these, we'd be better off just
> rewriting the test to use socat so we have 1 single impl to think about
> instead of 3.
That's a good idea. Alternatively we could also limit the test to "ncat",
AFAICT that name is not used by the other twos, is it?
Thomas
prev parent reply other threads:[~2025-03-19 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 21:13 [PATCH] Add files: a Matheus Tavares Bernardino
2025-03-18 21:17 ` test_migration.py not working with netcat-traditional Matheus Tavares Bernardino
2025-03-19 7:49 ` Thomas Huth
2025-03-19 8:57 ` Daniel P. Berrangé
2025-03-19 9:37 ` Thomas Huth [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=6220a804-0442-4270-8326-b4573d68c9db@redhat.com \
--to=thuth@redhat.com \
--cc=bcain@quicinc.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=quic_mliebel@quicinc.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).