On Saturday 13 November 2010, Freddy Vulto wrote:
> On 101113 11:04, Ville Skyttä wrote:
> > Cool, work on make (dist)check is appreciated. But (seemingly) all unit
> > tests are failing for me now, both when run with runUnit and with make
> > check.
>
> Both runUnit and `make check' running fine here. What is the error
> message exactly?
The expected one for each test. For example:
$ ./runUnit
[...]
Running ./unit/__expand_tilde_by_ref.exp ...
FAIL: ~user should return /home/user
FAIL: ~/foo should return /home/user/foo
FAIL: ~user/bar should return /home/user/bar
FAIL: ~user/$HOME should return /home/user/$HOME
[...]
Attached is the complete log/unit.log for a "./runUnit _count_args.exp" run
which finished with:
=== unit Summary ===
# of expected passes 1
# of unexpected failures 5
The results seem sane (for example there's a "2" for each "FAIL: ... should
set args to 2" etc) but for some reason it results in a FAIL nevertheless.
Just guessing, maybe something's wrong with the expected prompt?
I verified with git bisect that it's indeed commit c86b336 after which I
started seeing these failures.
Test Run By scop on Mon Nov 15 20:39:25 2010
Native configuration is x86_64-unknown-linux-gnu
=== unit tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/default.exp as tool-and-target-specific interface file.
Running ./unit/_count_args.exp ...
/@echo $?
0
/@is_bash_version_minimal 3 2 41 || set +o history
/@echo $?
0
/@BASH_COMPLETION_DIR=$(cd "$SRCDIR/.."; pwd)/completions
/@echo $?
0
/@BASH_COMPLETION_COMPAT_DIR=$BASH_COMPLETION_DIR
/@echo $?
0
/@BASH_COMPLETION=$(cd "$SRCDIR/.."; pwd)/bash_completion
/@echo $?
0
/@source "$BASH_COMPLETION"
/@echo $?
0
/@printf "%s" "$COMP_WORDBREAKS"
"'><=;|&(:/@echo $?
0
/@printf "%s " "${bash_versin...@]}"
4 1 7 1 release x86_64-redhat-linux-gnu /@echo $?
0
/@printf "%s" "$BASH_VERSION"
4.1.7(1)-release/@echo $?
0
/@printf "%s" "$TESTDIR"
/home/scop/cvs/bash-completion/test/@echo $?
0
/@eval $(locale); printf "%s" "$LC_CTYPE"
en_US.UTF-8/@echo $?
0
/@unset COMP_CWORD COMP_LINE COMP_POINT COMP_WORDS
/@echo $?
0
/@{ set; declare -F; shopt -p; } > "$TESTDIR/tmp/env.env1~"
/@echo $?
0
/@_count_args > /dev/null
/@echo $?
0
/@^C
/@COMP_WORDS=(a b); COMP_CWORD=1; COMP_LINE='a b'; COMP_POINT=3; _count_args; echo -n $args
1/@FAIL: a b| should set args to 1
^C
/@COMP_WORDS=(a bc); COMP_CWORD=1; COMP_LINE='a bc'; COMP_POINT=3; _count_args; echo -n $args
1/@FAIL: a b|c should set args to 1
^C
/@COMP_WORDS=(a b c); COMP_CWORD=2; COMP_LINE='a b c'; COMP_POINT=4; _count_args; echo -n $args
2/@FAIL: a b c| should set args to 2
^C
/@COMP_WORDS=(a b c); COMP_CWORD=1; COMP_LINE='a b c'; COMP_POINT=3; _count_args; echo -n $args
1/@FAIL: a b| c should set args to 1
^C
/@COMP_WORDS=(a b -c d); COMP_CWORD=2; COMP_LINE='a b -c d'; COMP_POINT=6; _count_args; echo -n $args
2/@FAIL: a b -c| d should set args to 2
^C
/@unset args COMP_CWORD COMP_LINE COMP_POINT COMP_WORDS
/@echo $?
0
/@{ set; declare -F; shopt -p; } > "$TESTDIR/tmp/env.env2~"
/@echo $?
0
/@diff_env "$TESTDIR/tmp/env.env1~" "$TESTDIR/tmp/env.env2~" "/COMP_WORDBREAKS=/{N
>
> d
>
> }" LAST-ARG
/@PASS: Environment should not be modified
testcase ./unit/_count_args.exp completed in 52 seconds
=== unit Summary ===
# of expected passes 1
# of unexpected failures 5
runtest completed at Mon Nov 15 20:40:17 2010
_______________________________________________
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
