Thomas Huth <th...@redhat.com> writes:

> On 29/04/2019 05.47, no-re...@patchew.org wrote:
>> Patchew URL: 
>> https://patchew.org/QEMU/20190428155451.15653-1-th...@redhat.com/
>>
>> This series failed the asan build test. Please find the testing commands and
>> their output below. If you have Docker installed, you can probably reproduce 
>> it
>> locally.
>>
>> === TEST SCRIPT BEGIN ===
>> #!/bin/bash
>> time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
>> === TEST SCRIPT END ===
>>
>> The full log is available at
>> http://patchew.org/logs/20190428155451.15653-1-th...@redhat.com/testing.asan/?type=message.
>
> The asan test failed since it could not check out the repository ...
> a networking problem?
>
> Anyway, looks like there was a real bug here:
>
>  
> https://patchew.org/logs/20190428155451.15653-1-th...@redhat.com/testing.docker-clang@ubuntu/?type=message
>
> Test 162 failed with:
>
> 162         - output mismatch (see 162.out.bad)
> --- /tmp/qemu-test/src/tests/qemu-iotests/162.out     2019-04-28 
> 16:09:31.000000000 +0000
> +++ /tmp/qemu-test/build/tests/qemu-iotests/162.out.bad       2019-04-28 
> 16:24:21.669646149 +0000
> @@ -6,7 +6,9 @@
>  image: nbd+unix://?socket=42
>
>  === SSH ===
> +qemu-img: warning: GLib: getpwuid_r(): failed due to unknown user id (1003)
>  qemu-img: Could not open 'json:{"driver": "ssh", "host": "localhost", 
> "port": "0", "path": "/foo"}': Failed to connect socket: Connection refused
> +qemu-img: warning: GLib: getpwuid_r(): failed due to unknown user id (1003)
>  qemu-img: Could not open 'driver=ssh,host=localhost,port=0,path=/foo': 
> Failed to connect socket: Connection refused
>  qemu-img: Could not open 'json:{"driver": "ssh", "host": "localhost", 
> "port": 0.42, "path": "/foo"}': Parameter 'port' expects a number
>  qemu-img: Could not open 'driver=ssh,host=localhost,port=0.42,path=/foo': 
> Parameter 'port' expects a number
>
> ... I think I'll remove 162 from the "auto" group to avoid this.

Should I wait for a v3 then?

--
Alex Bennée

Reply via email to