Pádraig Brady wrote:
> On 12/22/2011 11:44 AM, Jim Meyering wrote:
>> FYI, after updating to the latest tests/init.sh, I noticed new
>> failures in vc-dwim's "make check". Tracked it down to this:
>>
>
>> diff --git a/tests/init.sh b/tests/init.sh
>> index 19c0cf4..458a448 100644
>> --- a/tests/i
14f2081d659da0cc3a76536 Mon Sep 17 00:00:00 2001
>> From: Jim Meyering
>> Date: Thu, 22 Dec 2011 12:42:32 +0100
>> Subject: [PATCH] init.sh: avoid unwarranted test failure when using "set -x"
>>
>> * tests/init.sh (compare): Ignore nonzero exit from compare_dev_
On 12/22/2011 11:44 AM, Jim Meyering wrote:
> FYI, after updating to the latest tests/init.sh, I noticed new
> failures in vc-dwim's "make check". Tracked it down to this:
>
> diff --git a/tests/init.sh b/tests/init.sh
> index 19c0cf4..458a448 100644
> --- a/tests/init.sh
> +++ b/tests/init.sh
>
Jim Meyering
> Date: Thu, 22 Dec 2011 12:42:32 +0100
> Subject: [PATCH] init.sh: avoid unwarranted test failure when using "set -x"
>
> * tests/init.sh (compare): Ignore nonzero exit from compare_dev_null_.
> Otherwise, in a test script that uses "set -x" (like m
CH] init.sh: avoid unwarranted test failure when using "set -x"
* tests/init.sh (compare): Ignore nonzero exit from compare_dev_null_.
Otherwise, in a test script that uses "set -x" (like many in vc-dwim)
a use like "compare exp out" would get evoke an unconditional failure.