automake
[Top][All Lists]
Advanced

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

Re: Testsuite fails


From: Tom Tromey
Subject: Re: Testsuite fails
Date: 18 Feb 2001 17:21:46 -0700

>>>>> "Pavel" == Pavel Roskin <address@hidden> writes:

Pavel> AC_CHECK_TOOL([STRIP],[strip])

Yes, I wasn't thinking.  I've removed this.

Ideally we'd have some way to tell autoconf, "if this package can be
cross-compiled, then check for a cross `strip' as well".  Maybe
there's an ugly way to do this.

Pavel> But what bothers me is the fact that very serious patches were
Pavel> committed without running the testsuite.

Yeah, that's my fault.  Sometimes I forget to do this.  That's bad.

cvs doesn't provide a way to force regression tests to be run on the
client system at commit time.  We could set it up to do this on the
server, but I'd prefer not to.

gcc uses a nice regression framework that sends email to people who
committed patches in the window where a new bug could have been
introduced.  That seems like overkill for automake.

Pavel> Some people are offended by this condition because it's
Pavel> _implied_. But now we have to think how to fix the testsuite
Pavel> that already fails.

I'm just directly removing the bug.

I imagine we'll have to radically revamp the test suite when we move
to using autoconf's tracing feature.  The current test suite is very
dumb and doesn't usually generate a correct configure.in.

Perhaps we could also rewrite the test suite to be faster somehow.
Maybe writing most of it in Perl would help.

Tom



reply via email to

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