[lsb-discuss] Reporting dtk-manager-1.5 framework issues

Mon Dec 10 18:02:27 PST 2007

Hello, 

With the dtk-manager 1.5, I receive 76 additional failures in the core tests below compared to dtk-manager 1.4. I beleive these to be issues with the dtk-manager, as the testcases were passing while testing with dtk-manager 1.1-1.4.

FAILURES BELOW:

/tset/ANSI.os/locale/setlocale/T.setlocale 14 	Failed 	
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 6 	Failed 	
Messages from the test
setlocale does not change locale with invalid LANG
strcoll(a, A) failed
current language binding is VSX4L1
Expected return value < 0
Actual return value : 536870912
isupper(0x9c) failed
Current language binding is VSX4L1
Expected return value: 1
Actual return value: 0
isupper(0x9c) failed
Current language binding is VSX4L1
Expected return value: 1
Actual return value: 0
nl_langinfo(CRNCYSTR) failed
current language binding is VSX4L1
Expected currency -Dm
Actual currency -
sprintf(buf, "%4.2f", 12.34) failed
current language binding is VSX4L1
Expected radix character ,
Actual radix character .
strftime(pbuf, 12, "%a", timptr) failed
current language binding is VSX4L1
Expected day name Don
Actual day name Thu

* When the locale was successfully created, check the function which is effected by LC_CTYPE (e.g. isalpha) is executed correctly.

locale is broken or
iswctype and/or wctype don't behave correctly
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 7 	Failed 	
Messages from the test

* When the locale was successfully created, check the function which is effected by LC_COLLATE (e.g. strcoll) is executed correctly.

locale is broken or
wcscoll doesn't behave correctly
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 8 	Failed 	
Messages from the test

* When the locale was successfully created, check the function which is effected by LC_MONETARY (e.g. localeconv) is executed correctly.

locale is broken or
localeconv() doesn't behave correctly
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 9 	Failed 	
Messages from the test

* When the locale was successfully created, check the function which is effected by LC_NUMERIC (e.g. localeconv) is executed correctly.

locale is broken or
localeconv() doesn't behave correctly
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 10 	Failed 	
Messages from the test

* When the locale was successfully created, check the function which is effected by LC_TIME (e.g. nl_langinfo) is executed correctly.

locale is broken or
nl_langinfo(MON_2) doesn't behave correctly
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 11 	Failed 	
Messages from the test

* When the locale was successfully created, check the function which is effected by LC_MESSAGE (e.g. nl_langinfo) is executed correctly.

locale is broken or
nl_langinfo(YESEXPR) doesn't behave correctly
/tset/LI18NUX2K.L1/utils/comm/T.comm 1 	Failed 	
Messages from the test

* Verify this utility extracts the lines duplicated in file1 and file2 even if these files include multibyte character.

Can't handle multibyte characters.
/tset/LI18NUX2K.L1/utils/comm/T.comm 2 	Failed 	
Messages from the test

* Verify this utility extracts the lines duplicated in file1 and file2 when these files are ordered according to the collating sequence of the current locale.

Not ordered by the collating sequence.
/tset/LI18NUX2K.L1/utils/diff/T.diff 2 	Failed 	
Messages from the test

* When -b option is specified, verify this utility interprets whitespace character according to the current locale.

Can't interprets white space characters according to the current locale.
/tset/LI18NUX2K.L1/utils/egrep-tp/T.egrep-tp 5 	Failed 	
Messages from the test

* Verify this utility can perform pattern matching in searches without regard to case if -i option is specified.

Can't handle a pattern "ï¼¡ï½‚ï½ƒï¼¤" with -i.
/tset/LI18NUX2K.L1/utils/fgrep/T.fgrep 5 	Failed 	
Messages from the test

* Verify this utility can perform pattern matching in searches without regard to case if -i option is specified.

