All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: tabled RPM build fails before it succeeds
Date: Fri, 16 Apr 2010 14:19:32 -0600	[thread overview]
Message-ID: <20100416141932.53294d65@redhat.com> (raw)
In-Reply-To: <4BC89B88.7050304@garzik.org>

On Fri, 16 Apr 2010 13:16:56 -0400
Jeff Garzik <jeff@garzik.org> wrote:

> Build #1 (fails on x86_64):
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2119825

PASS: prep-db
chunkd[17774]: Waiting for CLD PortFile cld.port
cld[17773]: databases up
cld[17773]: Listening on port 34671
cld[17773]: initialized: nodebug
chunkd[17774]: Using CLD port 34671
chunkd[17775]: Listening on auto port 57521
tabled[17777]: Listening on port 36667
chunkd[17775]: New CLD session created, sid 4D81504D6021608C
chunkd[17775]: initialized
PASS: start-daemon
PASS: pid-exists
PASS: daemon-running
server is not up after 100 s

> Build #2 (fails on i686):
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2120174

Same.

I think it's time to figure it out. Going for a 100s delay
kinda sorta helped, but on second thought: why would any
packets get lost at all, on a loopback?

I'll try to see if I can reproduce this by overloading the
test system.

-- Pete

  reply	other threads:[~2010-04-16 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 17:16 tabled RPM build fails before it succeeds Jeff Garzik
2010-04-16 20:19 ` Pete Zaitcev [this message]
2010-05-13  0:49 ` Pete Zaitcev
2010-05-28 20:14 ` Pete Zaitcev

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=20100416141932.53294d65@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=hail-devel@vger.kernel.org \
    --cc=jeff@garzik.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.