From: Laurent Vivier <lvivier@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Jason Wang" <jasowang@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v6] tests/qtest: netdev: test stream and dgram backends
Date: Tue, 17 Jan 2023 18:24:45 +0100 [thread overview]
Message-ID: <a7b29b75-2d7d-8146-c590-6d2dd7602476@redhat.com> (raw)
In-Reply-To: <5b67045b-d8d7-14ef-21ff-3fcadff9e5bf@redhat.com>
On 1/17/23 17:45, Thomas Huth wrote:
> On 17/01/2023 14.15, Laurent Vivier wrote:
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>> Acked-by: Thomas Huth <thuth@redhat.com>
>> ---
>>
>> Notes:
>> v6:
>> - call socket_init() otherwise socket_check_protocol_support() fails
>> - if socket_check_protocol_support() fails then calls g_abort() to
>> report a problem.
>
> Last problem fixed, next one occurring:
Thank you Thomas
>
> 218/556 qemu:qtest+qtest-aarch64 / qtest-aarch64/netdev-socket
> ERROR 0.77s exit status 3
> ------------------------------------- 8< -------------------------------------
> stderr:
> qemu-system-aarch64: -netdev
> dgram,id=st0,remote.type=inet,remote.host=230.0.0.1,remote.port=1234: can't bind
> ip=230.0.0.1 to socket: Unknown error
> Broken pipe
It seems to be the test_dgram_mcast() test.
Perhaps windows doesn't support multicast datagram?
> ../tests/qtest/libqtest.c:195: kill_qemu() tried to terminate QEMU process but encountered
> exit status 1 (expected 0)
> TAP parsing error: Too few tests run (expected 6, got 4)
> (test program exited with status code 3)
> ------------------------------------------------------------------------------
>
> See: https://cirrus-ci.com/task/6491942456918016
I'm sorry I've not been able to find the cirrus-ci option in github, so I didn't test.
>
> ... maybe it would be better to simply limit the test to
> CONFIG_POSIX in the meson.build file?
I agree but first I'd like to only disable the multicast test. If it fails, I'll limit the
test to POSIX.
I'm sorry for the inconvenient.
Thanks,
Laurent
prev parent reply other threads:[~2023-01-17 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 13:15 [PATCH v6] tests/qtest: netdev: test stream and dgram backends Laurent Vivier
2023-01-17 16:45 ` Thomas Huth
2023-01-17 17:24 ` Laurent Vivier [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=a7b29b75-2d7d-8146-c590-6d2dd7602476@redhat.com \
--to=lvivier@redhat.com \
--cc=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.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).