Can't handle a pattern "ï¼¡ï½‚ï½ƒï¼¤" with -i.
/tset/LI18NUX2K.L1/utils/fold/T.fold 1 	Failed 	
Messages from the test

* When this utility folds the lines without -b option, verify each line is not folded in the middle of character.

Some characters are not wrapped on the assigned width.
/tset/LI18NUX2K.L1/utils/fold/T.fold 2 	Failed 	
Messages from the test

* When this utility folds the lines with -b option, verify each line is not folded in the middle of character.

Some characters are not wrapped on the assigned width.
/tset/LI18NUX2K.L1/utils/fold/T.fold 3 	Failed 	
Messages from the test

* When this utility folds the lines with -s option, verify this utility interprets blank characters according to the current locale.

Some blank character is not interpreted.
/tset/LI18NUX2K.L1/utils/grep-tp/T.grep-tp 5 	Failed 	
Messages from the test

* Verify this utility can perform pattern matching in searches without regard to case if -i option is specified.

Can't handle a pattern "ï¼¡ï½‚ï½ƒï¼¤" with -i.
/tset/LI18NUX2K.L1/utils/join/T.join 3 	Failed 	
Messages from the test

* When -t option is specified, verify this utility uses given character as a separator even if the character is multibyte character.

This utility does not join the files.
/tset/LI18NUX2K.L1/utils/join/T.join 4 	Failed 	
Messages from the test

* When -t option is not specified, verify blank characters according to the current locale are used as input field separators.

This utility does not join the files.
/tset/LI18NUX2K.L1/utils/pr/T.pr 1 	Failed 	
Messages from the test

* When -w option is specified, verify this utility truncates the lines to make the length of the lines be less than or equal to the assigned width.

Can't truncates the input lines correctly.
/tset/LI18NUX2K.L1/utils/pr/T.pr 3 	Failed 	
Messages from the test

* When -n option is specified, verify this utility uses the given character as the separator between line number and first column.

Can't interpret character as the separator between line number and first column.
/tset/LI18NUX2K.L1/utils/pr/T.pr 4 	Failed 	
Messages from the test

* When -s option is specified, verify this utility uses the given character as the separator during the columns.

Can't interpret character as the separator during the columns.
/tset/LI18NUX2K.L1/utils/pr/T.pr 5 	Failed 	
Messages from the test

* When -i option is specified, verify this utility uses the given character as the character which multiple space characters is replaced with. The replaced space characters are to the next tab stop.

Can't replace the taget spaces with the character correctry.
/tset/LI18NUX2K.L1/utils/pr/T.pr 6 	Failed 	
Messages from the test

* When -e option is specified, verify this utility uses the given character as the character which is replaced with multiple space characters. The number of space characters is defined so that next character stands at tab_stop.

Can't replace the character with the spaces correctry.
/tset/LI18NUX2K.L1/utils/sed-tp/T.sed-tp 6 	Failed 	
Messages from the test

* Verify that 'y' command handle strings per 1 character.

Can't replace correctly.
/tset/LI18NUX2K.L1/utils/sort/T.sort 1 	Failed 	
Messages from the test

* Verify this utility sorts lines according to the collating sequence of the current locale.

Can't sort input lines according to the collating sequence.
/tset/LI18NUX2K.L1/utils/sort/T.sort 3 	Failed 	
Messages from the test

* When -d option is specified, verify this utility interprets which character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the current locale.
/tset/LI18NUX2K.L1/utils/sort/T.sort 6 	Failed 	
Messages from the test

* When -n option is specified, verify this utility sorts numeric order. (Especially check the radix character, thousands separator and minus sign are interpreted correctly.)

Can't sort in numeric order.
/tset/LI18NUX2K.L1/utils/sort/T.sort 8 	Failed 	
Messages from the test

* When -t option is specified, verify this utility use a character as a field separator even if the character is a multibyte character.

Can't handle field separator written in a multibyte chaaracter.
/tset/LI18NUX2K.L1/utils/sort/T.sort 9 	Failed 	
Messages from the test

