All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org, berrange@redhat.com
Cc: alex.bennee@linaro.org, f4bug@amsat.org
Subject: Re: [Qemu-devel] [PATCH] docker: Fix PATH for ccache
Date: Wed, 18 Oct 2017 16:28:36 +0800	[thread overview]
Message-ID: <20171018082836.GD9443@lemon> (raw)
In-Reply-To: <150831409774.377.7665751901178175493@b58463cdfd5f>

On Wed, 10/18 01:08, no-reply@patchew.org wrote:
> Your branch is up-to-date with 'origin/test'.
> Submodule 'dtc' (git://git.qemu-project.org/dtc.git) registered for path 'dtc'
> Cloning into '/var/tmp/patchew-tester-tmp-jhpnlaz0/src/docker-src.2017-10-18-04.03.32.32287/qemu.tar.vroot/dtc'...
> fatal: unable to connect to git.qemu-project.org:
> git.qemu-project.org[0: 172.99.69.163]: errno=Connection timed out
> 
> fatal: clone of 'git://git.qemu-project.org/dtc.git' into submodule path '/var/tmp/patchew-tester-tmp-jhpnlaz0/src/docker-src.2017-10-18-04.03.32.32287/qemu.tar.vroot/dtc' failed
> Failed to clone 'dtc'. Retry scheduled
> Cloning into '/var/tmp/patchew-tester-tmp-jhpnlaz0/src/docker-src.2017-10-18-04.03.32.32287/qemu.tar.vroot/dtc'...
> fatal: unable to connect to git.qemu-project.org:
> git.qemu-project.org[0: 172.99.69.163]: errno=Connection timed out
> 
> fatal: clone of 'git://git.qemu-project.org/dtc.git' into submodule path '/var/tmp/patchew-tester-tmp-jhpnlaz0/src/docker-src.2017-10-18-04.03.32.32287/qemu.tar.vroot/dtc' failed
> Failed to clone 'dtc' a second time, aborting
> failed to init submodule dtc

So now patchew is less robust on network hiccups: a number of the same "git
submodule update --init" calls have succeeded above, so this is incidental. Any
idea how to improve that? Maybe if there is a checkout from $QEMU_SRC, clone/cp
from there instead of fetch from submodule remote?

Fam

  reply	other threads:[~2017-10-18  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  7:38 [Qemu-devel] [PATCH] docker: Fix PATH for ccache Fam Zheng
2017-10-18  8:08 ` no-reply
2017-10-18  8:28   ` Fam Zheng [this message]
2017-10-18  8:35     ` Daniel P. Berrange
2017-10-20 12:51       ` Daniel P. Berrange
2017-10-23  6:22         ` Fam Zheng
2017-10-23  8:37           ` Daniel P. Berrange
2017-10-23  8:02       ` Alistair Francis
2017-10-23  8:39         ` Daniel P. Berrange
2017-10-20  1:08 ` Fam Zheng

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=20171018082836.GD9443@lemon \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=f4bug@amsat.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.