GNU bug report logs - #14337
Unclear error messages when a test script is missing

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 14337 in the body.
You can then email your comments to 14337 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: Bruce Korb <bkorb <at> gnu.org>
To: GNU Automake mailing list <bug-automake <at> gnu.org>
Subject: Nothing to be done for `base.log'.
Date: Thu, 02 May 2013 16:58:15 -0700

It's taken me a few hours to unwind all this stuff, but the bottom line
seems to be that "make check" doesn't think it needs to do anything to
make the test log file.

Googling for:  "making test-suite.log: failed to create" log "nothing to be done for"
did not yield any useful hints.

Help, please?
===========================

$ make check
[.....]
>bash> make base.log
make[3]: Entering directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
make[3]: Nothing to be done for `base.log'.
make[3]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
>bash> am__dry=no
>bash> case $MAKEFLAGS in
>bash> for am__flg in '$MAKEFLAGS'
>bash> case $am__flg in
>bash> for am__flg in '$MAKEFLAGS'
>bash> case $am__flg in
>bash> for am__flg in '$MAKEFLAGS'
>bash> case $am__flg in
>bash> test no = yes
>bash> st=0
>bash> errmsg='fatal: making test-suite.log: failed to create'
>bash> for i in '$redo_bases'
>bash> test -f base.trs
>bash> echo 'fatal: making test-suite.log: failed to create base.trs'
fatal: making test-suite.log: failed to create base.trs
>bash> st=1
>bash> test -f base.log
>bash> echo 'fatal: making test-suite.log: failed to create base.log'
fatal: making test-suite.log: failed to create base.log
>bash> st=1
>bash> test 1 -eq 0
>bash> exit 1
make[2]: *** [test-suite.log] Error 1
make[2]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
make[1]: *** [check-TESTS] Error 2
make[1]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'

=====================  Makefile.am:

TESTS = base.test

TESTS_ENVIRONMENT = builddir=`pwd`

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

From: Bruce Korb <bkorb <at> gnu.org>
To: GNU Automake mailing list <bug-automake <at> gnu.org>
Subject: Re: Nothing to be done for `base.log'.
Date: Thu, 02 May 2013 17:07:11 -0700

On 05/02/13 16:58, Bruce Korb wrote:
> Help, please?

P.S. this only happens for srcdir != builddir builds
and the xtrace output below is triggered by manually inserting
"set -x" into the $(TEST_SUITE_LOG): rule.

> ===========================
>
> $ make check
> [.....]
>  >bash> make base.log
> make[3]: Entering directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
> make[3]: Nothing to be done for `base.log'.
> make[3]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
>  >bash> am__dry=no
>  >bash> case $MAKEFLAGS in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> test no = yes
>  >bash> st=0
>  >bash> errmsg='fatal: making test-suite.log: failed to create'
>  >bash> for i in '$redo_bases'
>  >bash> test -f base.trs
>  >bash> echo 'fatal: making test-suite.log: failed to create base.trs'
> fatal: making test-suite.log: failed to create base.trs
>  >bash> st=1
>  >bash> test -f base.log
>  >bash> echo 'fatal: making test-suite.log: failed to create base.log'
> fatal: making test-suite.log: failed to create base.log
>  >bash> st=1
>  >bash> test 1 -eq 0
>  >bash> exit 1
> make[2]: *** [test-suite.log] Error 1
> make[2]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
> make[1]: *** [check-TESTS] Error 2
> make[1]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
>
> =====================  Makefile.am:
>
> TESTS = base.test
>
> TESTS_ENVIRONMENT = builddir=`pwd`

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

From: Bruce Korb <bkorb <at> gnu.org>
To: 14337 <at> debbugs.gnu.org
Subject: Re: bug#14337: Acknowledgement (Nothing to be done for `base.log'.)
Date: Thu, 2 May 2013 20:48:24 -0400

Never mind.  I think the test driver code should say something
useful, however.  I neglected to notice that EXTRA_DIST should
include $(TESTS) or the tests won't get rolled into the tarball.

test -f $test_file || { echo cannot find $test_file ; exit 1 } 1>&2

On Thu, May 02, 2013 at 11:59:02PM +0000, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  bug-automake <at> gnu.org
> 
> If you wish to submit further information on this problem, please
> send it to 14337 <at> debbugs.gnu.org.
> 
> Please do not send mail to help-debbugs <at> gnu.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> -- 
> 14337: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14337
> GNU Bug Tracking System
> Contact help-debbugs <at> gnu.org with problems

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

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Bruce Korb <bkorb <at> gnu.org>
Cc: 14337 <at> debbugs.gnu.org
Subject: Re: bug#14337: Acknowledgement (Nothing to be done for `base.log'.)
Date: Fri, 03 May 2013 11:27:21 +0200

retitle 14337 Uncleer error messages when a test script is missing
severity 14337 minor
tags 14337 wontfix
thanks