* When -k keydef option is specified, verify this utility is able to define start/end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 10 	Failed 	
Messages from the test

* When -k keydef option is specified and keydef has a character b, verify this utility interprets which character is a blank character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 11 	Failed 	
Messages from the test

* When -k keydef option is specified and keydef has a character d, verify this utility interprets which character is a blank character or an alphanumeric character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 12 	Failed 	
Messages from the test

* When -k keydef option is specified and keydef has a character f, verify this utility treats a lower-case character as same as its upper-case character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 13 	Failed 	
Messages from the test

* When -k keydef option is specified and keydef has a character i, verify this utility interprets a printable character correctly in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 14 	Failed 	
Messages from the test

* When -k keydef option is specified and keydef has a character n, verify this utility sorts numeric order in the range which defined by keydef. (Especially check the radix character, thousands separator and sign are interpreted correctly.)

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 15 	Failed 	
Messages from the test

* When +pos option is specified, verify this utility is able to define start position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 16 	Failed 	
Messages from the test

* When -pos option is specified, verify this utility is able to define end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 17 	Failed 	
Messages from the test

* When -c option is specified, verify this utility checks the file whose lines are sorted according to the collating sequence of the current locale.

Can't sort input lines according to the collating sequence.
/tset/LI18NUX2K.L1/utils/sort/T.sort 19 	Failed 	
Messages from the test

* When -c and -d option are specified, verify this utility interprets which character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the current locale.
/tset/LI18NUX2K.L1/utils/sort/T.sort 22 	Failed 	
Messages from the test

* When -c and -n option are specified, verify this utility check the file whose lines are sorted numeric order. (Especially check the radix character, thousands separator and sign are interpreted correctly.)

Can't sort in numeric order.
/tset/LI18NUX2K.L1/utils/sort/T.sort 24 	Failed 	
Messages from the test

* When -c and -t option are specified, verify this utility use a character as a field separator even if the character is a multibyte character.

Can't handle field separator written in a multibyte chaaracter.
/tset/LI18NUX2K.L1/utils/sort/T.sort 25 	Failed 	
Messages from the test

* When -c and -k keydef option are specified, verify this utility is able to define start/end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 26 	Failed 	
Messages from the test

* When -c and -k keydef option are specified and the keydef has a character b, verify this utility interprets which character is a blank character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 27 	Failed 	
Messages from the test

* When -c and -k keydef option are specified and keydef has a character d, verify this utility interprets which character is a blank character or an alphanumeric character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 28 	Failed 	
Messages from the test

* When -c and -k keydef option is specified and keydef has a character f, verify this utility treats a lower-case character as same as its upper-case character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 29 	Failed 	
Messages from the test

* When -c and -k keydef option are specified and keydef has a character i, verify this utility interprets a printable character correctly in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 30 	Failed 	
Messages from the test

* When -c and -k keydef option are specified and keydef has a character n, verify this utility check the file whose lines are sorted numeric order in the range which defined by keydef. (Especially check the radix character, thousands separator and sign are interpreted correctly.)

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 31 	Failed 	
Messages from the test

* When -c and +pos option are specified, verify this utility is able to define start position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 32 	Failed 	
Messages from the test

* When -c and-pos option are specified, verify this utility is able to define end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 33 	Failed 	
Messages from the test

* When -m option is specified, verify the outputs this utility makes is sorted according to the collating sequence of the current locale.

Can't sort input lines according to the collating sequence.
/tset/LI18NUX2K.L1/utils/sort/T.sort 35 	Failed 	
Messages from the test

* When -m and -d option are specified verify this utility interprets which character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the current locale.
/tset/LI18NUX2K.L1/utils/sort/T.sort 38 	Failed 	
Messages from the test

* When -m and -n option are specified, verify the outputs this utility makes is sorted numeric order. (Especially check the radix character, thousands separator and sign are interpreted correctly.)

