TestPilot32-M2008
From The Linux Foundation
Contents |
[edit] Summary
Command Tests
Command Check v 3.1.95.20071225-1 Success Passed: 147
Static Interface Tests
Library Check v 3.1.95.20071225-1 Failures: 6 Passed: 47688
Runtime Interface Tests
Core Tests v 3.1.95-4 Failures: 151 Passed: 5236
Desktop-T2C Tests v 3.1.95-3 Failures: 13 Passed: 2792
Desktop Tests: v 3.1.95-5
Fontconfig Tests Success Passed: 3
FreeType Tests Success Passed: 4
GTK Tests Failures: 5 Passed: 8149
Libpng Tests Success Passed: 137
Libxml Tests Success Passed: 2314
Qt3 Tests Success Passed: 26
Qt4 Tests Failures: 6 Passed: 1363
XRender Tests Success Passed: 1
Xft Tests Success Passed: 4
Libstdc++ Tests v 3.4.3-6.95 Success Passed: 1274
Perl Tests v 3.1.95-3 Failures: 12 Passed: 915
Python Runtime Tests v 3.1.95-3 Failures: 1 Passed: 107
X11 Tests (XTS5) v 5.1.5-4 Failures: 12 Passed: 3389
Automated Application Battery Tests
Apache Tests v 2.2.4-2 Failures: 1 Passed: 4
Expect Tests v 5.43.0-5 Success Passed: 6
Groff Tests v 1.19.2-2 Success Passed: 5
Lynx Tests v 2.8.6-1 Success Passed: 20
Python Tests v 2.4.4-1 Failures: 2 Passed: 290
Raptor Tests v 1.4.15-1 Success Passed: 56
Rsync Tests v 2.6.9-1 Success Passed: 6
Samba Tests v 3.0.25b-1 No Result [?] Passed: 0
Tcl Tests v 8.5a4-1 Failures: 55 Passed: 134
Xpdf Tests v 1.01-5 Success Passed: 3
[edit] Details on suites with failing tests
[edit] Library Check v 3.1.95.20071225-1
libstdc++.so.6 2926 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNKSt9type_info10__do_catchEPKS_PPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (found) Virtual Function[0][4] _ZNKSt9type_info10__do_catchEPKS_PPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found) libstdc++.so.6 2939 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNKSt9type_info10__do_catchEPKS_PPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (found) Virtual Function[0][4] _ZNKSt9type_info10__do_catchEPKS_PPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found) libstdc++.so.6 3004 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv (found) Virtual Function[0][4] _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found) libstdc++.so.6 3017 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv (found) Virtual Function[0][4] _ZNK10__cxxabiv117__class_type_info10__do_catchEPKSt9type_infoPPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNK10__cxxabiv117__class_type_info11__do_upcastEPKS0_PPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found) libstdc++.so.6 3030 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNKSt9type_info10__do_catchEPKS_PPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (found) Virtual Function[0][4] _ZNKSt9type_info10__do_catchEPKS_PPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found) libstdc++.so.6 3043 Failed Virtual Function[0][2] _ZNKSt9type_info14__is_pointer_pEv (expected) doesn't match _ZNK10__cxxabiv117__pbase_type_info10__do_catchEPKSt9type_infoPPvj (found) Virtual Function[0][3] _ZNKSt9type_info15__is_function_pEv (expected) doesn't match _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (found) Virtual Function[0][4] _ZNK10__cxxabiv117__pbase_type_info10__do_catchEPKSt9type_infoPPvj (expected) doesn't match _ZNKSt9type_info14__is_pointer_pEv (found) Virtual Function[0][5] _ZNKSt9type_info11__do_upcastEPKN10__cxxabiv117__class_type_infoEPPv (expected) doesn't match _ZNKSt9type_info15__is_function_pEv (found)
[edit] Core Tests v 3.1.95-4
/tset/ANSI.os/maths/pow/T.pow 4 Warning (quelled) Insignificant
pow(0.0, -1.0) gave
RETURN VALUES: expected: -inf, observed: inf
Bit Representation: expected value: \000\000\000\000\000\000\360\377
Bit Representation: observed value: \000\000\000\000\000\000\360\177
Comment:
Both -inf and +inf are equally artificial results, Linux libc picks this one.
/tset/ANSI.os/streamio/fopen/T.fopen 28 Warning (quelled) Insignificant
fopen() succeeded when FOPEN_MAX streams were already open
Comment:
FOPEN_MAX is just an advisory limit, there is probably no real limit except memory.
/tset/ANSI.os/streamio/remove_X/T.remove_X 1 Warning (quelled) Feature
remove("remove_X-t.1") did not give correct results
RETURN VALUES: expected: -1, observed: 0
ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
Linux allows to remove a running executable file without any side effects.
/tset/ANSI.os/streamio/tmpfile/T.tmpfile 2 Warning (quelled) Feature
Note: There is a known issue with this test, see POSIX interpretation 1003.1-1990 #74
Note: This test is waived for LSB testing, please see the waivers database
tmpfile() did not creat file with mode 0666 when umask was set to 0, found 0600
Comment:
Not a bug but feature. Linux tmpfile() creates files with access rights 0600 which is more secure than POSIX mandated 0666.
/tset/ANSI.os/streamio/tmpfile/T.tmpfile 6 Failed
st_atime field on created file was not marked for update
st_ctime field on created file was not marked for update
st_mtime field on created file was not marked for update
/tset/POSIX.os/dataform/tar/T.tar 12 FIP (quelled) Correct
create utility exited with code 1
Comment:
This test tries to call tar with a file with too long name (>100 chars). The tar utility can either skip the file, or fail completely; both results are correct.
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 19 Warning (quelled) Normal
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/c_lflag/T.c_lflag 6 Warning (quelled) Normal
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/tcdrain/T.tcdrain 2 Warning (quelled) Normal
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 8 Warning (quelled) Normal
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/files/access_X/T.access_X 1 Warning (quelled) Feature
access("access_X-t.1", W_OK) did not give correct results
RETURN VALUES: expected: -1, observed: 0
ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
On Linux, running executable files are normally accessible.
/tset/POSIX.os/files/fstat/T.fstat 1 Failed
fstat() set st_atime incorrectly: expected 1199581805, observed 1199581804
fstat() set st_mtime incorrectly: expected 1199581807, observed 1199581806
fstat() set st_ctime incorrectly: expected 1199581807, observed 1199581806
path tracing error: path counter 6, expected 7
/tset/POSIX.os/files/rename_X/T.rename_X 1 Warning (quelled) Feature
rename("rename_X-t.1a", "rename_X-t.1b") did not give correct results
RETURN VALUES: expected: -1, observed: 0
ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
Not a bug but feature. On Linux, running executable files are normally accessible.
/tset/POSIX.os/files/stat_X/T.stat_X 1 FIP [?]
stat("/opt/lsb/test/core/tet/test_sets/nonexistb", buf) returned st_rdev value of 0xfb01
/tset/POSIX.os/files/stat_X/T.stat_X 2 FIP (quelled) Correct
stat("/dev/tty", buf) returned st_rdev value of 0x500
Comment:
This is a correct result, /dev/tty has major/minor number 0x0500.
/tset/POSIX.os/files/unlink_X/T.unlink_X 1 Warning (quelled) Feature
unlink("unlink_X-t.1") did not give correct results
RETURN VALUES: expected: -1, observed: 0
ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
On Linux, running executable files are normally accessible.
/tset/POSIX.os/files/posix_madvise/T.posix_madvise 4 Failed
posix_madvise returned 0 instead of EINVAL
/tset/POSIX.os/ioprim/read/T.read 13 Failed
time stamps incorrect: atime was not updated
/tset/POSIX.os/ioprim/read/T.read 15 Failed
time stamps incorrect: atime was not updated
/tset/POSIX.os/procenv/sysconf/T.sysconf 3 Warning (quelled) Insignificant
CLK_TCK not defined (obsolescent in POSIX but required)
Comment:
Insignificant; CLK_TCK is obsolete anyway.
/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 2 Failed
sysconf(_SC_XOPEN_VERSION) failed expected 500 - got 600
/tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 17 FIP [?]
sysconf(_SC_XOPEN_ENH_I18N) returned 1
- indicating the feature group is fully supported
sysconf(_SC_XOPEN_CRYPT) returned 1
- indicating the feature group is supported
sysconf(_SC_XOPEN_SHM) returned 1
- indicating the feature group is supported
sysconf(_SC_XOPEN_LEGACY) returned 1
- indicating the feature group is fully supported
/tset/POSIX.os/procenv/uname/T.uname 1 FIP [?]
system name - Linux
node name - mdw-linux.wichmann.us
release - 2.6.22.12-laptop-1mdv
version - #1 SMP Tue Nov 20 09:05:54 EST 2007
machine - i686
/tset/POSIX.os/procprim/exec/T.execl 31 Failed
After execl(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/exec/T.execle 31 Failed
After execle(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/exec/T.execlp 31 Failed
After execlp(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/exec/T.execv 31 Failed
After execv(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/exec/T.execve 31 Failed
After execve(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/exec/T.execvp 31 Failed
After execvp(../exec_tok, ...) completed successfully
time stamps incorrect: atime was not updated
/tset/POSIX.os/procprim/kill_X/T.kill_X 1 Warning (quelled) Insignificant
process calling kill() did not receive signal 10
Comment:
The Linux implementation of kill() sends the signal to everyone except its own process, which is also logical.
/tset/initd/misc/install/general-tc 3 Failed
Reference 20.3-3(C) Testing activation of initscript
If an initscript depends on a boot facility it shall not be
activated by a call to install_initd if the dependency is not met
Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initA
exit code 0 returned, expected 1
Check that lsb-initA is not installed in initscript directories
/etc/rc.d/rc0.d/K50lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc1.d/K50lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc2.d/S51lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc3.d/S51lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc4.d/S51lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc5.d/S51lsb-initA: found a symlink
exit code 2 returned, expected 1
/etc/rc.d/rc6.d/K50lsb-initA: found a symlink
exit code 2 returned, expected 1
Cleanup, deactivate initscripts, if any
Cleanup, remove initscript files, if any
/tset/initd/misc/install/general-tc 5 Failed
Reference 20.4-5(C) Testing deactivation of initscript
If a boot facility provided by an initscript is depended on by another
initscript the script shall not be deactivated by a call to remove_initd
Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initB
Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initA
Check that lsb-initA is installed in initscript directories
/etc/rc.d/rc0.d/K50lsb-initA: found a symlink
/etc/rc.d/rc1.d/K50lsb-initA: found a symlink
/etc/rc.d/rc2.d/S51lsb-initA: found a symlink
/etc/rc.d/rc3.d/S51lsb-initA: found a symlink
/etc/rc.d/rc4.d/S51lsb-initA: found a symlink
/etc/rc.d/rc5.d/S51lsb-initA: found a symlink
/etc/rc.d/rc6.d/K50lsb-initA: found a symlink
Check that lsb-initB is installed in initscript directories
/etc/rc.d/rc0.d/K50lsb-initB: found a symlink
/etc/rc.d/rc1.d/K50lsb-initB: found a symlink
/etc/rc.d/rc2.d/S50lsb-initB: found a symlink
/etc/rc.d/rc3.d/S50lsb-initB: found a symlink
/etc/rc.d/rc4.d/S50lsb-initB: found a symlink
/etc/rc.d/rc5.d/S50lsb-initB: found a symlink
/etc/rc.d/rc6.d/K50lsb-initB: found a symlink
Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initB
exit code 0 returned, expected non-zero
Check that lsb-initB is installed in initscript directories
/etc/rc.d/rc0.d/K??lsb-initB: file not found
/etc/rc.d/rc1.d/K??lsb-initB: file not found
/etc/rc.d/rc2.d/S??lsb-initB: file not found
exit code 1 returned, expected 2
/etc/rc.d/rc3.d/S??lsb-initB: file not found
exit code 1 returned, expected 2
/etc/rc.d/rc4.d/S??lsb-initB: file not found
exit code 1 returned, expected 2
/etc/rc.d/rc5.d/S??lsb-initB: file not found
exit code 1 returned, expected 2
/etc/rc.d/rc6.d/K??lsb-initB: file not found
Cleanup, deactivate initscripts, if any
Cleanup, remove initscript files, if any
/tset/LI18NUX2K.L1/base/bind_textdomain_codeset/T.bind_textdomain_codeset 1 Failed
When the codeset argument is a valid codeset name which can
be used for the iconv_open() function, verify that the
codeset of message outputted by gettext family is converted
into codeset argument.
gettext got wrong text. So bind_textdomain_codeset,
bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/bindtextdomain/T.bindtextdomain 1 Failed
Verify that this function specifies that the domainname
message catalog will be found in the dirname directory
hierarchy.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/bindtextdomain/T.bindtextdomain 2 Failed
Veirfy that this function applies domainname to the currently
active LC_MESSAGES locale.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/bindtextdomain/T.bindtextdomain 3 Failed
Verify that this function specifies the message even if the
dirname directory is absolute pathname.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/bindtextdomain/T.bindtextdomain 4 Failed
Verify that this function specifies the message even if the
dirname directory is relative pathname.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 1 Failed
Verify that this function locates the message according to
the string pointed by domainname.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 2 Failed
When category is LC_CTYPE, verify the message catalog file
under the LC_CTYPE directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 3 Failed
When category is LC_COLLATE, verify the message catalog file
under the LC_COLLATE directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 4 Failed
When category is LC_MESSAGES, verify the message catalog file
under the LC_MESSAGES directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 5 Failed
When category is LC_MONETARY, verify the message catalog file
under the LC_MONETARY directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 6 Failed
When category is LC_NUMERIC, verify the message catalog file
under the LC_NUMERIC directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcgettext/T.dcgettext 7 Failed
When category is LC_TIME, verify the message catalog file
under the LC_TIME directory is located.
dcgettext got wrong text.
So bindtextdomain, textdomain or dcgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dgettext/T.dgettext 1 Failed
Verify that this function locates the message according to
the string pointed by domainname.
dgettext got wrong text.
So bindtextdomain, textdomain or dgettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 1 Failed
Verify that this function locates the message according to
the string pointed by domainname.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 2 Failed
When category is LC_CTYPE, verify the message catalog file
under the LC_CTYPE directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 3 Failed
When category is LC_COLLATE, verify the message catalog file
under the LC_COLLATE directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 4 Failed
When category is LC_MESSAGES, verify the message catalog file
under the LC_MESSAGES directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 5 Failed
When category is LC_MONETARY, verify the message catalog file
under the LC_MONETARY directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 6 Failed
When category is LC_NUMERIC, verify the message catalog file
under the LC_NUMERIC directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dcngettext/T.dcngettext 7 Failed
When category is LC_TIME, verify the message catalog file
under the LC_TIME directory is located.
dcngettext got wrong text.
So bindtextdomain, textdomain or dcngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/dngettext/T.dngettext 1 Failed
Verify that this function locates the message according to
the string pointed by domainname.
dngettext got wrong text.
So bindtextdomain, textdomain or dngettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/textdomain/T.textdomain 1 Failed
When the domainname is not NULL nor the pointer to null
string and this function called successfully, verify that
the message outputted by gettext family searches the message
from domain whose name is domainname.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/textdomain/T.textdomain 4 Failed
When the domainname is the pointer to null string and this
function called successfully, verify that the current domain
is changed to `messages'.
gettext got wrong text.
So bindtextdomain, textdomain or gettext works incorrectly.
path tracing error: path counter 0, expected 1
/tset/LI18NUX2K.L1/base/strptime/T.strptime 32 Failed
If the conversion character is `EY', verify this function converts the characters which is the full alternative year representation.
Test Locale is LTP_1.UTF-8
The locale's alternative year representation is not interpreted correctly.
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 3 Warning (quelled) Waived
* When the locale specification exceeded implementation limits or the coded character set or sets used were not supported by the implementation, and no locale was created, verify the exit value is 2.
created locale unexpectedly
This test should not create locale and exit code code sould be 2.
eixt code of localedef is 0
if exit code is more than 3, please check directory if user 'vsx0' has write permission of the locale directory
*) This test result is waived now.
Comment:
This test is waived by the LSB committee.
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 11 Failed
* 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
* 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
* 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/join/T.join 1 Failed
* Verify this utility joins files and writes the results correctly, when these files is ordered according to the collating sequence of the current locale.
This utility does not join the files.
/tset/LI18NUX2K.L1/utils/join/T.join 2 Failed
* When -e option is specified, verify this utility replaces empty output fields in the list selected by -o with the string even if the string is written in multibyte characters.
This utility does not join the files.
/tset/LI18NUX2K.L1/utils/join/T.join 3 Failed
* 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
* 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/sort/T.sort 1 Failed
* 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 2 Failed
* When -u option is specified, verify duplicate lines are turned into one line even if the lines have multibyte characters.
Can't unify duplicate lines including multibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 3 Failed
* 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 4 Failed
* When -f option is specified, verify this utility treats a lower-case character as same as its upper-case character.
Can't interpret a lower-case character as upper-case character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 5 Failed
* When -i option is specified, verify this utility interprets a printable character correctly.
Can't interpret printable characters correctly.
/tset/LI18NUX2K.L1/utils/sort/T.sort 6 Failed
* 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 7 Failed
* When -b option is specified, verify this utility interprets which character is a blank character.
Can't interpret blank character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 9 Failed
* 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
* 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
* 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 13 Failed
* 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 15 Failed
* 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
* 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
* 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 18 Failed
* When -c and -u option are specified, verify this utility checks the file which has duplicate lines even if the lines have multibyte characters.
Can't unify duplicate lines including multibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 19 Failed
* 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 20 Failed
* When -c and -f option are specified, verify this utility treats a lower-case character as same as its upper-case character.
Can't interpret a lower-case character as upper-case character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 21 Failed
* When -c and -i option are specified, verify this utility interprets a printable character correctly.
Can't interpret printable characters correctly.
/tset/LI18NUX2K.L1/utils/sort/T.sort 22 Failed
* 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 23 Failed
* When -c and -b option are specified, verify this utility interprets which character is a blank character.
Can't interpret blank character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 25 Failed
* 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
* 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
* 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 29 Failed
* 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 31 Failed
* 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
* 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
* 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 34 Failed
* When -m and -u option are specified, verify duplicate lines are turned into one line even if the line have multibyte characters.
Can't unify duplicate lines including multibyte characters.
/tset/LI18NUX2K.L1/utils/sort/T.sort 35 Failed
* 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 36 Failed
* When -m and -f option are specified, verify this utility treats a lower-case character as same as its upper-case character.
Can't interpret a lower-case character as upper-case character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 37 Failed
* When -m and -i option are specified, verify this utility interprets a printable character correctly.
Can't interpret printable characters correctly.
/tset/LI18NUX2K.L1/utils/sort/T.sort 38 Failed
* 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 39 Failed
* When -m and -b option are specified, verify this utility interprets which character is a blank character.
Can't interpret blank character.
/tset/LI18NUX2K.L1/utils/sort/T.sort 41 Failed
* 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
* 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
* 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 45 Failed
* 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 47 Failed
* 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
* 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/uniq/T.uniq 1 Failed
* Verify this utility compares text files which have multibyte characters.
This utility can not compares text files
/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.
* 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/ls-fh/T.ls-fh 2 Failed
* 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/msgfmt/T.msgfmt 1 Failed
Verify this utility creates message object
file which can be gotten messages by gettext
family library.
The gettext library gets wrong message
/tset/LI18NUX2K.L1/utils/msgfmt/T.msgfmt 6 Failed
When '-f' or '--use-fuzzy' option is specified,
verify that the fuzzy entries are included into
the output.
The gettext library gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 1 Failed
When the operand 'textdomain' is present, verify
that this utility uses the value of the operand
as dommain name.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 2 Failed
When '-d dommainname' or '--domain=dommainname'
option is specified, verify this utility uses
dommainname as dommain name.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 3 Failed
With the following situation, check that this utility
uses the value of TEXTDOMAIN as dommain name.
* The operand 'textdomain' is not present.
* '-d dommainname' and '--domain=dommainname'
option are not specified.
* The environment variable TEXTDOMAIN is set.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 6 Failed
When the environment variable TEXTDOMAINDIR is set,
verify that this utility uses the value of
TEXTTDOMAINDIR as dirname.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 8 Failed
Verify that the name of the current locale is used as lang.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 9 Failed
When '-e' option is specified, verify that this utility
interprets \t for tab character.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 11 Failed
When '-e' option is specified, verify that this utility
interprets \n for newline character.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 12 Failed
When '-n' option is specified, verify that this utility
suppress trailing newline.
The gettext gets wrong message
/tset/LI18NUX2K.L1/utils/gettext/T.gettext 13 Failed
When '-s' option is specified, verify that the behavior of
this utility is similar to the behavior of the echo utility
except to translate the message which is found in the
selected catalog.
The gettext gets wrong message
/tset/LSB.fhs/root/bin/bin-tc 37 Failed
Reference 3.4-37 (C)
If the implementation supports a C Shell or equivalent (tcsh):
The path name of the C Shell shall be /bin/csh.
/bin/csh is not executable
/tset/LSB.fhs/root/bin/bin-tc 47 Failed
Reference 3.4-47 (A)
The gunzip utility shall be a hard link or symlink to the gzip utility
The gunzip utility is not a hard link to gzip
exit code 1 returned, expected 0
Unexpected output written to stdout, as shown below:
stdout:/bin/gunzip expected to be symlink to /bin/gzip, returned non-symlink
/tset/LSB.fhs/root/bin/bin-tc 48 Failed
Reference 3.4-48 (A)
The zcat utility shall be a hard link or symlink to the gzip utility
The zcat utility is not a hard link to gzip
exit code 1 returned, expected 0
Unexpected output written to stdout, as shown below:
stdout:/bin/zcat expected to be symlink to /bin/gzip, returned non-symlink
/tset/LSB.fhs/var/spool-lpd/spool-lpd-tc 2 FIP (quelled) Normal
Reference 5.14.3-2(C)
If the implementation has the lpd daemon running then
The lock file /var/spool/lpd/lpd.lock exists
/var/spool/lpd/lpd.lock: file not found
exit code 1 returned, expected 0
This test result needs to be manually resolved
Comment:
Normal when lpd is not installed.
/tset/LSB.fhs/var/spool-rwho/spool-rwho-tc 1 FIP (quelled) Normal
Reference 5.14.4-1(C)
If the subsystem is supported
The /var/spool/rwho directory exists and is searchable
/var/spool/rwho: directory not found
exit code 1 returned, expected 0
This test result needs to be manually resolved, returning FIP result
Comment:
Normal when rwho is not installed.
/tset/LSB.os/genuts/ftw_L/T.ftw_L 4 Warning (quelled) Insignificant
ftw did not call function with argument FTW_SL and
correct first and second arguments when traversing
file tree
Comment:
The linux ftw() function follows symlinks, it does not report them.
/tset/LSB.os/genuts/getopt/T.getopt 1 Warning (quelled) Known minor bug
getopt() failed when called with :-
optstring : [ab:cd:e]
arguments : [-a] [-d]
optind : [2]
getopt() failed on the following :-
optind : expected [4], actual [3]
getopt() failed when called with :-
optstring : [ab:cd:e]
arguments : [-ab]
optind : [1]
getopt() failed on the following :-
optind : expected [3], actual [2]
getopt() failed when called with :-
optstring : [:ab:cd:e]
arguments : [-a] [-d]
optind : [2]
getopt() failed on the following :-
optind : expected [4], actual [3]
getopt() failed when called with :-
optstring : [:ab:cd:e]
arguments : [-ab]
optind : [1]
getopt() failed on the following :-
optind : expected [3], actual [2]
Comment:
This is a known minor bug related to locale handling.
/tset/LSB.os/ioprim/readv_L/T.readv_L 13 Failed
time stamps incorrect: atime was not updated
/tset/LSB.os/ioprim/readv_L/T.readv_L 15 Failed
time stamps incorrect: atime was not updated
/tset/LSB.os/ipc/msgsnd/T.msgsnd 1 Failed
msg_stime not set as expected
Expected range: 1199589997 - 1199589997, Observed: 1199589996
/tset/LSB.os/libm/fpeOver/T.fpeOver 1 Unreported
When feenableexcept(FE_OVERFLOW) is set, and triggered by an overflow, the exception shall be handled by the defined signal handler.
/tset/LSB.os/libm/fpeOver/T.fpeOver 2 Unresolved
unexpected signal 8 (SIGFPE) received
/tset/LSB.os/libm/fpeUnder/T.fpeUnder 1 Unreported
When feenableexcept(FE_UNDERFLOW) is set, and triggered by an underflow, the exception shall be handled by the defined signal handler.
/tset/LSB.os/libm/fpeUnder/T.fpeUnder 2 Failed
When fedisableexcept(FE_UNDERFLOW) is set, and triggered by an underflow, the exception should not be handled by the defined signal handler.
Signal handler fpeHandler2 called when not expected
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5 Failed (quelled) TEF's fault
pam_authenticate returned Authentication failure when expected to succeed
uid : 501
euid : 0
initialise failed
Comment:
This test fails because Test Execution Framework hacks PAM in order to let vsx0 user do super-user's actions without asking for password. The details haven't been explored, but this failure doesn't appear if the test has been runned without DTK Manager.
/tset/LSB.usersgroups/usersgroups/names/names-tc 6 Warning
Reference User & Group Names 16-1
If User Name (sync) exists it should be in the Group (sync)
WARNING: User Name (sync) is in the wrong group (root).
/tset/LSB.usersgroups/usersgroups/names/names-tc 7 Warning
Reference User & Group Names 16-1
If User Name (shutdown) exists it should be in the Group (shutdown)
WARNING: User Name (shutdown) is in the wrong group (root).
/tset/LSB.usersgroups/usersgroups/names/names-tc 8 Warning
Reference User & Group Names 16-1
If User Name (halt) exists it should be in the Group (halt)
WARNING: User Name (halt) is in the wrong group (root).
/tset/LSB.usersgroups/usersgroups/names/names-tc 14 Warning
Reference User & Group Names 16-1
If User Name (nobody) exists it should be in the Group (nobody)
WARNING: User Name (nobody) is in the wrong group (nogroup).
/tset/LSB.usersgroups/commands/misc/T.misc 29 Unresolved
chsh -s: change login shell. - Reference the Commands and Utilities chapter in the Specification
login shell should changed for the test user.
Un-able to add a test user vsxyy123
/tset/LSB.usersgroups/commands/misc/T.misc 30 Unresolved
chfn -f: set the user's full name - Reference the Commands and Utilities chapter in the Specification
User's fullname should change accordingly.
Un-able to add a test user vsxyy123
/tset/LSB.usersgroups/commands/misc/T.misc 33 Unresolved
chfn -h: set the user's home phone number. - Reference the Commands and Utilities chapter in the Specification
User's home phone number should change accordingly.
Un-able to add a test user vsxyy123
/tset/LSB.usersgroups/commands/misc/T.misc 35 Unresolved
groups - display groups the user is in. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user: useradd -g
/tset/LSB.usersgroups/commands/misc/T.misc 36 Unresolved
newgrp - change group ID. - Reference the Commands and Utilities chapter in the Specification
Should change to a new group.
Un-able to add a test group: groupadd
/tset/LSB.usersgroups/commands/misc/T.misc 37 Unresolved
usermod -s :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -s UNRESOLVED: Can not add a test user vsx21
/tset/LSB.usersgroups/commands/misc/T.misc 38 Unresolved
usermod -u :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -u UNRESOLVED: Can not add a test user vsx22
/tset/LSB.usersgroups/commands/misc/T.misc 39 Unresolved
usermod -e :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -e UNRESOLVED: Can not add a test user vsx23
/tset/LSB.usersgroups/commands/misc/T.misc 40 Unresolved
passwd - change a user password. - Reference the Commands and Utilities chapter in the Specification
Password for the user should be change.
Un-able to add a test user: useradd
/tset/LSB.usersgroups/commands/misc/T.misc 41 Unresolved
passwd -x: set the max number of days a password remains valid. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 42 Unresolved
passwd -n: set the min number of days before a password may be changed. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 43 Unresolved
passwd -w: Set the number of days warning the user will receive before their password will expire. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 44 Unresolved
passwd -i: Disable an account after the password has been expired for the given number of days. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 45 Unresolved
passwd -l: Disable an account by changing its password. - Reference the Commands and Utilities chapter in the Specification
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 46 Unresolved
passwd -u: Re-enable an account. - Reference the Commands and Utilities chapter in the Specification
The account's password should change back to
its previous value.
Un-able to add a test user with a given password: useradd -p
/tset/LSB.usersgroups/commands/misc/T.misc 47 Failed
groupadd : Create a new group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
/tset/LSB.usersgroups/commands/misc/T.misc 48 Failed
groupadd -g: Create a new group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
/tset/LSB.usersgroups/commands/misc/T.misc 49 Unresolved
groupadd -g -o : Create a new group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
/tset/LSB.usersgroups/commands/misc/T.misc 50 Unresolved
groupdel : delete a group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
/tset/LSB.usersgroups/commands/misc/T.misc 51 Unresolved
groupmod : modify a group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
Un-able to add new group: vsxg20
/tset/LSB.usersgroups/commands/misc/T.misc 52 Unresolved
groupmod -g : modify a group - Reference the Commands and Utilities chapter in the Specification
vsxg20 was not added
Un-able to add new group
/tset/LSB.usersgroups/commands/misc/T.misc 53 Unresolved
groupmod -g -o modify a group - Reference the Commands and Utilities chapter in the Specification
foo11 was not added
Un-able to add new group: foo11
/tset/LSB.usersgroups/commands/misc/T.misc 54 Failed
useradd :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx24 was not added.
useradd : FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 55 Failed
useradd -d :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx25 was not found
useradd -d: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 56 Failed
useradd -c :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx26 was not found
useradd -c: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 57 Failed
useradd -g :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx27 was not found
useradd -g: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 58 Unresolved
usermod -p :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
User vsx28 was not added.
usermod -p UNRESOLVED: Can not add a test user vsx28
/tset/LSB.usersgroups/commands/misc/T.misc 59 Failed
useradd -u :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx29 was not found
/tset/LSB.usersgroups/commands/misc/T.misc 60 Failed
useradd -e :Create a new user. - Reference the Commands and Utilities chapter in the Specification
Can not useradd -e vsx30
useradd -e: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 61 Failed
useradd -f :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx31 was not found
useradd -f: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 62 Failed
useradd -p :Create a new user. - Reference the Commands and Utilities chapter in the Specification
User vsx32 was not found
useradd -p: FAIL
/tset/LSB.usersgroups/commands/misc/T.misc 63 Unresolved
userdel :Delete a user account. - Reference the Commands and Utilities chapter in the Specification
userdel UNRESOLVED: Can not add a test user
/tset/LSB.usersgroups/commands/misc/T.misc 64 Unresolved
usermod -d :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -d UNRESOLVED: Can not add a test user vsx34
/tset/LSB.usersgroups/commands/misc/T.misc 65 Unresolved
usermod -c :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -c UNRESOLVED: Can not add a test user vsx35
/tset/LSB.usersgroups/commands/misc/T.misc 66 Unresolved
usermod -g :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -g UNRESOLVED: Can not add a test user vsx36
/tset/LSB.usersgroups/commands/misc/T.misc 67 Unresolved
usermod -f :Modify a user account. - Reference the Commands and Utilities chapter in the Specification
usermod -f UNRESOLVED: Un-able to add a test user vsx37
/tset/LSB.usersgroups/commands/misc/T.misc 68 Unresolved
userdel -r: remove user plus his/her home dir. - Reference the Commands and Utilities chapter in the Specification
UNRESOLVED: un-able to add a test user: useradd -d /home/tmp vsx38
/tset/LSB.usersgroups/commands/misc/T.misc 69 Unresolved
usermod -l: change login name. - Reference the Commands and Utilities chapter in the Specification
UNRESOLVED: un-able to add a test user: vsx39
/tset/LSB.usersgroups/commands/misc/T.misc 70 Unresolved
usermod -G : change supplementary groups. - Reference the Commands and Utilities chapter in the Specification
UNRESOLVED: un-able to add a test user: vsx40
/tset/LSB.usersgroups/commands/misc/T.misc 71 Failed
useradd -G : add new user with specified supplementary groups. - Reference the Commands and Utilities chapter in the Specification
useradd -G : FAILED.
/tset/LSB.usersgroups/commands/misc/T.misc 72 Failed
useradd -m -k : add a user with specified home dir. - Reference the Commands and Utilities chapter in the Specification
useradd -m -k FAILED
WARNING: un-able to remove an added test user and/or his/her home_dir.
/tset/LSB.usersgroups/commands/misc/T.misc 73 Failed
useradd -m: add a user with home dir same as /etc/skel - Reference the Commands and Utilities chapter in the Specification
useradd -m FAILED
WARNING: un-able to remove an added test user and/or his/her home_dir.
/tset/lsb_release/testcases/lsb_release/lsb_release-tc 2 Failed
Reference 15.2, The lsb_release command should return the version of LSB against which the distribution is compliant.
Spec reference: 15.2. Command Behavior
Expecting at least 2 core-3.2 results from lsb_release
exit code 1 returned, expected 0
[edit] Desktop-T2C Tests v 3.1.95-3
/atk-t2c/tests/AtkHyperlink/AtkHyperlink 19 Failed (quelled) Known problem (waived)
Target interface(s):
start_index
--------
Property "start-index" has value 20,
but function atk_hyperlink_get_start_index returned 10.
Value of property should coincide with value returned by atk_hyperlink_get_start_index.
Requirement failed:
{start_index.05}
Property means the start index of the AtkHyperlink object.
Comment:
This failure occurs due to the following problem:
Incorrect registration of the "start-index" property for AtkHyperlink.
/atk-t2c/tests/AtkObject_properties/AtkObject_properties 4 Failed (quelled) Known problem (waived)
Target interface(s):
accessible_role
--------
Checked requirements: accessible_role.01
Checked requirements: accessible_role.02
Checked requirements: accessible_role.03
Checked requirements: accessible_role.05
Initial value of the role is 66, but should be 0.
Value of the property should be 0 just after creation of an object.
Requirement failed:
{accessible_role.05}
Default value: 0
Comment:
This failure occurs due to the following problem:
"accessible-role" - invalid default value.
/atk-t2c/tests/AtkObject_properties/AtkObject_properties 16 Failed (quelled) Known problem (waived)
Target interface(s):
accessible_value
--------
Value = 10.000000 was passed to function g_object_set().
But after call of the function g_object_get,
value, address of which was passed to it, contains 0.000000.
g_object_get() should return same value, as set by g_object_set().
Requirement failed:
{accessible_value.02}
Type of property should be gdouble. Property should be readable and writable.
Comment:
This failure occurs due to the following problem:
Spurious gdouble in "accesible-value" property of an AtkObject.
/atk-t2c/tests/AtkObject_relation/AtkObject_relation 6 Failed (quelled) Known problem (waived)
Target interface(s):
atk_object_remove_relationship
--------
Checked requirements: app.atk_object_remove_relationship.03
Checked requirements: app.atk_object_remove_relationship.04
Checked requirements: app.atk_object_remove_relationship.05
Checked requirements: atk_object_remove_relationship.02
Checked requirements: atk_object_remove_relationship.01
Before call of the function there were 5 relationships(total).
After call - 3.
Function shouldn't delete other relationships
Requirement failed:
{atk_object_remove_relationship.01}
Removes a relationship of the specified type with the specified target.
Comment:
This failure occurs due to the following problem:
atk_object_remove_relationship can remove more relationships than it should.
/atk-t2c/tests/AtkObject_relation/AtkObject_relation 7 Failed (quelled) Known problem (waived)
Target interface(s):
atk_object_remove_relationship
--------
Checked requirements: app.atk_object_remove_relationship.03
Checked requirements: app.atk_object_remove_relationship.04
Checked requirements: app.atk_object_remove_relationship.05
Checked requirements: atk_object_remove_relationship.02
Checked requirements: atk_object_remove_relationship.01
Before call of the function there were 5 relationships(total).
After call - 3.
Function shouldn't delete other relationships
Requirement failed:
{atk_object_remove_relationship.01}
Removes a relationship of the specified type with the specified target.
Comment:
This failure occurs due to the following problem:
atk_object_remove_relationship can remove more relationships than it should.
/atk-t2c/tests/AtkObject_signals/AtkObject_signals 16 Failed (quelled) Known problem (waived)
Target interface(s):
property_change
--------
Property 'accessible-role' has changed it's value from 66 to 2
The signal "property-change" should be emitted when an object's property value changes.
Requirement failed:
{property_change.04}
The signal "property-change" should be emitted when an object's property value changes.
Comment:
This failure occurs due to the following problem:
"property-change" signal is not always emitted when the value of the "accessible-role" property changes.
/atk-t2c/tests/AtkRelationSet/AtkRelationSet 10 Failed (quelled) Known problem (waived)
Target interface(s):
atk_relation_set_add
--------
Checked requirements: app.atk_relation_set_add.02
Checked requirements: app.atk_relation_set_add.03
Initial set contained the following relations:
0x806d320,
0x806d308.
And the function was called with relation = 0x806d320,
which was in the set
After call of the function the set is expected to contain the following:
0x806d320,
0x806d308.
And it contains the following:
0x806d320,
0x806d320,
0x806d308.
Function should not add a relation to the set if the relation is already present in it.
Requirement failed:
{atk_relation_set_add.01}
Add a new relation to the current relation set if it is not already present.
Comment:
This failure occurs due to the following problem:
atk_relation_set_add always adds relation to the set.
/atk-t2c/tests/AtkStateSet/AtkStateSet 24 Failed (quelled) Known problem (waived)
Target interface(s):
atk_state_set_or_sets
--------
When called for empty sets, the function should return NULL.
But it returned 0x8069a48.
Requirement failed:
{atk_state_set_or_sets.01.02}
returns NULL if the union is empty.
Comment:
This failure occurs due to the following problem:
atk_state_set_or_sets returns an empty set rather than NULL.
/atk-t2c/tests/AtkUtils/AtkUtils 5 Failed (quelled) Known problem (waived)
Target interface(s):
atk_add_global_event_listener
--------
Function returns 4294967295 (-1)
Function should return 0 on failure.
Requirement failed:
{atk_add_global_event_listener.02.02}
Returns 0 on failure.
Comment:
This failure occurs due to the following problem:
atk_add_global_event_listener, atk_add_key_event_listener return incorrect value in case of error.
/atk-t2c/tests/AtkUtils/AtkUtils 8 Failed (quelled) Known problem (waived)
Target interface(s):
atk_add_key_event_listener
--------
Function returns 4294967295 (-1)
The function should return 0 on failure.
Requirement failed:
{atk_add_key_event_listener.03.02}
Returns 0 on failure.
Comment:
This failure occurs due to the following problem:
atk_add_global_event_listener, atk_add_key_event_listener return incorrect value in case of error.
/glib-t2c/tests/glib_AsyncQueue/glib_AsyncQueue 5 Time expired Known problem
Target interface(s):
g_async_queue_pop
--------
pop_test(): after g_cond_signal()
Child process timed out.
Comment:
This problem was detected on Mandriva 2008 Free and Fedora Core 8.
The main thread of the test hangs in g_cond_wait(). Meanwhile, the other thread calls g_cond_signal() to wake up the main thread but it seems to have no effect.
/glib-t2c/tests/glib_file_utilities/glib_file_utilities 32 Failed
Target interface(s):
g_file_open_tmp
--------
actual name used is not returned
Requirement failed:
{g_file_open_tmp.06}
The actual name used is returned in name_used if non-NULL
/glib-t2c/tests/glib_file_utilities/glib_file_utilities 33 Failed
Target interface(s):
g_file_open_tmp
--------
actual name used is not returned
Requirement failed:
{g_file_open_tmp.06}
The actual name used is returned in name_used if non-NULL
/glib-t2c/tests/glib_key_parser/glib_key_parser 6 Unresolved
Target interface(s):
g_key_file_load_from_file
--------
FAILED CHECK in glib_key_parser.c, line 752
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 7 Unresolved
Target interface(s):
g_key_file_load_from_file
--------
FAILED CHECK in glib_key_parser.c, line 901
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 8 Unresolved
Target interface(s):
g_key_file_load_from_file
--------
FAILED CHECK in glib_key_parser.c, line 1050
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 9 Unresolved
Target interface(s):
g_key_file_load_from_file
--------
FAILED CHECK in glib_key_parser.c, line 1199
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 14 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 1881
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 15 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 2072
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 16 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 2263
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 17 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 2454
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 18 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 2645
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 19 Unresolved
Target interface(s):
g_key_file_load_from_data_dirs
--------
FAILED CHECK in glib_key_parser.c, line 2836
comment: Startup failed, aborting the test case.
Error: Test purpose error.
/glib-t2c/tests/glib_key_parser/glib_key_parser 36 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_has_key
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 5038
comment: [g_key_file_has_key: assertion `group_name != NULL' failed]
Checked requirements: g_key_file_has_key.03
Returned value should be TRUE.
At least one of the following requirements failed:
{g_key_file_has_key.02}
If group_name is NULL, the start group is used.
{g_key_file_has_key.01.01}
Returns TRUE if key is a part of group_name.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation "g_key_file_has_key".
/glib-t2c/tests/glib_key_parser/glib_key_parser 60 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_boolean
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 9100
comment: [g_key_file_get_boolean: assertion `group_name != NULL' failed]
returned value is FALSE, should be TRUE
At least one of the following requirements failed:
{g_key_file_get_boolean.04}
If group_name is NULL, the start group is used.
{g_key_file_get_boolean.01}
Returns the value associated with key under group_name as a boolean.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_get_boolean".
/glib-t2c/tests/glib_key_parser/glib_key_parser 64 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_integer
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 9608
comment: [g_key_file_get_integer: assertion `group_name != NULL' failed]
Returned incorrect value.
At least one of the following requirements failed:
{g_key_file_get_integer.04}
If group_name is NULL, the start_group is used.
{g_key_file_get_integer.01}
Returns the value associated with key under group_name as an integer.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_get_integer".
/glib-t2c/tests/glib_key_parser/glib_key_parser 76 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_locale_string_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 12403
comment: [g_key_file_get_locale_string_list: assertion `group_name != NULL' failed]
Returned NULL.
At least one of the following requirements failed:
{g_key_file_get_locale_string_list.07}
The default list separator is ';'.
{g_key_file_get_locale_string_list.01}
Returns the values associated with key under group_name translated in the given locale if available.
{g_key_file_get_locale_string_list.08}
If group_name is NULL, then the start group is used.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_get_locale_string_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 83 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_boolean_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 14163
comment: [g_key_file_get_boolean_list: assertion `group_name != NULL' failed]
Returned value is NULL.
At least one of the following requirements failed:
{g_key_file_get_boolean_list.06}
If group_name is NULL, the start_group is used.
{g_key_file_get_boolean_list.05}
The default list separator is ';'.
{g_key_file_get_boolean_list.01}
Returns the values associated with key under group_name as booleans.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_get_boolean_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 87 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_integer_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 14934
comment: [g_key_file_get_integer_list: assertion `group_name != NULL' failed]
Returned value is NULL.
At least one of the following requirements failed:
{g_key_file_get_integer_list.05}
The default list separator is ';'.
{g_key_file_get_integer_list.04}
the number of integers returned
{g_key_file_get_integer_list.06}
If group_name is NULL, the start group is used.
{g_key_file_get_integer_list.01}
Returns the values associated with key under group_name as integers.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_get_integer_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 88 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_get_comment.04
get comment failed: expected value = "Fourth Comment", returned value = "Fourth Comment
"
Requirement failed:
{g_key_file_get_comment.01}
Retrieves a comment above key from group_name.
Comment:
This failure occurs due to the following problem:
The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
/glib-t2c/tests/glib_key_parser/glib_key_parser 89 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_get_comment.04
get comment from above group failed: expected value = "Third Comment", returned value = "Third Comment
"
Requirement failed:
{g_key_file_get_comment.02}
If key is NULL then comment will be read from above group_name.
Comment:
This failure occurs due to the following problem:
The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
/glib-t2c/tests/glib_key_parser/glib_key_parser 90 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_get_comment.04
get comment from above first group failed: expected value = "First Comment", returned value = "First Comment
"
Requirement failed:
{g_key_file_get_comment.03}
If both key and group_name are NULL, then comment will be read from above the first group in the file.
Comment:
This failure occurs due to the following problem:
The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
/glib-t2c/tests/glib_key_parser/glib_key_parser 101 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_boolean
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 16864
comment: [g_key_file_get_boolean: assertion `group_name != NULL' failed]
Set boolean value = TRUE, while Get FALSE.
At least one of the following requirements failed:
{g_key_file_set_boolean.03}
If group_name is NULL, the start group is used.
{g_key_file_get_boolean.04}
If group_name is NULL, the start group is used.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_set_boolean".
/glib-t2c/tests/glib_key_parser/glib_key_parser 104 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_integer
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 17195
comment: [g_key_file_set_value: assertion `g_key_file_is_group_name (group_name)' failed]
Set integer value = "15", while Get integer = "-1".
At least one of the following requirements failed:
{g_key_file_set_integer.03}
If group_name is NULL, the start group is used.
{g_key_file_get_integer.04}
If group_name is NULL, the start_group is used.
{g_key_file_set_integer.01}
Associates a new integer value with key under group_name.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation "g_key_file_set_integer".
/glib-t2c/tests/glib_key_parser/glib_key_parser 110 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_locale_string_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 18247
comment: [g_key_file_set_value: assertion `g_key_file_is_group_name (group_name)' failed]
Get returns NULL for Key = "Welcome" and Locale = "en" of the Group = "(null)", while Set filled the list.
At least one of the following requirements failed:
{g_key_file_set_locale_string_list.03}
If group_name is NULL, the start group is used.
{g_key_file_get_locale_string_list.07}
The default list separator is ';'.
{g_key_file_get_locale_string_list.08}
If group_name is NULL, then the start group is used.
{g_key_file_set_locale_string_list.01}
Associates a list of string values for key and locale under group_name.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation "g_key_file_set_locale_string_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 113 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_boolean_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 18764
comment: [g_key_file_set_value: assertion `g_key_file_is_group_name (group_name)' failed]
Get returns NULL for Key = "BooleanList" of the Group = "(null)", while Set filled the list.
At least one of the following requirements failed:
{g_key_file_set_boolean_list.03}
If group_name is NULL, the start_group is used.
{g_key_file_get_boolean_list.06}
If group_name is NULL, the start_group is used.
{g_key_file_set_boolean_list.01}
Associates a list of boolean values with key under group_name.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation of the interface "g_key_file_set_boolean_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 116 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_integer_list
--------
Checked requirements: g_key_file_new.01
Error reported in glib_key_parser.c, line 19338
comment: [g_key_file_set_value: assertion `g_key_file_is_group_name (group_name)' failed]
Get returns NULL for Key = "Numbers" of the Group = "First Group", while Set filled the list.
At least one of the following requirements failed:
{g_key_file_set_integer_list.03}
If group_name is NULL the start group is used.
{g_key_file_get_integer_list.06}
If group_name is NULL, the start group is used.
{g_key_file_set_integer_list.01}
Associates a list of integer values with key under group_name.
Comment:
This failure occurs due to the following problem:
Inconsistency between standard and implementation "g_key_file_set_integer_list".
/glib-t2c/tests/glib_key_parser/glib_key_parser 117 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_comment
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_set_comment.04
Trying to set comment: set comment = "comment 1" get comment = "comment 1
"
At least one of the following requirements failed:
{g_key_file_set_comment.01}
Places a comment above key from group_name.
{g_key_file_get_comment.01}
Retrieves a comment above key from group_name.
Comment:
This failure occurs due to the following problem:
The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
/glib-t2c/tests/glib_key_parser/glib_key_parser 118 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_comment
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_set_comment.04
Trying to set comment above the group: set comment = "comment 2" get comment = "#comment 2"
At least one of the following requirements failed:
{g_key_file_set_comment.02}
If key is NULL then comment will be written above group_name.
{g_key_file_get_comment.02}
If key is NULL then comment will be read from above group_name.
Comment:
This failure occurs due to the following problem:
The "g_key_file_set_comment" interface prepends '#' character to the comment.
/glib-t2c/tests/glib_key_parser/glib_key_parser 119 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_set_comment
g_key_file_get_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_set_comment.04
Trying to set comment above the first group: set comment = "comment 3" get comment = "comment 3
"
At least one of the following requirements failed:
{g_key_file_set_comment.03}
If both key and group_name are NULL, then comment will be written above the first group in the file.
{g_key_file_get_comment.03}
If both key and group_name are NULL, then comment will be read from above the first group in the file.
Comment:
This failure occurs due to the following problem:
The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
/glib-t2c/tests/glib_key_parser/glib_key_parser 125 Failed (quelled) Known problem (waived)
Target interface(s):
g_key_file_remove_comment
--------
Checked requirements: g_key_file_new.01
Checked requirements: g_key_file_remove_comment.04
Comment above the Group = "Second Group" not removed , Get comment should be NULL, now is "Third Comment
".
Requirement failed:
{g_key_file_remove_comment.02}
If key is NULL then comment will be removed above group_name.
Comment:
This failure occurs due to the following problem:
Invocation of the interface "g_key_file_remove_comment" does not remove comment in specific case.
/glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 46 Failed (quelled) Known problem (waived)
Target interface(s):
g_main_context_check
--------
g_main_context_check: sources with higher numerical priority than specified are being checked.
Requirement failed:
{g_main_context_check.01}
max_priority : the maximum numerical priority of sources to check
Comment:
This failure occurs due to the following problem:
The "g_main_context_check" interface ignores it's "max_priority" parameter.
/glib-t2c/tests/glib_memchunks/glib_memchunks 9 Failed (quelled) Known problem (waived)
Target interface(s):
g_mem_chunk_print
g_mem_chunk_info
--------
No print in log or GMemChunk name not found in message
Requirement failed:
{g_mem_chunk_info.01}
Outputs debugging information for all GMemChunk objects currently in use. It outputs the number of GMemChunk objects currently allocated, and calls g_mem_chunk_print() to output information on each one.
Comment:
Memory chunks are deprecated since glib version 2.10.
/glib-t2c/tests/glib_memchunks/glib_memchunks 10 Failed (quelled) Known problem (waived)
Target interface(s):
g_mem_chunk_print
g_mem_chunk_info
--------
No print in log or GMemChunk name not found in message
Requirement failed:
{g_mem_chunk_print.01}
Outputs debugging information for a GMemChunk. It outputs the name of the GMemChunk (set with g_mem_chunk_new()), the number of bytes used, and the number of blocks of memory allocated.
Comment:
Memory chunks are deprecated since glib version 2.10.
/gmodule-t2c/tests/gmodule/gmodule 11 Failed (quelled) Known problem (waived)
Target interface(s):
g_module_open
--------
g_module_open cannot open module '/opt/lsb/test/desktop-t2c/gmodule-t2c/testdata/gmodule/open/la1/test.la'.
Requirement failed:
{g_module_open.01.01}
First of all g_module_open() tries to open file_name as a module.
Comment:
This failure occurs due to the following problem:
g_module_open fails to open modules with ".la" extension.
Detailed description of this problem is available here.
/gmodule-t2c/tests/gmodule/gmodule 23 Failed (quelled) Known problem (waived)
Target interface(s):
g_module_error
--------
A string meaning that no error occured is '(null)', current error string is '(null)'.
Error occurs in g_module_open, but g_module_error doesn't reveal it.
Requirement failed:
{g_module_error.01}
Returns :a string describing the last module error.
Comment:
This failure occurs due to the following problem:
g_module_error returns NULL after g_module_open has failed to open a module with ".la" extension.
[edit] LSB desktop test suites
[edit] Desktop::GTK Tests v 3.1.95-5
/tests/functions/GdkImages/GdkImages 2 Failed test case: /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/26415aa/tests/functions/GdkImages/GdkImages, TP number: 2 GdkImages.c, line 127: gdk_image_new: it's not a GDK_TYPE_IMAGE /tests/functions/GtkWindow/GtkWindow 127 Failed test case: /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/26415aa/tests/functions/GtkWindow/GtkWindow, TP number: 127 GtkWindow.c, line 9412: toplevel_list_length = 19, toplevel_count = 18 /tests/functions/GtkWindow/GtkWindow 128 Failed test case: /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/26415aa/tests/functions/GtkWindow/GtkWindow, TP number: 128 GtkWindow.c, line 9517: toplevel_list_length = 16, toplevel_count = 15 /tests/functions/GtkWindow/GtkWindow 129 Failed test case: /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/26415aa/tests/functions/GtkWindow/GtkWindow, TP number: 129 GtkWindow.c, line 9622: toplevel_list_length = 31, toplevel_count = 30 /tests/functions/GtkToolbar/GtkToolbar 15 Failed test case: /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/26415aa/tests/functions/GtkToolbar/GtkToolbar, TP number: 15 GtkToolbar.c, line 934: tooltips is 1, should be 0
[edit] Desktop::Qt4 Tests v 3.1.95-5
tst_QFont_setFontRaw 7 Failed
Compared values are not the same Actual (QFontInfo(f).family().left(5).toLower()): liber Expected (QString("fixed")): fixed
tst_QIcon_actualSize 1 Failed
Compared values are not the same
tst_QIcon_actualSize2 2 Failed
Compared values are not the same
tst_QIcon_isNull 3 Failed
(none)
tst_QTextDocumentFragment_html_qt3RichtextWhitespaceMode 173 Failed
(none)
tst_QTreeView_disabledButCheckable 54 Failed
Compared values are not the same
[edit] Perl Tests v 3.1.95-3
../lib/CGI/t/function.t 246 Failed FAILED tests 25-27 Failed 3/31 tests, 90.32% okay ../lib/CGI/t/util.t 254 Failed FAILED test 58 Failed 1/59 tests, 98.31% okay ../lib/ExtUtils/t/Constant.t 294 Failed FAILED tests 3-272 Failed 270/272 tests, 0.74% okay ../lib/ExtUtils/t/Embed.t 295 Failed FAILED tests 1-9 Failed 9/9 tests, 0.00% okay ../lib/Net/Ping/t/200_ping_tcp.t 473 Failed FAILED test 6 Failed 1/13 tests, 92.31% okay ../lib/Net/Ping/t/400_ping_syn.t 475 Failed FAILED test 19 Failed 1/19 tests, 94.74% okay ../lib/Net/Ping/t/410_syn_host.t 476 Failed FAILED test 13 Failed 1/19 tests, 94.74% okay ../lib/Net/t/hostname.t 479 Failed FAILED test 1 Failed 1/2 tests, 50.00% okay ../lib/Pod/Perldoc/t/01_about_verbose.t 493 Failed FAILED tests 1-2 Failed 2/2 tests, 0.00% okay ../lib/Pod/Perldoc/t/checkerbasic.t 494 Failed FAILED test 2 Failed 1/2 tests, 50.00% okay ../lib/Pod/Perldoc/t/perldocbasic.t 495 Failed FAILED tests 2-3 Failed 2/3 tests, 33.33% okay ../lib/Pod/Perldoc/t/textbasic.t 496 Failed FAILED test 2 Failed 1/2 tests, 50.00% okay
[edit] Python Runtime Tests v 3.1.95-3
/usr/bin/python 87 Failed Traceback (most recent call last): File "/opt/lsb/test/python/Lib25/test/test_socket.py", line 456, in testSockName my_ip_addr = socket.gethostbyname(socket.gethostname()) gaierror: (-2, 'Name or service not known')
[edit] X11 Tests (XTS5) v 5.1.5-4
/tset/Xproto/chngkybrdm/Test 3 Unresolved VSW5TESTSUITE PURPOSE 3 Assertion ChangeKeyboardMapping-3.(B) When a client sends an invalid ChangeKeyboardMapping protocol request to the X server, in which the length field of the request exceeds the maximum length accepted by the X server, then the X server sends back a BadLength error to the client. Reason for omission: There is no known portable test method for this assertion METH: Call library function testfunc() to do the following: METH: Open a connection to the X server using native byte sex. METH: Send an invalid ChangeKeyboardMapping protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. METH: Open a connection to the X server using reversed byte sex. METH: Send an invalid ChangeKeyboardMapping protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. TRACE: About to test with Native byte-sex (MSB) TRACE: client 0 sent default GetKeyboardMapping request TRACE: client 0 received GetKeyboardMapping reply INFO: Processing a big request child process was terminated by signal 13 (SIGPIPE) CHECK: ChangeKeyboardMapping-3 1, line 327 /tset/Xproto/frclrmp/Test 3 Unresolved VSW5TESTSUITE PURPOSE 3 Assertion FreeColormap-3.(B) When a client sends an invalid FreeColormap protocol request to the X server, in which the length field of the request exceeds the maximum length accepted by the X server, then the X server sends back a BadLength error to the client. Reason for omission: There is no known portable test method for this assertion METH: Call library function testfunc() to do the following: METH: Open a connection to the X server using native byte sex. METH: Send an invalid FreeColormap protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. METH: Open a connection to the X server using reversed byte sex. METH: Send an invalid FreeColormap protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. TRACE: About to test with Native byte-sex (MSB) TRACE: client 0 sent default CreateWindow for window 4194304 TRACE: client 0 sent CreateColormap for colormap 4194305 INFO: Processing a big request child process was terminated by signal 13 (SIGPIPE) CHECK: FreeColormap-3 1, line 327 /tset/Xproto/lstfntswth/Test 3 Unresolved VSW5TESTSUITE PURPOSE 3 Assertion ListFontsWithInfo-3.(B) When a client sends an invalid ListFontsWithInfo protocol request to the X server, in which the length field of the request exceeds the maximum length accepted by the X server, then the X server sends back a BadLength error to the client. Reason for omission: There is no known portable test method for this assertion METH: Call library function testfunc() to do the following: METH: Open a connection to the X server using native byte sex. METH: Send an invalid ListFontsWithInfo protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. METH: Open a connection to the X server using reversed byte sex. METH: Send an invalid ListFontsWithInfo protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. TRACE: About to test with Native byte-sex (MSB) INFO: Processing a big request child process was terminated by signal 13 (SIGPIPE) CHECK: ListFontsWithInfo-3 1, line 327 /tset/Xproto/lsthsts/Test 3 Unresolved VSW5TESTSUITE PURPOSE 3 Assertion ListHosts-3.(B) When a client sends an invalid ListHosts protocol request to the X server, in which the length field of the request exceeds the maximum length accepted by the X server, then the X server sends back a BadLength error to the client. Reason for omission: There is no known portable test method for this assertion METH: Call library function testfunc() to do the following: METH: Open a connection to the X server using native byte sex. METH: Send an invalid ListHosts protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. METH: Open a connection to the X server using reversed byte sex. METH: Send an invalid ListHosts protocol request to the X server with length METH: one greater than the maximum length accepted by the server. METH: Verify that the X server sends back a BadLength error. TRACE: About to test with Native byte-sex (MSB) INFO: Processing a big request child process was terminated by signal 13 (SIGPIPE) CHECK: ListHosts-3 1, line 327 /tset/Xlib3/vndrrls/Test 1 FIP [?] VSW5TESTSUITE PURPOSE 1 Assertion XVendorRelease-1.(B) A call to XVendorRelease returns a number related to a vendor's release of the X server. Reason for omission: There is no known portable test method for this assertion METH: Obtain the value of the vendor's X server release using XVendorRelease. REPORT: XVendorRelease() returned 70200000 instead of 40201001. /tset/Xlib3/srvrvndr/Test 1 FIP (quelled) Correct answer for X.Org-based X server VSW5TESTSUITE PURPOSE 1 Assertion XServerVendor-1.(A) A call to XServerVendor returns a pointer to a null-terminated string that identifies the owner of the X server implementation. METH: Obtain the server vendor string using XServerVendor. METH: Verify that the value is that given in parameter XT_SERVER_VENDOR. REPORT: XServerVendor() returns incorrect value for server vendor string REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation" REPORT: Observed value "The X.Org Foundation" Comment: This answer is correct provided that the X server is X.Org-based. /tset/Xlib3/vndrrls/MTest 1 FIP [?] VSW5TESTSUITE PURPOSE 1 Assertion VendorRelease-1.(B) A call to VendorRelease returns a number related to a vendor's release of the X server. Reason for omission: There is no known portable test method for this assertion METH: Obtain the value of the vendor's X server release using VendorRelease. REPORT: VendorRelease() returned 70200000 instead of 40201001. /tset/Xlib3/srvrvndr/MTest 1 FIP (quelled) Correct answer for X.Org-based X server VSW5TESTSUITE PURPOSE 1 Assertion ServerVendor-1.(A) A call to ServerVendor returns a pointer to a null-terminated string that identifies the owner of the X server implementation. METH: Obtain the server vendor string using ServerVendor. METH: Verify that the value is that given in parameter XT_SERVER_VENDOR. REPORT: ServerVendor() returns incorrect value for server vendor string REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation" REPORT: Observed value "The X.Org Foundation" Comment: This answer is correct provided that the X server is X.Org-based. /tset/Xlib9/drwarc/Test 42 Warning VSW5TESTSUITE PURPOSE 42 Assertion XDrawArc-42.(A) When the line_style is LineOnOffDash, then cap_style applies to all internal ends of the individual dashes, except CapNotLast is treated as CapButt. METH: Set graphics coordinates for dashed lines METH: (includes horizontal and vertical cases, METH: and includes joins and caps where relevant). METH: Set the line_style of the GC to LineOnOffDash using XChangeGC. METH: Set the dash_list of the GC to using XSetDashes. METH: For cap_style CapNotLast, CapButt, CapProjecting, CapRound: METH: Set the cap_style of the GC using XChangeGC. METH: Draw paths. METH: Pixmap verify. METH: Clear drawable. TRACE: --- Running test with visual class TrueColor, depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArc-42 1, line 3626 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArc-42 2, line 3626 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArc-42 3, line 3626 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 4 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0000.err for results CHECK: XDrawArc-42 4, line 3626 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArc-42 5, line 3626 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArc-42 6, line 3626 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArc-42 7, line 3626 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArc-42 8, line 3626 TRACE: --- Running test with visual class DirectColor, depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArc-42 9, line 3626 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArc-42 10, line 3626 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArc-42 11, line 3626 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 4 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0001.err for results CHECK: XDrawArc-42 12, line 3626 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArc-42 13, line 3626 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArc-42 14, line 3626 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArc-42 15, line 3626 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArc-42 16, line 3626 TRACE: --- Running test with pixmap depth 1 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArc-42 17, line 3626 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArc-42 18, line 3626 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArc-42 19, line 3626 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 4 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0002.err for results CHECK: XDrawArc-42 20, line 3626 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArc-42 21, line 3626 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArc-42 22, line 3626 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArc-42 23, line 3626 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArc-42 24, line 3626 TRACE: --- Running test with pixmap depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArc-42 25, line 3626 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArc-42 26, line 3626 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArc-42 27, line 3626 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 4 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0003.err for results CHECK: XDrawArc-42 28, line 3626 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArc-42 29, line 3626 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArc-42 30, line 3626 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArc-42 31, line 3626 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArc-42 32, line 3626 TRACE: --- Running test with pixmap depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArc-42 33, line 3626 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArc-42 34, line 3626 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArc-42 35, line 3626 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 4 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0004.err for results CHECK: XDrawArc-42 36, line 3626 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArc-42 37, line 3626 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArc-42 38, line 3626 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArc-42 39, line 3626 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArc-42 40, line 3626 /tset/Xlib9/drwarc/Test 63 Warning VSW5TESTSUITE PURPOSE 63 Assertion XDrawArc-63.(A) When the cap_style is CapNotLast and the line_width is zero (0), then this is equivalent to CapButt except that the final endpoint is not drawn. METH: Draw line with CapButt. METH: Set GC component function to GXxor. METH: Draw line with CapNotLast. METH: Verify that only the final end point is set. TRACE: --- Running test with visual class TrueColor, depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0005.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArc-63 1, line 4622 TRACE: --- Running test with visual class DirectColor, depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0006.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArc-63 2, line 4622 TRACE: --- Running test with pixmap depth 1 REPORT: Pixel mismatch in image REPORT: See file Err0007.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArc-63 3, line 4622 TRACE: --- Running test with pixmap depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0008.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArc-63 4, line 4622 TRACE: --- Running test with pixmap depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0009.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArc-63 5, line 4622 /tset/Xlib9/drwarc/Test 66 Warning VSW5TESTSUITE PURPOSE 66 Assertion XDrawArc-66.(A) When the cap_style is CapRound and line-width is not zero, then the line has a circular arc, with the diamater equal to the line_width, centred on the endpoint. METH: For a variety of line widths. METH: Draw line with CapRound. METH: Pixmap verify. TRACE: --- Running test with visual class TrueColor, depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArc-66 1, line 4750 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0010.err for results CHECK: XDrawArc-66 2, line 4750 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0011.err for results CHECK: XDrawArc-66 3, line 4750 TRACE: Trying CapRound with width of 5 CHECK: XDrawArc-66 4, line 4750 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0012.err for results CHECK: XDrawArc-66 5, line 4750 TRACE: Trying CapRound with width of 11 CHECK: XDrawArc-66 6, line 4750 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0013.err for results CHECK: XDrawArc-66 7, line 4750 TRACE: Trying CapRound with width of 41 CHECK: XDrawArc-66 8, line 4750 TRACE: --- Running test with visual class DirectColor, depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArc-66 9, line 4750 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0014.err for results CHECK: XDrawArc-66 10, line 4750 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0015.err for results CHECK: XDrawArc-66 11, line 4750 TRACE: Trying CapRound with width of 5 CHECK: XDrawArc-66 12, line 4750 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0016.err for results CHECK: XDrawArc-66 13, line 4750 TRACE: Trying CapRound with width of 11 CHECK: XDrawArc-66 14, line 4750 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0017.err for results CHECK: XDrawArc-66 15, line 4750 TRACE: Trying CapRound with width of 41 CHECK: XDrawArc-66 16, line 4750 TRACE: --- Running test with pixmap depth 1 TRACE: Trying CapRound with width of 1 CHECK: XDrawArc-66 17, line 4750 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0018.err for results CHECK: XDrawArc-66 18, line 4750 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0019.err for results CHECK: XDrawArc-66 19, line 4750 TRACE: Trying CapRound with width of 5 CHECK: XDrawArc-66 20, line 4750 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0020.err for results CHECK: XDrawArc-66 21, line 4750 TRACE: Trying CapRound with width of 11 CHECK: XDrawArc-66 22, line 4750 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0021.err for results CHECK: XDrawArc-66 23, line 4750 TRACE: Trying CapRound with width of 41 CHECK: XDrawArc-66 24, line 4750 TRACE: --- Running test with pixmap depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArc-66 25, line 4750 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0022.err for results CHECK: XDrawArc-66 26, line 4750 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0023.err for results CHECK: XDrawArc-66 27, line 4750 TRACE: Trying CapRound with width of 5 CHECK: XDrawArc-66 28, line 4750 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0024.err for results CHECK: XDrawArc-66 29, line 4750 TRACE: Trying CapRound with width of 11 CHECK: XDrawArc-66 30, line 4750 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0025.err for results CHECK: XDrawArc-66 31, line 4750 TRACE: Trying CapRound with width of 41 CHECK: XDrawArc-66 32, line 4750 TRACE: --- Running test with pixmap depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArc-66 33, line 4750 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0026.err for results CHECK: XDrawArc-66 34, line 4750 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0027.err for results CHECK: XDrawArc-66 35, line 4750 TRACE: Trying CapRound with width of 5 CHECK: XDrawArc-66 36, line 4750 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0028.err for results CHECK: XDrawArc-66 37, line 4750 TRACE: Trying CapRound with width of 11 CHECK: XDrawArc-66 38, line 4750 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0029.err for results CHECK: XDrawArc-66 39, line 4750 TRACE: Trying CapRound with width of 41 CHECK: XDrawArc-66 40, line 4750 /tset/Xlib9/drwarc/Test 73 Warning VSW5TESTSUITE PURPOSE 73 Assertion XDrawArc-73.(A) When a line has coincident endpoints (x1=x2, y1=y2), and the cap_style is applied to both endpoints and the line_width is not equal to zero and the cap_style is CapRound, then the closed path is a circle, centered at the endpoint, and with the diameter equal to the line-width. METH: Draw zero length line with CapRound. METH: Pixmap verify. TRACE: --- Running test with visual class TrueColor, depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0030.err for results CHECK: XDrawArc-73 1, line 5081 CHECK: XDrawArc-73 2, line 5081 TRACE: --- Running test with visual class DirectColor, depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0031.err for results CHECK: XDrawArc-73 3, line 5081 CHECK: XDrawArc-73 4, line 5081 TRACE: --- Running test with pixmap depth 1 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0032.err for results CHECK: XDrawArc-73 5, line 5081 CHECK: XDrawArc-73 6, line 5081 TRACE: --- Running test with pixmap depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0033.err for results CHECK: XDrawArc-73 7, line 5081 CHECK: XDrawArc-73 8, line 5081 TRACE: --- Running test with pixmap depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0034.err for results CHECK: XDrawArc-73 9, line 5081 CHECK: XDrawArc-73 10, line 5081 /tset/Xlib9/drwarcs/Test 45 Warning VSW5TESTSUITE PURPOSE 45 Assertion XDrawArcs-45.(A) When the line_style is LineOnOffDash, then cap_style applies to all internal ends of the individual dashes, except CapNotLast is treated as CapButt. METH: Set graphics coordinates for dashed lines METH: (includes horizontal and vertical cases, METH: and includes joins and caps where relevant). METH: Set the line_style of the GC to LineOnOffDash using XChangeGC. METH: Set the dash_list of the GC to using XSetDashes. METH: For cap_style CapNotLast, CapButt, CapProjecting, CapRound: METH: Set the cap_style of the GC using XChangeGC. METH: Draw paths. METH: Pixmap verify. METH: Clear drawable. TRACE: --- Running test with visual class TrueColor, depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArcs-45 1, line 3912 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArcs-45 2, line 3912 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArcs-45 3, line 3912 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 8 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0000.err for results CHECK: XDrawArcs-45 4, line 3912 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArcs-45 5, line 3912 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArcs-45 6, line 3912 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArcs-45 7, line 3912 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArcs-45 8, line 3912 TRACE: --- Running test with visual class DirectColor, depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArcs-45 9, line 3912 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArcs-45 10, line 3912 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArcs-45 11, line 3912 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 8 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0001.err for results CHECK: XDrawArcs-45 12, line 3912 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArcs-45 13, line 3912 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArcs-45 14, line 3912 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArcs-45 15, line 3912 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArcs-45 16, line 3912 TRACE: --- Running test with pixmap depth 1 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArcs-45 17, line 3912 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArcs-45 18, line 3912 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArcs-45 19, line 3912 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 8 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0002.err for results CHECK: XDrawArcs-45 20, line 3912 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArcs-45 21, line 3912 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArcs-45 22, line 3912 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArcs-45 23, line 3912 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArcs-45 24, line 3912 TRACE: --- Running test with pixmap depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArcs-45 25, line 3912 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArcs-45 26, line 3912 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArcs-45 27, line 3912 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 8 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0003.err for results CHECK: XDrawArcs-45 28, line 3912 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArcs-45 29, line 3912 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArcs-45 30, line 3912 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArcs-45 31, line 3912 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArcs-45 32, line 3912 TRACE: --- Running test with pixmap depth 16 TRACE: LineOnOffDash with CapNotLast width 4 CHECK: XDrawArcs-45 33, line 3912 TRACE: LineOnOffDash with CapButt width 4 CHECK: XDrawArcs-45 34, line 3912 TRACE: LineOnOffDash with CapProjecting width 4 CHECK: XDrawArcs-45 35, line 3912 TRACE: LineOnOffDash with CapRound width 4 REPORT: A total of 8 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0004.err for results CHECK: XDrawArcs-45 36, line 3912 TRACE: LineOnOffDash with CapNotLast width 5 CHECK: XDrawArcs-45 37, line 3912 TRACE: LineOnOffDash with CapButt width 5 CHECK: XDrawArcs-45 38, line 3912 TRACE: LineOnOffDash with CapProjecting width 5 CHECK: XDrawArcs-45 39, line 3912 TRACE: LineOnOffDash with CapRound width 5 CHECK: XDrawArcs-45 40, line 3912 /tset/Xlib9/drwarcs/Test 66 Warning VSW5TESTSUITE PURPOSE 66 Assertion XDrawArcs-66.(A) When the cap_style is CapNotLast and the line_width is zero (0), then this is equivalent to CapButt except that the final endpoint is not drawn. METH: Draw line with CapButt. METH: Set GC component function to GXxor. METH: Draw line with CapNotLast. METH: Verify that only the final end point is set. TRACE: --- Running test with visual class TrueColor, depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0005.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArcs-66 1, line 4908 TRACE: --- Running test with visual class DirectColor, depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0006.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArcs-66 2, line 4908 TRACE: --- Running test with pixmap depth 1 REPORT: Pixel mismatch in image REPORT: See file Err0007.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArcs-66 3, line 4908 TRACE: --- Running test with pixmap depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0008.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArcs-66 4, line 4908 TRACE: --- Running test with pixmap depth 16 REPORT: Pixel mismatch in image REPORT: See file Err0009.err for details REPORT: Cap style incorrect for thin line and CapNotLast CHECK: XDrawArcs-66 5, line 4908 /tset/Xlib9/drwarcs/Test 69 Warning VSW5TESTSUITE PURPOSE 69 Assertion XDrawArcs-69.(A) When the cap_style is CapRound and line-width is not zero, then the line has a circular arc, with the diamater equal to the line_width, centred on the endpoint. METH: For a variety of line widths. METH: Draw line with CapRound. METH: Pixmap verify. TRACE: --- Running test with visual class TrueColor, depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArcs-69 1, line 5036 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0010.err for results CHECK: XDrawArcs-69 2, line 5036 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0011.err for results CHECK: XDrawArcs-69 3, line 5036 TRACE: Trying CapRound with width of 5 CHECK: XDrawArcs-69 4, line 5036 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0012.err for results CHECK: XDrawArcs-69 5, line 5036 TRACE: Trying CapRound with width of 11 CHECK: XDrawArcs-69 6, line 5036 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0013.err for results CHECK: XDrawArcs-69 7, line 5036 TRACE: Trying CapRound with width of 41 CHECK: XDrawArcs-69 8, line 5036 TRACE: --- Running test with visual class DirectColor, depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArcs-69 9, line 5036 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0014.err for results CHECK: XDrawArcs-69 10, line 5036 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0015.err for results CHECK: XDrawArcs-69 11, line 5036 TRACE: Trying CapRound with width of 5 CHECK: XDrawArcs-69 12, line 5036 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0016.err for results CHECK: XDrawArcs-69 13, line 5036 TRACE: Trying CapRound with width of 11 CHECK: XDrawArcs-69 14, line 5036 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0017.err for results CHECK: XDrawArcs-69 15, line 5036 TRACE: Trying CapRound with width of 41 CHECK: XDrawArcs-69 16, line 5036 TRACE: --- Running test with pixmap depth 1 TRACE: Trying CapRound with width of 1 CHECK: XDrawArcs-69 17, line 5036 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0018.err for results CHECK: XDrawArcs-69 18, line 5036 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0019.err for results CHECK: XDrawArcs-69 19, line 5036 TRACE: Trying CapRound with width of 5 CHECK: XDrawArcs-69 20, line 5036 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0020.err for results CHECK: XDrawArcs-69 21, line 5036 TRACE: Trying CapRound with width of 11 CHECK: XDrawArcs-69 22, line 5036 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0021.err for results CHECK: XDrawArcs-69 23, line 5036 TRACE: Trying CapRound with width of 41 CHECK: XDrawArcs-69 24, line 5036 TRACE: --- Running test with pixmap depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArcs-69 25, line 5036 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0022.err for results CHECK: XDrawArcs-69 26, line 5036 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0023.err for results CHECK: XDrawArcs-69 27, line 5036 TRACE: Trying CapRound with width of 5 CHECK: XDrawArcs-69 28, line 5036 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0024.err for results CHECK: XDrawArcs-69 29, line 5036 TRACE: Trying CapRound with width of 11 CHECK: XDrawArcs-69 30, line 5036 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0025.err for results CHECK: XDrawArcs-69 31, line 5036 TRACE: Trying CapRound with width of 41 CHECK: XDrawArcs-69 32, line 5036 TRACE: --- Running test with pixmap depth 16 TRACE: Trying CapRound with width of 1 CHECK: XDrawArcs-69 33, line 5036 TRACE: Trying CapRound with width of 2 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0026.err for results CHECK: XDrawArcs-69 34, line 5036 TRACE: Trying CapRound with width of 4 REPORT: A total of 2 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0027.err for results CHECK: XDrawArcs-69 35, line 5036 TRACE: Trying CapRound with width of 5 CHECK: XDrawArcs-69 36, line 5036 TRACE: Trying CapRound with width of 10 REPORT: A total of 6 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0028.err for results CHECK: XDrawArcs-69 37, line 5036 TRACE: Trying CapRound with width of 11 CHECK: XDrawArcs-69 38, line 5036 TRACE: Trying CapRound with width of 40 REPORT: A total of 1 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0029.err for results CHECK: XDrawArcs-69 39, line 5036 TRACE: Trying CapRound with width of 41 CHECK: XDrawArcs-69 40, line 5036 /tset/Xlib9/drwarcs/Test 76 Warning VSW5TESTSUITE PURPOSE 76 Assertion XDrawArcs-76.(A) When a line has coincident endpoints (x1=x2, y1=y2), and the cap_style is applied to both endpoints and the line_width is not equal to zero and the cap_style is CapRound, then the closed path is a circle, centered at the endpoint, and with the diameter equal to the line-width. METH: Draw zero length line with CapRound. METH: Pixmap verify. TRACE: --- Running test with visual class TrueColor, depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0030.err for results CHECK: XDrawArcs-76 1, line 5367 CHECK: XDrawArcs-76 2, line 5367 TRACE: --- Running test with visual class DirectColor, depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0031.err for results CHECK: XDrawArcs-76 3, line 5367 CHECK: XDrawArcs-76 4, line 5367 TRACE: --- Running test with pixmap depth 1 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0032.err for results CHECK: XDrawArcs-76 5, line 5367 CHECK: XDrawArcs-76 6, line 5367 TRACE: --- Running test with pixmap depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0033.err for results CHECK: XDrawArcs-76 7, line 5367 CHECK: XDrawArcs-76 8, line 5367 TRACE: --- Running test with pixmap depth 16 REPORT: A total of 3 out of 9000 pixels were bad REPORT: Pixel check failed. See file Err0034.err for results CHECK: XDrawArcs-76 9, line 5367 CHECK: XDrawArcs-76 10, line 5367 /tset/Xlib15/gtwmnrmlhn/Test 1 Failed VSW5TESTSUITE PURPOSE 1 Assertion XGetWMNormalHints-1.(A) When the WM_NORMAL_HINTS property has been set on the window w with a type of WM_SIZE_HINTS, a format of 32 and is long enough to contain either a pre-ICCCM structure or a new size hints structure, then a call to XGetWMNormalHints sets the components of the XSizeHints structure named by the hints_return argument irrespective of whether the particular hint was previously set, and returns non-zero. METH: Create a window with XCreate window. METH: Set the WM_NORMAL_HINTS property with XSetWMNormalHints. METH: Obtain the value of the WM_NORMAL_HINTS property using XGetWMNormalhints. METH: Verify that the entire structure has been returned. TRACE: --- Running test with visual class TrueColor, depth 16 CHECK: XGetWMNormalHints-1 1, line 282 CHECK: XGetWMNormalHints-1 2, line 288 REPORT: The x component of the XSizeHints structure was 0 instead of 1. REPORT: The y component of the XSizeHints structure was 0 instead of 2. REPORT: The width component of the XSizeHints structure was 0 instead of 3. REPORT: The height component of the XSizeHints structure was 0 instead of 4. REPORT: The min_width component of the XSizeHints structure was 0 instead of 5. REPORT: The min_height component of the XSizeHints structure was 0 instead of 6. REPORT: The max_width component of the XSizeHints structure was 0 instead of 7. REPORT: The max_height component of the XSizeHints structure was 0 instead of 8. REPORT: The width_inc component of the XSizeHints structure was 0 instead