From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [tabled patch 1/1] Stagger the start-daemon
Date: Thu, 01 Jul 2010 16:23:49 -0400 [thread overview]
Message-ID: <4C2CF955.80006@garzik.org> (raw)
In-Reply-To: <20100630084948.1f68e423@lembas.zaitcev.lan>
On 06/30/2010 10:49 AM, Pete Zaitcev wrote:
> My rule of thumb is that magic delays are evil or stupid, so I worked on
> eliminating them from our scripts. However, in this case it's just not
> worth it, because the result is that we have to wait way more than 100s
> for several cycles of CLD timeouts to complete, not just one, before we
> declare a failure. With this patch, all builds completed that I submitted
> to Fedora build system.
>
> Signed-off-by: Pete Zaitcev<zaitcev@redhat.com>
>
> ---
> test/start-daemon | 4 ++++
> test/wait-for-listen.c | 7 ++-----
> 2 files changed, 6 insertions(+), 5 deletions(-)
applied
prev parent reply other threads:[~2010-07-01 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 14:49 [tabled patch 1/1] Stagger the start-daemon Pete Zaitcev
2010-07-01 20:23 ` Jeff Garzik [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=4C2CF955.80006@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@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 read-only IMAP folder(s) and NNTP newsgroup(s).