On 05/03/2013 02:48 AM, Bruce Korb wrote:
>
> It's taken me a few hours to unwind all this stuff, but the bottom line
> seems to be that "make check" doesn't think it needs to do anything to
> make the test log file.
>
> Googling for:  "making test-suite.log: failed to create" log "nothing to
> be done for" did not yield any useful hints.
>
> Help, please?
>
> P.S. this only happens for srcdir != builddir builds
> and the xtrace output below is triggered by manually inserting
> "set -x" into the $(TEST_SUITE_LOG): rule.
>
> ===========================
>
> $ make check
> [.....]
>  >bash> make base.log
> make[3]: Entering directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
> make[3]: Nothing to be done for `base.log'.
> make[3]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
>  >bash> am__dry=no
>  >bash> case $MAKEFLAGS in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> for am__flg in '$MAKEFLAGS'
>  >bash> case $am__flg in
>  >bash> test no = yes
>  >bash> st=0
>  >bash> errmsg='fatal: making test-suite.log: failed to create'
>  >bash> for i in '$redo_bases'
>  >bash> test -f base.trs
>  >bash> echo 'fatal: making test-suite.log: failed to create base.trs'
> fatal: making test-suite.log: failed to create base.trs
>  >bash> st=1
>  >bash> test -f base.log
>  >bash> echo 'fatal: making test-suite.log: failed to create base.log'
> fatal: making test-suite.log: failed to create base.log
>  >bash> st=1
>  >bash> test 1 -eq 0
>  >bash> exit 1
> make[2]: *** [test-suite.log] Error 1
> make[2]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
> make[1]: *** [check-TESTS] Error 2
> make[1]: Leaving directory `/u/bkorb/ag/mypw/mypw-0.1-dev11/_build/tests'
>
> =====================  Makefile.am:
>
> TESTS = base.test
>
> TESTS_ENVIRONMENT = builddir=`pwd`
>
BTW, TESTS_ENVIRONMENT should be reserved for the user; you should
employ AM_TESTS_ENVIRONMENT to pass developer-defined environment
to the tests (the manual should speak about this).

> [LATER ...]
>
> Never mind.  I think the test driver code should say something
> useful, however.  I neglected to notice that EXTRA_DIST should
> include $(TESTS) or the tests won't get rolled into the tarball.
> 
> test -f $test_file || { echo cannot find $test_file ; exit 1 } 1>&2
>
That would prevent the user to use the contents of $(TESTS) as
parameters (with no real associated test script) for a single test
driver, a feature that has been supported until today (and Automake
itself once used to employ in its testsuite).

Not sure how actually useful that usage can be, but I see no
pressing reasons to change the status quo ATM.  Other people might
think differently though, and I'm ready to change my mind, so I
won't close this report for the moment being.

Regards,
  Stefano

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

From: Bruce Korb <bkorb <at> gnu.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 14337 <at> debbugs.gnu.org
Subject: Re: bug#14337: Acknowledgement (Nothing to be done for `base.log'.)
Date: Fri, 03 May 2013 06:37:28 -0700

On 05/03/13 02:27, Stefano Lattarini wrote:
> retitle 14337 Uncleer error messages when a test script is missing
> severity 14337 minor
> tags 14337 wontfix
> thanks

Meets _my_ expectation... :)

>> Never mind.  I think the test driver code should say something
>> useful, however.  I neglected to notice that EXTRA_DIST should
>> include $(TESTS) or the tests won't get rolled into the tarball.
>>
>> test -f $test_file || { echo cannot find $test_file ; exit 1 } 1>&2
>>
> That would prevent the user to use the contents of $(TESTS) as

If someone were to type "make dist TESTS=bogus", then they get what they deserve :)

> Not sure how actually useful that usage can be, but I see no
> pressing reasons to change the status quo ATM.  Other people might
> think differently though, and I'm ready to change my mind, so I
> won't close this report for the moment being.

I think clear error messages are always important, even if the
circumstances are rare.  If you know how to give the hapless user
(like me) better guidance, it's best to do so.  Messages about
"nothing to be done for base.log" are much more obscure than
"no rule to make target" or "cannot find base.test".

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

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Bruce Korb <bkorb <at> gnu.org>
Cc: 14337 <at> debbugs.gnu.org
Subject: Re: bug#14337: Acknowledgement (Nothing to be done for `base.log'.)
Date: Fri, 03 May 2013 15:41:16 +0200

On 05/03/2013 03:37 PM, Bruce Korb wrote:
> On 05/03/13 02:27, Stefano Lattarini wrote:
>> retitle 14337 Uncleer error messages when a test script is missing
>> severity 14337 minor
>> tags 14337 wontfix
>> thanks
> 
> Meets _my_ expectation... :)
> 
>>> Never mind.  I think the test driver code should say something
>>> useful, however.  I neglected to notice that EXTRA_DIST should
>>> include $(TESTS) or the tests won't get rolled into the tarball.
>>>
>>> test -f $test_file || { echo cannot find $test_file ; exit 1 } 1>&2
>>>
>> That would prevent the user to use the contents of $(TESTS) as
> 
> If someone were to type "make dist TESTS=bogus", then they get what they deserve :)
> 
>> Not sure how actually useful that usage can be, but I see no
>> pressing reasons to change the status quo ATM.  Other people might
>> think differently though, and I'm ready to change my mind, so I
>> won't close this report for the moment being.
> 
> I think clear error messages are always important, even if the
> circumstances are rare.  If you know how to give the hapless user
> (like me) better guidance, it's best to do so.  Messages about
> "nothing to be done for base.log" are much more obscure than
> "no rule to make target" or "cannot find base.test".
>
The point is that,in the scenario I explained, it *is* valid to have
entries in $(TESTS) that have no corresponding script on the
filesystem...

Regards,
  Stefano

Previous Next

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