[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AT_ARG_OPTION_ARG test failure
From: |
Ralf Wildenhues |
Subject: |
AT_ARG_OPTION_ARG test failure |
Date: |
Tue, 20 Jul 2010 07:09:03 +0200 |
User-agent: |
Mutt/1.5.20 (2010-04-22) |
I don't get it, esp. I don't get why I haven't seen this anywhere
before. This is with bash 3.2.39 on Debian GNU/Linux x86. Can anyone
confirm this failure? Otherwise I guess I should go looking for weird
stuff in my setup.
Anyway, rerunning
./micro-suite -x 1 FROB=default FROB_ARG=
in the test directory does not show any failures.
Cheers,
Ralf
# -*- compilation -*-
192. autotest.at:1184: testing AT_ARG_OPTION_ARG ...
../../autoconf/tests/autotest.at:1184: cat >./atconfig <<EOF
at_testdir=.
abs_builddir='`pwd`'
at_srcdir=.
abs_srcdir='`pwd`'
at_top_srcdir=.
abs_top_srcdir='`pwd`'
at_top_build_prefix=
abs_top_builddir='`pwd`'
EOF
../../autoconf/tests/autotest.at:1184: autom4te --language=autotest -o
micro-suite micro-suite.at
../../autoconf/tests/autotest.at:1184: $CONFIG_SHELL ./micro-suite --help
stdout:
Usage: ./micro-suite [OPTION]... [VARIABLE=VALUE]... [TESTS]
Run all the tests, or the selected TESTS, given by numeric ranges, and
save a detailed log file. Upon failure, create debugging scripts.
Do not change environment variables directly. Instead, set them via
command line arguments. Set `AUTOTEST_PATH' to select the executables
to exercise. Each relative directory is expanded as build and source
directories relative to the top level of this distribution.
E.g., from within the build directory /tmp/foo-1.0, invoking this:
$ ./micro-suite AUTOTEST_PATH=bin
is equivalent to the following, assuming the source directory is /src/foo-1.0:
PATH=/tmp/foo-1.0/bin:/src/foo-1.0/bin:$PATH ./micro-suite
Operation modes:
-h, --help print the help message, then exit
-V, --version print version number, then exit
-c, --clean remove all the files this test suite might create and exit
-l, --list describes all the tests, or the selected TESTS
Execution tuning:
-C, --directory=DIR
change to directory DIR before starting
--color[=never|auto|always]
enable colored test results on terminal, or always
-j, --jobs[=N]
Allow N jobs at once; infinite jobs with no arg (default 1)
-k, --keywords=KEYWORDS
select the tests matching all the comma-separated KEYWORDS
multiple `-k' accumulate; prefixed `!' negates a KEYWORD
--recheck select all tests that failed or passed unexpectedly last time
-e, --errexit abort as soon as a test fails; implies --debug
-v, --verbose force more detailed output
default for debugging scripts
-d, --debug inhibit clean up and top-level logging
default for debugging scripts
-x, --trace enable tests shell tracing
Other options:
-f, --frob=FOO frobnicate FOO
--opt-with-hyphen=ARG option name with hypen
--ping ping on every encounter
Report bugs to <address@hidden>.
General help using GNU software: <http://www.gnu.org/gethelp/>.
../../autoconf/tests/autotest.at:1184: $CONFIG_SHELL ./micro-suite -v -x --help
stdout:
Usage: ./micro-suite [OPTION]... [VARIABLE=VALUE]... [TESTS]
Run all the tests, or the selected TESTS, given by numeric ranges, and
save a detailed log file. Upon failure, create debugging scripts.
Do not change environment variables directly. Instead, set them via
command line arguments. Set `AUTOTEST_PATH' to select the executables
to exercise. Each relative directory is expanded as build and source
directories relative to the top level of this distribution.
E.g., from within the build directory /tmp/foo-1.0, invoking this:
$ ./micro-suite AUTOTEST_PATH=bin
is equivalent to the following, assuming the source directory is /src/foo-1.0:
PATH=/tmp/foo-1.0/bin:/src/foo-1.0/bin:$PATH ./micro-suite
Operation modes:
-h, --help print the help message, then exit
-V, --version print version number, then exit
-c, --clean remove all the files this test suite might create and exit
-l, --list describes all the tests, or the selected TESTS
Execution tuning:
-C, --directory=DIR
change to directory DIR before starting
--color[=never|auto|always]
enable colored test results on terminal, or always
-j, --jobs[=N]
Allow N jobs at once; infinite jobs with no arg (default 1)
-k, --keywords=KEYWORDS
select the tests matching all the comma-separated KEYWORDS
multiple `-k' accumulate; prefixed `!' negates a KEYWORD
--recheck select all tests that failed or passed unexpectedly last time
-e, --errexit abort as soon as a test fails; implies --debug
-v, --verbose force more detailed output
default for debugging scripts
-d, --debug inhibit clean up and top-level logging
default for debugging scripts
-x, --trace enable tests shell tracing
Other options:
-f, --frob=FOO frobnicate FOO
--opt-with-hyphen=ARG option name with hypen
--ping ping on every encounter
Report bugs to <address@hidden>.
General help using GNU software: <http://www.gnu.org/gethelp/>.
../../autoconf/tests/autotest.at:1184: grep ' -f, --frob.*frobnicate' stdout
stdout:
-f, --frob=FOO frobnicate FOO
../../autoconf/tests/autotest.at:1184: $CONFIG_SHELL ./micro-suite -x --frob
stderr:
micro-suite: error: `--frob' requires an argument
stdout:
../../autoconf/tests/autotest.at:1184: grep 'requires an argument' stderr
stdout:
micro-suite: error: `--frob' requires an argument
../../autoconf/tests/autotest.at:1184: $CONFIG_SHELL ./micro-suite -x --no-frob
stderr:
micro-suite: invalid option: --no-frob
Try `./micro-suite --help' for more information.
stdout:
../../autoconf/tests/autotest.at:1184: grep 'invalid option' stderr
stdout:
micro-suite: invalid option: --no-frob
../../autoconf/tests/autotest.at:1184: $CONFIG_SHELL ./micro-suite -x $args
--- /dev/null 2010-07-15 07:29:44.504439755 +0200
+++ /tmp/build/tests/testsuite.dir/at-groups/192/stderr 2010-07-20
06:02:21.000000000 +0200
@@ -0,0 +1,3 @@
+ERROR: 1 test was run,
+1 failed unexpectedly.
+sed: can't read config.log: No such file or directory
stdout:
## --------------------------------------------------- ##
## GNU Nonsense 1.0 test suite: artificial test suite. ##
## --------------------------------------------------- ##
1: test argument handling FAILED (micro-suite.at:14)
## ------------- ##
## Test results. ##
## ------------- ##
## ---------------------------- ##
## micro-suite.log was created. ##
## ---------------------------- ##
Please send `./micro-suite.log' and all information you think might help:
To: <address@hidden>
Subject: [GNU Nonsense 1.0] micro-suite: 1 failed
You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point. Its output may
be found below `./micro-suite.dir'.
../../autoconf/tests/autotest.at:1184: exit code was 1, expected 0
./micro-suite.log:
> ## --------------------------------------------------- ##
> ## GNU Nonsense 1.0 test suite: artificial test suite. ##
> ## --------------------------------------------------- ##
>
> micro-suite: command line was:
> $ ./micro-suite -x 1 FROB=default FROB_ARG=
>
> ## --------- ##
> ## Platform. ##
> ## --------- ##
>
> uname -m = i686
> uname -r = 2.6.26-2-686
> uname -s = Linux
[...]
> PATH: /tmp/build/tests
> PATH: /tmp/autoconf/tests
> PATH: /home/ralf/local/bin
> PATH: /usr/local/bin
> PATH: /usr/bin
> PATH: /bin
> PATH: /usr/bin/X11
> PATH: /usr/games
> PATH: /usr/X11R6/bin
>
> micro-suite: atconfig:
> | at_testdir=.
> | abs_builddir='/tmp/build/tests/testsuite.dir/192'
> | at_srcdir=.
> | abs_srcdir='/tmp/build/tests/testsuite.dir/192'
> | at_top_srcdir=.
> | abs_top_srcdir='/tmp/build/tests/testsuite.dir/192'
> | at_top_build_prefix=
> | abs_top_builddir='/tmp/build/tests/testsuite.dir/192'
>
> ## ---------------- ##
> ## Tested programs. ##
> ## ---------------- ##
>
> ## ------------------ ##
> ## Running the tests. ##
> ## ------------------ ##
> micro-suite: starting at: Tue Jul 20 06:02:21 CEST 2010
> micro-suite: ending at: Tue Jul 20 06:02:21 CEST 2010
> micro-suite: test suite duration: 0h 0m 0s
>
> ## ------------- ##
> ## Test results. ##
> ## ------------- ##
>
> ERROR: 1 test was run,
> 1 failed unexpectedly.
>
> ## ------------------------ ##
> ## Summary of the failures. ##
> ## ------------------------ ##
> Failed tests:
> GNU Nonsense 1.0 test suite: artificial test suite test groups:
>
> NUM: FILE-NAME:LINE TEST-GROUP-NAME
> KEYWORDS
>
> 1: micro-suite.at:12 test argument handling
>
> ## ---------------------- ##
> ## Detailed failed tests. ##
> ## ---------------------- ##
>
> # -*- compilation -*-
> 1. micro-suite.at:12: testing test argument handling ...
> ++ set +x
> ./micro-suite.at:13: test "$frob" = "$FROB"
> ++ test default = default
> ++ set +x
> ./micro-suite.at:14: test "$at_arg_frob" = "$FROB_ARG"
> ++ test '' = 0
> ./micro-suite.at:14: exit code was 1, expected 0
> 1. micro-suite.at:12: 1. test argument handling (micro-suite.at:12): FAILED
> (micro-suite.at:14)
>
>
> ## ---------- ##
> ## config.log ##
> ## ---------- ##
>
192. autotest.at:1184: 192. AT_ARG_OPTION_ARG (autotest.at:1184): FAILED
(autotest.at:1184)
- AT_ARG_OPTION_ARG test failure,
Ralf Wildenhues <=