[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AS_IF stress failure [was: interrupt causes parse error in configure
From: |
Ralf Wildenhues |
Subject: |
Re: AS_IF stress failure [was: interrupt causes parse error in configure script] |
Date: |
Tue, 19 Aug 2008 07:50:43 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Eric Blake wrote on Tue, Aug 19, 2008 at 06:22:40AM CEST:
> According to Ralf Wildenhues on 8/18/2008 5:09 PM:
> >
> > Ahh, thanks for this hint. It is indeed weird that I can trip the
> > failure of test 50 with './testsuite 59-60' or './testsuite 60' but not
> > with './testsuite 59-61'. So I guess this messes up some internal shell
> > data.
> >
> > Maybe we should relax that test?
>
> Sure. This scales AS_IF back by a factor of 10, then stresses
> m4_transform separately.
Thanks. Weirdly, the failure still happens. It even still happens if I
set 'limit' to 10. This is on GNU/Linux x86, m4 1.4.11, GNU bash,
version 3.2.39(1)-release.
Confused,
Ralf
- Re: interrupt causes parse error in configure script, (continued)
- Re: interrupt causes parse error in configure script, Eric Blake, 2008/08/19
- Re: interrupt causes parse error in configure script, Ralf Wildenhues, 2008/08/19
- AS_IF failure, Eric Blake, 2008/08/19
- Re: AS_IF failure, Ralf Wildenhues, 2008/08/20
- Re: AS_IF failure, Eric Blake, 2008/08/20
- Re: AS_IF failure, Ralf Wildenhues, 2008/08/21
- Re: interrupt causes parse error in configure script, Jim Meyering, 2008/08/19
- Re: interrupt causes parse error in configure script, Eric Blake, 2008/08/18
- Re: interrupt causes parse error in configure script, Ralf Wildenhues, 2008/08/18
- AS_IF stress failure [was: interrupt causes parse error in configure script], Eric Blake, 2008/08/19
- Re: AS_IF stress failure [was: interrupt causes parse error in configure script],
Ralf Wildenhues <=
Re: interrupt causes parse error in configure script, Eric Blake, 2008/08/18