qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v5] tests/qtest: netdev: test stream and dgram backends
Date: Tue, 17 Jan 2023 12:44:31 +0100	[thread overview]
Message-ID: <819db04a-0b00-96e2-65f2-57db1e244fe3@redhat.com> (raw)
In-Reply-To: <4b12b445-f8e3-8003-60a2-a5aec0a12026@linaro.org>

On 1/17/23 12:32, Philippe Mathieu-Daudé wrote:
> On 17/1/23 12:03, Laurent Vivier wrote:
>> On 1/17/23 11:00, Thomas Huth wrote:
>>> On 16/01/2023 09.40, Thomas Huth wrote:
>>>> On 16/01/2023 09.29, Laurent Vivier wrote:
>>>>> ping
>>>>>
>>>>> On 1/5/23 10:37, 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>
>>>>
>>>> I'll queue it for my next pull request (unless someone else wants to take this first)
>>>
>>> Sorry, but I have to unqueue it again. I'm still seeing failures
>>> in the Windows Cirrus-CI:
>>>
>>>   https://cirrus-ci.com/task/5867407370092544
>>>
>>> For example:
>>>
>>> 218/556 qemu:qtest+qtest-aarch64 / qtest-aarch64/netdev-socket ERROR           0.02s   
>>> exit status 3
>>> ------------------------------------- 8< -------------------------------------
>>> stderr:
>>> socket_check_protocol_support() failed
>>>
>>> (C:/Users/ContainerAdministrator/AppData/Local/Temp/cirrus-ci-build/build/tests/qtest/netdev-socket.exe:3300): GLib-CRITICAL **: 09:08:00.984: g_utf8_to_utf16: assertion 'str != NULL' failed
>>>
>>> (test program exited with status code 3)
>>>
>>> No clue where this comes from, though, I don't see a call
>>> to g_utf8_to_utf16() in your code?
>>
>> OK, there is an error in the log:
>>
>> socket_check_protocol_support() failed
>>
>> So tmpdir is NULL and we try an g_rmdir(tmpdir)
> 
> "In case of errors, NULL is returned and error will be set."
> 
> I don't see the ""Can't create temporary directory" string in
> Thomas' failing job.
> 
> In such case, are the g_strconcat(tmpdir) calls returning "\0"?
> 
> 

I'm going to use g_error() on socket_check_protocol_support() failure to exit. Without the 
problem with g_utf8_to_utf16() I would not know the socket_init() function was needed.

Thanks,
Laurent



      reply	other threads:[~2023-01-17 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  9:37 [PATCH v5] tests/qtest: netdev: test stream and dgram backends Laurent Vivier
2023-01-16  8:29 ` Laurent Vivier
2023-01-16  8:40   ` Thomas Huth
2023-01-17 10:00     ` Thomas Huth
2023-01-17 10:53       ` Laurent Vivier
2023-01-17 11:20         ` Thomas Huth
2023-01-17 11:03       ` Laurent Vivier
2023-01-17 11:32         ` Philippe Mathieu-Daudé
2023-01-17 11:44           ` 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=819db04a-0b00-96e2-65f2-57db1e244fe3@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).