libtool-patches
[Top][All Lists]
Advanced

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

Re: [PATCH 1/6] Require Automake 1.11.1 for Libtool, enable color-tests.


From: Gary V. Vaughan
Subject: Re: [PATCH 1/6] Require Automake 1.11.1 for Libtool, enable color-tests.
Date: Sun, 22 Aug 2010 22:41:52 +0700

On 22 Aug 2010, at 22:30, Ralf Wildenhues wrote:
> * Gary V. Vaughan wrote on Sun, Aug 22, 2010 at 05:24:05PM CEST:
>> On 22 Aug 2010, at 22:09, Ralf Wildenhues wrote:
> 
>>> # consider using shallow clones here, to ease server load.
>>> git clone git://git.sv.gnu.org/autoconf.git
>>> git clone git://git.sv.gnu.org/automake.git
>> 
>> We could pull the already bootstrapped release tarballs from an
>> ftp.gnu.org mirror here instead.
> 
> Sure.
> 
>>> git clone git://git.sv.gnu.org/libtool.git
>> 
>> Of course, that doesn't test the patch series you haven't
>> pushed yet...
> 
> Just add 'git checkout origin/parallel-tests'.

I meant that if I want to check that my next round of m4sh patches
don't break with older Autotools before I push, this script doesn't
help, since it wants a fresh libtool checkout.  The script would
be more useful if it can be run inside a dirty working directory.

>> And running it as an Autotest inside the existing tree would
>> get us better coverage, and obviate the need for a separate
>> checkout of the libtool tree entirely.
> 
> Sure.  But look at the existing sort-of-recursive tests.  They are
> tricky.  I am waiting for the day where we add infinite recursion in
> some corner case and have developers complain.

Actually, I've not looked at the details of those recursive tests,
so I must admit that I don't know how tricky they are.  I just
assumed that we could reuse that pattern here.

> The net is abundant now, I think such test helper scripts are a real
> easy way to get more coverage, but I don't think it is necessary to
> run them as part of each testsuite run, because they are very expensive.

A very good point.  Maybe we should add a 'maintainer-test' target or
similar, which executes this and other expensive test-helper scripts
in addition to the regular testsuite(s). And it's also worth considering
migrating our other recursive tests to helper scripts too in that case.

>>> # Now, mail all output and logs to the autobuild site ...
>>> # ... and consider cleaning up afterwards.
>> 
>> The last bit of the script is missing ;)
> 
> TBD when I have all the autobuild setup figured out and all.

Kidding!! LOL

Cheers,
-- 
Gary V. Vaughan (address@hidden)

Attachment: PGP.sig
Description: This is a digitally signed message part


reply via email to

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