Can't sort in numeric order.
/tset/LI18NUX2K.L1/utils/sort/T.sort 40 	Failed 	
Messages from the test

* When -m and -t option are specified, verify this utility use a character as a field separator even if the character is a multibyte character.

Can't handle field separator written in a multibyte chaaracter.
/tset/LI18NUX2K.L1/utils/sort/T.sort 41 	Failed 	
Messages from the test

* When -m and -k keydef option are specified, verify this utility is able to define start/end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 42 	Failed 	
Messages from the test

* When -m and -k keydef option are specified and keydef has a character b, verify this utility interprets which character is a blank character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 43 	Failed 	
Messages from the test

* When -m and -k keydef option are specified and keydef has a character d, verify this utility interprets which character is a blank character or an alphanumeric character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 44 	Failed 	
Messages from the test

* When -m and -k keydef option are specified and keydef has a character f, verify this utility treats a lower-case character as same as its upper-case character in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 45 	Failed 	
Messages from the test

* When -m and -k keydef option are specified and keydef has a character i, verify this utility interprets a printable character correctly in the range which defined by keydef.

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 46 	Failed 	
Messages from the test

* When -m and -k keydef option are specified and keydef has a character n, verify the outputs this utility makes is sorted numeric order in the range which defined by keydef. (Especially check the radix character, thousands separator and sign are interpreted correctly.)

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 47 	Failed 	
Messages from the test

* When -m and +pos option are specified, verify this utility is able to define start position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 48 	Failed 	
Messages from the test

