zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Test hang in Y01
Date: Sun, 11 Jan 2009 09:46:33 -0800	[thread overview]
Message-ID: <090111094633.ZM12036@torch.brasslantern.com> (raw)
In-Reply-To: <20a807210901101034y3babd1deia8ac5fdfa6d3623c@mail.gmail.com>
In-Reply-To: <20090111054506.GA15893@primenet.com.au>

On Jan 10,  1:34pm, Vin Shelton wrote:
}
} ubuntu 8.4
} 
} uname -a reports:
} 
} Linux samwise 2.6.24-23-generic #1 SMP Thu Nov 27 18:44:42 UTC 2008
} i686 GNU/Linux

I have exactly the same on my work laptop (well, except for the host
name :-).

On Jan 11,  4:45pm, Geoff Wing wrote:
} Subject: Re: Test hang in Y01
}
} Does it for me too.  My nightly build/test cron job first picked it up
} 12 hours ago so it only due to something in the last day or so.  It hangs
} with continuous CPU use.

Odd.  Having never built zsh on that laptop, before, I did a complete
fresh CVS checkout from sourceforge, preconfig, configure, make, and
make test.  Everything passed.

I haven't tried building from the tarball.  Could there be something
wrong with the configure script that a new preconfig pass fixes up?


  parent reply	other threads:[~2009-01-11 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 15:44 Vin Shelton
2009-01-10 17:34 ` Bart Schaefer
2009-01-10 18:34   ` Vin Shelton
2009-01-10 21:48 ` Peter Stephenson
     [not found]   ` <20a807210901101719p58000b77sd0e37bf8b86469a9@mail.gmail.com>
2009-01-11  1:22     ` Vin Shelton
2009-01-11  5:45   ` Geoff Wing
2009-01-11 14:18     ` Peter Stephenson
2009-01-11 17:46     ` Bart Schaefer [this message]
2009-01-12  2:25       ` Vin Shelton
2009-01-12  3:19         ` Geoff Wing
2009-01-13 12:00         ` Peter Stephenson
2009-01-13 12:23           ` Peter Stephenson

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=090111094633.ZM12036@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).