[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: acloca20 test intermittent failure

From: Stepan Kasal
Subject: Re: acloca20 test intermittent failure
Date: Wed, 25 Oct 2006 12:23:42 +0200
User-agent: Mutt/


On Wed, Oct 25, 2006 at 07:51:35AM +1000, Greg Schafer wrote:
> On Tue, Oct 24, 2006 at 06:04:30PM +0200, Stepan Kasal wrote:
> > The fix is obvious: `autom4te' should always create the output file,
> > if --force was given.  Patch attached.
> > I committed it to the Autoconf CVS.
> Indeed it does! No failures at all now :-)

thank you very much for verifying this!

And thanks to Ralf for reminding me that each bugfix should be
accompanied by a test case.

To reproduce the bug, we need an output file which has modified date
``now'' or newer.  I can see two ways to try to reproduce this:

1) Call a minimum autom4te configuration, so that the chance that it
finishes in the same second is great.  With the buggy autom4te, the
probability that the test will fail is high, even on my slow box.
But this does not work with sub-second time stamps.

2) Use `touch --date' to set time stamp of the output file to the
future.  Requires GNU touch, an perhaps even GNU libc.

The patch uses combination of the two techniques.

Does the patch look OK?


Attachment: autoconf-20061025-check-force.patch
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]