GNU bug report logs - #23099
typos automake.texi

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23099 in the body.
You can then email your comments to 23099 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dilyan Palauzov <dilyan.palauzov <at> aegee.org>
To: bug-automake <at> gnu.org
Subject: typos automake.texi
Date: Wed, 23 Mar 2016 22:21:59 +0100

Hello,

please update in doc/automake.texi, line 9132:

It's important to note that ... the AM_TESTS_ENVIRONMENT and 
TESTS_ENVIRONMENT variables cannot BE USE to define a custom test runner;

to

It's important to note that ... the AM_TESTS_ENVIRONMENT and 
TESTS_ENVIRONMENT variables cannot be used to define a custom test runner;

AND

in node "Scripts-based Testsuites" replace:

for example, in tests using TAP, there is NOT WAY to disable hard 
errors, and the ‘DISABLE_HARD_ERRORS’ variable has no effect on them

with

for example, in tests using TAP, there is no way to disable hard errors, 
and the ‘DISABLE_HARD_ERRORS’ variable has no effect on them

Greetings
  Dilian

Message #8 received at 23099 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Lirzin <mthl <at> gnu.org>
To: Dilyan Palauzov <dilyan.palauzov <at> aegee.org>
Cc: 23099 <at> debbugs.gnu.org
Subject: Re: bug#23099: typos automake.texi
Date: Sun, 16 Jul 2017 01:07:58 +0200

Hello,

Dilyan Palauzov <dilyan.palauzov <at> aegee.org> writes:

> please update in doc/automake.texi, line 9132:
>
> It's important to note that ... the AM_TESTS_ENVIRONMENT and
> TESTS_ENVIRONMENT variables cannot BE USE to define a custom test
> runner;
>
> to
>
> It's important to note that ... the AM_TESTS_ENVIRONMENT and
> TESTS_ENVIRONMENT variables cannot be used to define a custom test
> runner;
>
> AND
>
> in node "Scripts-based Testsuites" replace:
>
> for example, in tests using TAP, there is NOT WAY to disable hard
> errors, and the ‘DISABLE_HARD_ERRORS’ variable has no effect on them
>
> with
>
> for example, in tests using TAP, there is no way to disable hard
> errors, and the ‘DISABLE_HARD_ERRORS’ variable has no effect on them

This has been fixed in commit 5864fb5564a8607bf9a1fd90e12259127d8c629b.

Thanks for the report.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.