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 (CLD) failing on i386
Date: Mon, 15 Feb 2010 11:04:26 -0700	[thread overview]
Message-ID: <20100215110426.6f32d051@redhat.com> (raw)
In-Reply-To: <4B790FF3.1070207@garzik.org>

On Mon, 15 Feb 2010 04:12:19 -0500
Jeff Garzik <jeff@garzik.org> wrote:

> x86-64 ok, i686 fail:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=1986987
> 
> x86-64 fail, i686 ok:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=1987025

I would try something like this for a start:

diff --git a/test/wait-for-listen.c b/test/wait-for-listen.c
index c1946c4..a5f1a52 100644
--- a/test/wait-for-listen.c
+++ b/test/wait-for-listen.c
@@ -133,9 +133,12 @@ int main()
  		 * Vote in DB4 replication takes about 12-13s.
 		 * In addition we may have retries when tabled polls for
 		 * Chunk daemons to come up. On busy boxes we may miss 20s.
+		 * So, 25s should be plenty, and we used that for a while,
+		 * but sometimes a daemon can fail establishing a session
+		 * with CLD and a retry takes a minute.
 		 */
-		if (time(NULL) >= start_time + 25) {
-			fprintf(stderr, "server is not up after 25 s\n");
+		if (time(NULL) >= start_time + 100) {
+			fprintf(stderr, "server is not up after 100 s\n");
 			exit(1);
 		}
 
@@ -159,6 +162,8 @@ int main()
 
 		sleep(2);
 	}
+
+	printf("tabled went up after %ld s\n", (long)time(NULL) - start_time);
 	return 0;
 }
 

-- Pete

      parent reply	other threads:[~2010-02-15 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15  9:12 tabled (CLD) failing on i386 Jeff Garzik
2010-02-15 14:46 ` Pete Zaitcev
2010-02-15 18:04 ` Pete Zaitcev [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=20100215110426.6f32d051@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.