On 02/22/2012 09:22 PM, Bob Friesenhahn wrote:
> On Wed, 22 Feb 2012, Stefano Lattarini wrote:
>>>
>> I don't understand how that patch could actually work ... If there are
>> too many tests in $(TESTS), there will be too many logs in $(TEST_LOGS),
>> and since the recipe for $(TEST_SUITE_LOG) con
On Wed, 22 Feb 2012, Stefano Lattarini wrote:
I don't understand how that patch could actually work ... If there are
too many tests in $(TESTS), there will be too many logs in $(TEST_LOGS),
and since the recipe for $(TEST_SUITE_LOG) contents the expansion of
$(TEST_LOGS), the command line leng
Hi Peter.
On 02/22/2012 08:31 PM, p...@lysator.liu.se wrote:
>> On 02/21/2012 09:56 PM, Stefano Lattarini wrote:
>>> With this change, our testsuite now uses 'configure.ac' as the
>>> name for the typical autoconf input, instead of the obsolescent
>>> 'configure.in' (which has been deprecated for
On 02/22/2012 03:57 PM, Bob Friesenhahn wrote:
> On Wed, 22 Feb 2012, Stefano Lattarini wrote:
>
>> Hi Bob, sorry for the delay.
>>
>> On 02/19/2012 07:55 PM, Bob Friesenhahn wrote:
>>> I am again bit by automake not being able run the test suite on systems
>>> with bounded command line length. U
> On 02/21/2012 09:56 PM, Stefano Lattarini wrote:
>> With this change, our testsuite now uses 'configure.ac' as the
>> name for the typical autoconf input, instead of the obsolescent
>> 'configure.in' (which has been deprecated for several years, at
>> least since autoconf 2.50).
>>
>> The test ca
On Wed, 22 Feb 2012, Stefano Lattarini wrote:
Hi Bob, sorry for the delay.
On 02/19/2012 07:55 PM, Bob Friesenhahn wrote:
I am again bit by automake not being able run the test suite on systems
with bounded command line length. Up to automake 1.11.2 I was able to
apply a patch by Ralf Wildenh
According to recent testing by Eric Blake, it seems that all
non-museum rm(1) implementations don't complain if called without
file operands, *if* the '-f' option is used. This behaviour will
likely be mandated by future versions of the POSIX standard as
well.
We'd like to start assuming this rm(
* tests/tap-setup.sh: Pass also '-f' option to 'cp' invocations,
so that files that have already been copied in without write
permissions will still be overwritten where needed, instead of
causing a spurious testsuite failure. Issue seen when the
testsuite is run under "distcheck".
* tests/defs (g
* tests/parallel-tests-many.test: Adjust grepping of "make check"
and "make recheck" output to match the new format of the testsuite
summary. Remove redundant 'set -e' call since we are at it.
---
tests/parallel-tests-many.test |8
1 files changed, 4 insertions(+), 4 deletions(-)
di
Hi Bob, sorry for the delay.
On 02/19/2012 07:55 PM, Bob Friesenhahn wrote:
> I am again bit by automake not being able run the test suite on systems
> with bounded command line length. Up to automake 1.11.2 I was able to
> apply a patch by Ralf Wildenhues.
>
Which patch are you referring to exac
On 02/21/2012 09:56 PM, Stefano Lattarini wrote:
> With this change, our testsuite now uses 'configure.ac' as the
> name for the typical autoconf input, instead of the obsolescent
> 'configure.in' (which has been deprecated for several years, at
> least since autoconf 2.50).
>
> The test cases cha
11 matches
Mail list logo
