[Bash-completion-devel] [bash-completion-Bugs][312323] Test suite bug: Double failure in assert_complete when returning nothing instead of multiple expected replies.

[bash-completion-bugs at alioth.debian.org]

Bugs item #312323, was opened at 2010-02-02 16:39 by Leonard Crestez
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312323&group_id=100114

Status: Open
Priority: 3
Submitted By: Leonard Crestez (cdleonard-guest)
Assigned to: Nobody (None)
Summary: Test suite bug: Double failure in assert_complete when returning nothing instead of multiple expected replies. 
Distribution: None
Originally reported in: None
Milestone: None
Status: None
Original bug number: 


Initial Comment:
This is easy to reproduce; just apply this one-line patch:

diff --git a/contrib/java b/contrib/java
index b9418ed..6bcffba 100644
--- a/contrib/java
+++ b/contrib/java
@@ -121,6 +121,7 @@ _java()
     local cur prev i
 
     COMPREPLY=()
+    return
     cur=`_get_cword`
     prev=${COMP_WORDS[COMP_CWORD-1]}
 
All it does is make the _java never return anything. This causes the java.exp test (./runCompletion completion/java.exp) to go from 6 passes to 2 passes and 7 failures. That is not good.

Apparently test/lib/library.exp:146 assumes that "$cmd\r\n" will always be echoed. This is false when COMPREPLY is empty and a "failure at timeout" is reported. The function caries on and another failure is reported at test/lib/library.exp:180.

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312323&group_id=100114