From: Fam Zheng <fzheng@redhat.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/4] coroutine-lock: polymorphic CoQueue
Date: Wed, 17 Jan 2018 14:24:11 +0800 [thread overview]
Message-ID: <efbd1278-36e1-6f5b-773d-05a4244a8767@redhat.com> (raw)
In-Reply-To: <151616908700.575.7368076470257215397@5adcb62bf0d6>
On 01/17/2018 02:04 PM, no-reply@patchew.org wrote:
> BUILD min-glib
> Traceback (most recent call last):
> File "./tests/docker/docker.py", line 407, in <module>
> sys.exit(main())
> File "./tests/docker/docker.py", line 404, in main
> return args.cmdobj.run(args, argv)
> File "./tests/docker/docker.py", line 287, in run
> dkr = Docker()
> File "./tests/docker/docker.py", line 133, in __init__
> self._command = _guess_docker_command()
> File "./tests/docker/docker.py", line 58, in _guess_docker_command
> commands_txt)
> Exception: Cannot find working docker command. Tried:
> docker
> sudo -n docker
Patchew.org was misconfigured to run this docker tests on a host that
has no docker. Fixed now. Sorry for the noise.
Fam
next prev parent reply other threads:[~2018-01-17 6:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 14:23 [Qemu-devel] [PATCH v2 0/4] coroutine-lock: polymorphic CoQueue Paolo Bonzini
2018-01-16 14:23 ` [Qemu-devel] [PATCH 1/4] lockable: add QemuLockable Paolo Bonzini
2018-01-16 14:23 ` [Qemu-devel] [PATCH 2/4] coroutine-lock: convert CoQueue to use QemuLockable Paolo Bonzini
2018-01-16 14:23 ` [Qemu-devel] [PATCH 3/4] coroutine-lock: make qemu_co_enter_next thread-safe Paolo Bonzini
2018-01-16 14:23 ` [Qemu-devel] [PATCH 4/4] curl: convert to CoQueue Paolo Bonzini
2018-01-17 6:04 ` [Qemu-devel] [PATCH v2 0/4] coroutine-lock: polymorphic CoQueue no-reply
2018-01-17 6:24 ` Fam Zheng [this message]
2018-01-24 3:58 ` Fam Zheng
2018-01-24 9:00 ` Paolo Bonzini
2018-01-25 15:05 ` Fam Zheng
2018-01-25 15:12 ` Paolo Bonzini
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=efbd1278-36e1-6f5b-773d-05a4244a8767@redhat.com \
--to=fzheng@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).