From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, ptoscano@redhat.com
Cc: kwolf@redhat.com, fam@euphon.net, qemu-block@nongnu.org,
sw@weilnetz.de, rjones@redhat.com, mreitz@redhat.com,
alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH v9] ssh: switch from libssh2 to libssh
Date: Fri, 14 Jun 2019 17:12:03 +0200 [thread overview]
Message-ID: <80eff352-8e1f-4451-0cdf-c8808dc033e8@redhat.com> (raw)
In-Reply-To: <aee10f02-3ff8-222c-bfd4-833d595aa7e2@redhat.com>
On 6/13/19 8:18 PM, Paolo Bonzini wrote:
> On 13/06/19 19:15, Philippe Mathieu-Daudé wrote:
>>
>> On 6/13/19 6:24 PM, no-reply@patchew.org wrote:
>>> === 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/20190613132000.2146-1-ptoscano@redhat.com/testing.asan/?type=message.
>>
>>
>> === OUTPUT BEGIN ===
>> BUILD fedora
>> The command '/bin/sh -c dnf install -y $PACKAGES' returned a non-zero
>> code: 1
>> Traceback (most recent call last):
>> File "./tests/docker/docker.py", line 615, in <module>
>> sys.exit(main())
>> File "./tests/docker/docker.py", line 611, in main
>> return args.cmdobj.run(args, argv)
>> File "./tests/docker/docker.py", line 413, in run
>> extra_files_cksum=cksum)
>> File "./tests/docker/docker.py", line 280, in build_image
>> quiet=quiet)
>> File "./tests/docker/docker.py", line 207, in _do_check
>> return subprocess.check_call(self._command + cmd, **kwargs)
>> File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
>> raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['sudo', '-n', 'docker',
>> 'build', '-t', 'qemu:fedora', '-f',
>> '/tmp/docker_buildN2FMKc/tmpz_9Up_.docker', '/tmp/docker_buildN2FMKc']'
>> returned non-zero exit status 1
>> make: *** [docker-image-fedora] Error 1
>>
>> real 3m54.376s
>>
>> Not sure this is a network issue or something else, should we rebuild
>> docker images with V=1 on patchew?
>>
>
> I restarted the job with V=1.
Thanks!
Patchew did not send update, which means no failure.
Hopefully it updated the same url with the full log.
Indeed the job is successful:
real 30m39.367s
user 0m8.061s
sys 0m5.880s
=== OUTPUT END ===
Test command exited with code: 0
next prev parent reply other threads:[~2019-06-14 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 13:20 [Qemu-devel] [PATCH v9] ssh: switch from libssh2 to libssh Pino Toscano
2019-06-13 13:50 ` Philippe Mathieu-Daudé
2019-06-13 16:24 ` no-reply
2019-06-13 17:15 ` Philippe Mathieu-Daudé
2019-06-13 18:18 ` Paolo Bonzini
2019-06-14 15:12 ` Philippe Mathieu-Daudé [this message]
2019-06-13 19:31 ` Max Reitz
2019-06-13 20:06 ` Eric Blake
2019-06-14 14:26 ` Philippe Mathieu-Daudé
2019-06-14 14:30 ` Max Reitz
2019-06-14 15:09 ` Philippe Mathieu-Daudé
2019-06-14 14:29 ` Pino Toscano
2019-06-14 14:34 ` Max Reitz
2019-06-14 15:15 ` Philippe Mathieu-Daudé
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=80eff352-8e1f-4451-0cdf-c8808dc033e8@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ptoscano@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=sw@weilnetz.de \
/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).