* When -m and -pos option are specified, verify this utility is able to define end position even if the lines have multibyte characters (Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
/tset/LI18NUX2K.L1/utils/unexpand/T.unexpand 1 	Failed 	
Messages from the test

* When -a option is specified and this utility processes tab and space characters, verify this utility determines the width in column positions each character would occupy on a constant-width font output device.

Can't determine width in column positions.
/tset/LI18NUX2K.L1/utils/uniq/T.uniq 2 	Failed 	
Messages from the test

* When -f option or -number is specified, this utility correctly recognizes the boundaries of words. The boundaries are shown as blank characters constituted in current locale.

This utility can not interpret blank characters
/tset/LI18NUX2K.L1/utils/uniq/T.uniq 3 	Failed 	
Messages from the test

* When -s option or +number is specified, this utility ignore the first n characters when doing comparisons even if the characters are multibyte characters.

This utility can not interpret multibyte characters
/tset/LI18NUX2K.L1/utils/wc/T.wc 1 	Failed 	
Messages from the test

* When -m option is specified, verify this utility outputs the number of characters in each input file even if the characters are multibyte characters.

Can't count number of characters.
/tset/LI18NUX2K.L1/utils/wc/T.wc 2 	Failed 	
Messages from the test

* When this utility writes to the standard output the number of words, this utility correctly recognizes the boundaries of words. The boundaries are shown as white-space characters constituted in current locale.

Can't count number of words.
/tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 5 	Failed 	These failures occur with cpio 2.6. There is a patch to fix this problem.
Messages from the test

* When -i option is specified, if extract files is selected in pattern form, '?' is matched 1 file-system-safe characters.

The archive file doesn't preserve file contents.
Comment:
http://www.linux-foundation.org/en/TestPilot31#cpio These failures occur with cpio 2.6. They are the result of a build system glitch in cpio, where the build system fails to properly detect the presence of the setlocale() function and disables it. There is a patch to cpio to fix this problem, follow the link above. Also see Debian bug 381348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348
/tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 6 	Failed 	These failures occur with cpio 2.6. There is a patch to fix this problem.
Messages from the test

* When -i option is specified, if extract files is selected in pattern form, matching list expression '[...]' is matched any one of the enclosed file-system-safe characters.

The archive file doesn't preserve file contents.
Comment:
http://www.linux-foundation.org/en/TestPilot31#cpio These failures occur with cpio 2.6. They are the result of a build system glitch in cpio, where the build system fails to properly detect the presence of the setlocale() function and disables it. There is a patch to cpio to fix this problem, follow the link above. Also see Debian bug 381348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348
/tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 7 	Failed 	These failures occur with cpio 2.6. There is a patch to fix this problem.
Messages from the test

* When -i option is specified, if extract files is selected in pattern form, a range expression '[c-c]' is matched any symbol between the pair (inclusive). The range expression may not be matched multi-character collating element and the range expression can be based on code point order instead of collating element order.

The archive file doesn't preserve file contents.
Comment:
http://www.linux-foundation.org/en/TestPilot31#cpio These failures occur with cpio 2.6. They are the result of a build system glitch in cpio, where the build system fails to properly detect the presence of the setlocale() function and disables it. There is a patch to cpio to fix this problem, follow the link above. Also see Debian bug 381348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348
/tset/LI18NUX2K.L1/utils/find/T.find 6 	Failed 	
Messages from the test

* If -name option is specified and the search pattern has '?', verify '?' is matched any file-system-safe characters.

Can't handle search pattern including `?'.
/tset/LI18NUX2K.L1/utils/find/T.find 8 	Failed 	
Messages from the test

* If -name option is specified and the search pattern has a matching list expression '[...]', verify the matching list expression is matched the character with the file-system-safe character which is in the list.

Can't handle search pattern including `[...]'.
/tset/LI18NUX2K.L1/utils/ls-fh/T.ls-fh 2 	Failed 	
Messages from the test

* When options which decide how to sort is not specified. verify this utility sorts output filename according to the collating sequence in the current locale.

Can't print filenames according to the collating sequence.
/tset/LI18NUX2K.L1/utils/tar-fh/T.tar-fh 3 	Failed 	
Messages from the test

* When keyword 't' is specified, verify this utility prints filenames which is written in file-system-safe characters.

Can't print filenames written in file-system-safe characters.
/tset/LI18NUX2K.L1/utils/tar-fh/T.tar-fh 6 	Failed 	
Messages from the test

* When keyword 'f' is specified, verify this utility handles the filename which is written in file-system-safe characters.

Can't handle filenames written in file-system-safe characters.
/tset/LI18NUX2K.L1/utils/gencat/T.gencat 1 	Failed 	
Messages from the test

* When keyword 'f' is specified, verify this utility handles the filename which is written in file-system-safe characters.
Cannot handle filename written in file-system-safe characters.
/tset/LI18NUX2K.L1/utils/gencat/T.gencat 2 	Failed 	
Messages from the test

* When inserting a message text file into an existing message catalog file, if the set and message numbers do not collide, the new message text shall be added to the existing catalog file without changing existing messages.
The test output did not match what was expected
expected: ãƒ‡ã‚£ã‚¹ã‚¯ "1st Disk" ã«ã¯ ä½•ã‚‚ãƒ•ã‚¡ã‚¤ãƒ«ãŒå«ã¾ã‚Œã¦ã„ã¾ã›ã‚“ã€‚
expected: ãƒ‡ã‚£ã‚¹ã‚¯ "2nd Disk" ã«ã¯ 1 å€‹ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚
expected: ãƒ‡ã‚£ã‚¹ã‚¯ "3rd Disk" ã«ã¯ 367 å€‹ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚
expected: ãƒ‡ã‚£ã‚¹ã‚¯ "4th Disk" ã«ã¯ 15 å€‹ã®ãƒ†ã‚ã‚¹ãƒˆãƒ•ã‚¡ã‚¤ãƒ«ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚
got: The disk 1st Disk contains 0 file(s).
got: The disk 2nd Disk contains 1 file(s).
got: The disk 3rd Disk contains 367 file(s).
got: The disk 4th Disk contains 15 file(s).
/tset/LI18NUX2K.L1/utils/gencat/T.gencat 3 	Failed 	

Henry Yei
MontaVista Software, Inc.
hyei at mvista.com