# Problem Database # Version 2.45 2010-02-08 # LSB 3.0 test libstdc++.so.6 3052 expected_severity failed marker Did not find symbol addr for Virtual table entry [0][4] marker Did not find symbol name for Virtual table entry [0][4] comment Test suite issue, virtual table entries are incorrect in the specification. lsb_report_id 0071 resolution Test suite deficiency quell dup libstdc++.so.6 3059 end # LSB 3.0 test /24_iterators/istreambuf_iterator/2.cc 1 expected_severity failed marker _24_iterators_istreambuf_iterator_2.exe comment Probably a bug in test suite header files (works with normal header files). comment The same problems are PR 0065 and PR 0095 #lsb_report_id 0065 #lsb_report_id 0095 #lsb_report_id 0129 lsb_report_id 0079 resolution Test suite deficiency quell end # LSB 3.0 test /demangle/abi_examples/01.cc 1 expected_severity failed marker terminate called after throwing an instance of 'std::runtime_error' marker what(): float comment The ABI changed from the last version of the test, the test suite was not yet updated. lsb_report_id 0080 #lsb_report_id 0130 resolution Test suite deficiency quell dup /demangle/abi_examples/02.cc 1 end # LSB 3.0 test /tset/PTHR.os/thread/pthread_create/T.pthread_create 4 expected_severity unresolved marker Posix Ref: Component PTHREAD_CREATE marker Assertion 9945-1:1996 16.2.2.2-4(A) marker waitpid() failed - errno 10 (ECHILD) marker tet_fork, expected 0, got -1 comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called. lsb_report_id 0082 resolution Test suite deficiency quell end # LSB 3.0 test /thread/pthread1.cc 1 expected_severity unreported lsb_report_id 0083 resolution Withdrawn quell dup /thread/pthread2.cc 1 dup /thread/pthread3.cc 1 dup /thread/pthread4.cc 1 dup /thread/pthread5.cc 1 dup /thread/pthread6.cc 1 end # LSB 3.0 test /tset/PTHR.os/thread/pthread_join/T.pthread_join 4 expected_severity unresolved marker Posix Ref: Component PTHREAD_JOIN marker Assertion 9945-1:1996 16.2.3.4-4(A) marker waitpid() failed - errno 10 (ECHILD) marker tet_fork, expected 0, got -1 comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called. comment See also Problem Report #102. #lsb_report_id 0102 lsb_report_id 0084 resolution Test suite deficiency quell end test /tset/CH03/mprsd/mprsd 12 expected_severity unresolved comment The test setup required to run the tests has been written to assume a live display or a virtual frame buffer with backing store, comment even though an X server and/or xvfb are not required by the LSB. This is a method to test the X library functions. comment Until recently the default xvfb had the backing store enabled, and this is expected to be reinstated. Its a one line change. comment Future releases of the test suite might include a working xvfb binary. lsb_report_id 0085 resolution This problem is because of runnig tests on Xvfb. quell dup /tset/CH03/mpsbws/mpsbws 11 dup /tset/CH03/mpsbws/mpsbws 12 dup /tset/CH03/mpwdw/mpwdw 12 dup /tset/CH03/mpwdw/mpwdw 13 end test http-4.15 0 expected_severity failed marker This test may fail if you use a proxy server marker not a problem with Tcl comment This test may fail if you use a proxy server. That is to be expected and is not a problem with Tcl. resolution Check if you use a proxy server. quell FIP end # LSB 3.0 test httpold-4.12 0 expected_severity failed marker set token [http_get $url -timeout 1 -command {lappend x fail}] marker ok ok marker timeout ok comment It is resolved by a newer tcl version and newer test suite. lsb_report_id 0088 resolution Test suite deficiency quell end # LSB 3.0 test /tset/POSIX.os/procprim/sigconcept/T.sigconcept 41 expected_severity unresolved marker unexpected signal 15 (SIGTERM) received comment Bugzilla 1065 highlights a possible timing error in this test case and has been accepted as a test suite deficiency. A patch has been proposed with bugzilla 1065 to address this. comment http://bugs.linuxbase.org/show_bug.cgi?id=1065 comment See also PR 0094, PR 0093 #lsb_report_id 0093 #lsb_report_id 0094 lsb_report_id 0089 resolution Test suite deficiency quell end # LSB 3.0 test libstdc++.so.6 3401 expected_severity failed marker _ZNSt15basic_streambuf marker showmanyc comment Test suite issue, the basic_streambuf::showmanyc() method was reimplemented comment in basic_streambuf instead of being inherited starting from gcc 4.0 lsb_report_id 0090 #lsb_report_id 0127 resolution Test suite deficiency quell dup libstdc++.so.6 3414 end # LSB 3.0 test /21_strings/char_traits/requirements/wchar_t/1.cc 1 expected_severity failed marker DejaGNUTest.command_1: /opt/lsb/test/lib/qmtest_libstdcpp_3.4.3/_21_strings_char_traits_requirements_wchar_t_1.exe marker DejaGNUTest.command_status_1: 11 marker DejaGNUTest.result_1: FAIL: 21_strings/char_traits/requirements/wchar_t/1.cc execution test marker INFO: qmtest.cause: 21_strings/char_traits/requirements/wchar_t/1.cc execution test comment See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23550. comment Also tracked here: http://bugs.linuxbase.org/show_bug.cgi?id=1069. lsb_report_id 0091 resolution Test suite deficiency quell end # LSB 3.0 test /tset/LSB.os/jump/makecontext/T.makecontext 1 expected_severity unresolved marker child process timed out comment The problem is the following: /* Save context area */ oucp = ucp; ucontext_t on PPC32 contains pointer into the struct itself. So, after this, the pointers will show to the wrong place. If you removes this line and add instead: + getcontext(&oucp); rval = getcontext(&ucp); a second getcontext call, it works. comment See also PR 0067 #lsb_report_id 0067 lsb_report_id 0092 resolution Test suite deficiency quell dup /tset/LSB.os/jump/makecontext/T.makecontext 3 end # LSB 3.0 test /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 8 expected_severity unreported comment The 32-bit binary test fails on PPC64 because mprotect() modifies comment permissions of some of the pages in the specified range even if comment it later fails; the test does not take this into account. lsb_report_id 0099 resolution Test suite deficiency quell end # LSB 3.0 test /tset/PTHR.os/thread/pthread_create/T.pthread_create 11 expected_severity unresolved marker Posix Ref: Component PTHREAD_CREATE marker Assertion 9945-1:1996 16.2.1.2-11(A) marker waitpid() failed - errno 10 (ECHILD) marker tet_fork, expected 0, got -1 comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called. lsb_report_id 0103 resolution Test suite deficiency quell end # LSB 3.0 test /tset/POSIX.os/procprim/sleep/T.sleep 1 expected_severity failed marker sleep returned after 26 seconds instead of 25 seconds comment See also PR 0096 #lsb_report_id 0096 lsb_report_id 0104 resolution Test suite deficiency quell end # LSB 3.0 test /tset/ANSI.os/streamio/fwrite 3 expected_severity unresolved marker fwrite() on non-blocking pipe failed with errno set to EAGAIN comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem. lsb_report_id 0105 resolution Test suite deficiency quell end test /tset/LSB.os/ioprim/writev_L 13 expected_severity failed marker writev() returned -1, expected > 0 comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem. lsb_report_id 0105 resolution Test suite deficiency quell end test /tset/POSIX.os/ioprim/write 13 expected_severity failed marker write() returned -1, expected > 0 comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem. lsb_report_id 0105 resolution Test suite deficiency quell end # LSB 1.3 test /test/LSB.os/mfiles/mmap_P/T.mmap_P 23 expected_severity failed marker vsrt_wait_for: Timed-out waiting for marker child to exit comment This is an S390 issue lsb_report_id 0108 resolution Regression end # LSB 3.0 test expect-1.3 0 expected_severity failed marker expect -ex hi {set x 3} comment See LSB Bugzilla #1116 lsb_report_id 0109 resolution Test suite deficiency quell end # LSB 3.0 test /tset/LSB.os/mfiles/msync_P/T.msync_P 5 expected_severity failed lsb_report_id 0110 resolution Test suite deficiency quell dup /tset/ANSI.os/streamio/freopen/T.freopen 17 dup /tset/LSB.os/ipc/msgget/T.msgget 2 dup /tset/LSB.os/ipc/msgget/T.msgget 3 end # LSB 3.0 test /tset/LSB.pam/testcases/pam_start/pam_start 3 expected_severity failed marker pam_start returned System error for NULL conv structure marker It was expected to return PAM_BUF_ERR. comment It is unclear what should be returned, both error values comment make sense. comment Entered into LSB Bugzilla as bug #1281 lsb_report_id 0111 resolution Test suite deficiency quell end # LSB 3.0 test /tset/POSIX.os/procenv/sysconf/T.sysconf 2 expected_severity failed marker sysconf(_SC_CHILD_MAX) did not return the value of CHILD_MAX comment The test seems to be incorrectly built with hard-wired value comment of the CHILD_MAX constant. comment Entered into LSB bugzilla as bug #1188. lsb_report_id 0112 resolution Test suite deficiency quell end # LSB 3.0 test /tset/LI18NUX2K.L1/base/setlocale/T.setlocale 1 expected_severity failed marker path tracing error: path counter comment The /tset/LI18NUX2K.L1/base/setlocale/T.setlocale{1,2} tests fail, reporting that the LC_CTYPE setting is not honored, when the iswxdigit() call returns a nonzero value different from 1 when applied on a digit. As the POSIX specs do not mandate the exact value, only the nonzero-ness, this test is overly strict. comment Reported to LSB Bugzilla as bug #1151 (http://bugs.linuxbase.org/show_bug.cgi?id=1151) and fixed for LSB 3.1. lsb_report_id 0113 resolution Test is too strict quell dup /tset/LI18NUX2K.L1/base/setlocale/T.setlocale 2 end # LSB 3.0 test /tset/LI18NUX2K.L1/utils/shell/T.shell 8 expected_severity failed marker test shell: bash marker diff is 1c1 < 0 1 2 3 4 a b c z - --- > 0 1 2 3 4 a b c z [[:hyphen:]] marker examined '[[:xdigit:]] [[:hyphen:]]' marker expected '0 1 2 3 4 a b c z -' marker in the locale LC_CTYPE = LTP_1.UTF-8 marker [[:xdigit:]] should contain 'z'('Z') marker [[:hyphen:]] should be '-' comment This test tries to create a file named '-' and then match it against a character class. However, it issues an incorrect command "touch -" which does not do what was expected. Reported to LSB Bugzilla as part of bug #1151 (please see comment #7 and following), fixed for LSB 3.1. comment LSB Bug #1151 tracks this. A patch has been developed. This is a test suite deficiency. comment http://bugs.linuxbase.org/show_bug.cgi?id=1151 lsb_report_id 0114 resolution Test suite deficiency quell end # LSB 3.0 test libpam.so.0 15 expected_severity failed marker ((unversioned)) comment The lsblibcheck tool does not expect symbols in libpam to be versioned, comment so it fails on every such symbol. Reported to LSB bugzilla as bug #1122 comment and fixed for LSB 3.1. lsb_report_id 0115 resolution Test suite deficiency quell dup libpam.so.0 16 dup libpam.so.0 17 dup libpam.so.0 18 dup libpam.so.0 19 dup libpam.so.0 20 dup libpam.so.0 21 dup libpam.so.0 22 dup libpam.so.0 23 dup libpam.so.0 24 dup libpam.so.0 25 dup libpam.so.0 26 dup libpam.so.0 27 end # LSB 3.0 test LSB.os/ioprim/writev_L/T.writev_L 30 expected_severity failed marker iov[0].iov_len = 1024 marker readv(5, iov, 1024) did not behave as expected marker ERRNO VALUES: expected: marker (EINVAL) marker observed: marker (EFAULT) comment The test attempts to do a writev() call with sum of sizes I/O buffers larger than ssize_t, to test whether the call properly returns EINVAL. This however fails on 64-bit architectures because they have ssize_t so large that it is not possible to allocate a buffer of such size (2 TB). This causes the test to fail. comment Reported to LSB bugzilla as bug #844 comment See also LSB bugzilla bug #6 lsb_report_id 0116 #lsb_report_id 0144 resolution Test suite deficiency quell end # LSB 3.0 test /tset/LSB.os/ioprim/readv_L/T.readv_L 24 expected_severity failed marker ERRNO VALUES: expected: 21 (EINVAL), observed: 14 (EFAULT) comment The test fails after trying to do a readv() with the sum of buffers larger than ssize_t (the 64-bit architecture has ssize_t so large that it is not possible to create a buffer so large that it would overflow). lsb_report_id 0117 #lsb_report_id 0143 resolution Test suite deficiency quell end # LSB 3.1 test /tset/CH02/clsdsply/clsdsply 8 expected_severity Unreported comment The clsdsply.8 test crashes (glibc reports memory corruption) when run with a Xvfb server with Rui Feng's patch (which fixes failures with overlong requests and deadlock on rprntwdw test). lsb_report_id 0118 resolution Test suite deficiency quell end # LSB 3.1 test /22_locale/locale/cons/12352.cc 1 expected_severity failed comment It was decided that this test does not test any identifiable part of the specification, and should be removed. comment It is the sense of the SA that this failure, while not perhaps a violation of the LSB specification, may possibly cause QA problems for any distribution which sees it, and should thus be taken seriously. lsb_report_id 0119 resolution Test suite deficiency quell end # LSB 3.1 test /tset/CH02/vndrrls/vndrrls 1 expected_severity failed marker XVendorRelease() returned 7 comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX. comment See also bug 1339 in the Bugzilla: http://bugs.linuxbase.org/show_bug.cgi?id=1339 lsb_report_id 0122 #lsb_report_id 0123 #lsb_report_id 0124 resolution OK for Xserver 7.XX quell end test /tset/CH02/vndrrls/mvndrrls 1 expected_severity failed marker VendorRelease() returned 7 comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX. comment See also bug 1339 in the Bugzilla: http://bugs.linuxbase.org/show_bug.cgi?id=1339 lsb_report_id 0122 #lsb_report_id 0123 #lsb_report_id 0124 resolution OK for Xserver 7.XX quell end # LSB 3.1 test libX11.so.6 478 expected_severity failed marker Did not find Xau marker ((unversioned)) in libX11.so.6 comment Bug 1330: http://bugs.linuxbase.org/show_bug.cgi?id=1330 lsb_report_id 0125 #lsb_report_id 0126 #lsb_report_id 0128 resolution Test suite deficiency quell dup libX11.so.6 479 dup libX11.so.6 480 dup libX11.so.6 481 end test /tset/LSB.os/genuts/nftw/T.nftw 9 expected_severity failed lsb_report_id 0132 resolution Known problem dup /tset/LSB.os/mfiles/msync_P/T.msync_P 7 end test /22_locale/locale/cons/12438.cc 1 expected_severity failed marker St9bad_alloc lsb_report_id 0133 resolution Test suite deficiency quell end # LSB 3.1 test /tset/PTHR.os/threadattr/pthread_attr_getstacksize/T.pthread_attr_getstacksize 1 expected_severity failed comment This failure is caused by VSTH_VALID_STACKSIZE=16384 which is too small comment for ppc{32,64} in glibc-2.5, due to the decision to go with 64KB pages. lsb_report_id 0134 resolution Test suite deficiency quell dup /tset/PTHR.os/threadattr/pthread_attr_setstacksize/T.pthread_attr_setstacksize 2 end # LSB 3.1 test /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r 1 expected_severity failed marker The system does not support the PTHREAD_SCOPE_PROCESS lsb_report_id 0137 resolution Known problem dup /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r 2 end # LSB 3.1 test /tset/POSIX.os/procenv/getlogin/T.getlogin 1 expected_severity failed marker getlogin() returned failed - errno 2 (ENOENT) resolution Known problem lsb_report_id 0138 end # LSB 3.1 test /tests/functions/GdkProperties/GdkProperties 5 expected_severity failed marker gdk_atom_name: doesnt match the expected string comment The test should not intern a random atom and expect to always get comment the same number back from the X server. lsb_report_id 0139 resolution Test suite deficiency quell end test /tests/functions/GdkProperties/GdkProperties 11 expected_severity failed marker gdk_atom_intern: not a expected atom comment The test should not intern a random atom and expect to always get comment the same number back from the X server. lsb_report_id 0139 resolution Test suite deficiency quell end # LSB 3.1 test /tests/functions/GtkTreeStore/GtkTreeStore 53 expected_severity failed marker iter_valid = 1, should be 0 comment GtkTreeView never guarantees that certain operations do invalidate an iter. comment It only guarantees that certain operations do not invalide an iter. comment So checking an iter for being invalid is not a meaningful test. lsb_report_id 0140 resolution Test suite deficiency quell end # LSB 3.1 test /tset/LI18NUX2K.L1/base/getwchar/T.getwchar 3 expected_severity failed marker path tracing error: path counter 0, expected 1 lsb_report_id 0141 resolution Test suite deficiency quell end # LSB 3.1 test /tests/functions/GtkContainer/GtkContainer 65 expected_severity unreported comment See also LSB Bugzilla #1551. lsb_report_id 0142 resolution Known problem quell end # LSB 3.1 test /tset/ANSI.os/genuts/free/T.free 1 expected_severity failed marker failed to reuse freed memory in next 1000 malloc() calls lsb_report_id 0145 resolution Test suite deficiency quell end # LSB 3.1 test libstdc++.so.6 4003 expected_severity failed marker 0x80ee24a078 lsb_report_id 0146 resolution Test suite deficiency quell end # test libstdc++.so.6 4010 expected_severity failed marker 0x80ee246af8 lsb_report_id 0146 resolution Test suite deficiency quell end # LSB 3.1 test /tset/LSB.os/genuts/nftw/T.nftw 5 expected_severity failed marker ftw(".", ..., 3) returned -1 instead of 0 marker function set by ftw() not called for marker ./ftwD2/ftw_d.3/ftw_t.7 marker function set by ftw() not called for ./ftwD2/ftw_d.3 lsb_report_id 0147 resolution Test suite deficiency quell end # LSB 3.0 test libstdc++.so.6 3079 expected_severity failed marker _ZNKSt9exception4whatEv (expected) doesn't match _ZNKSt10bad_typeid4whatEv (found) lsb_report_id 0148 resolution Test suite deficiency quell end # LSB 3.1 test /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 2 expected_severity failed marker sysconf(_SC_XOPEN_VERSION) marker got 600 lsb_report_id 0149 resolution Test suite deficiency quell end # LSB 3.1 test /tset/CH05/crtclrmp/crtclrmp 11 expected_severity failed marker Received error type BadMatch marker Got BadMatch, Expecting BadValue lsb_report_id 0150 comment Upstream Xorg has evidently changed an error value from BadValue to BadMatch. As noted in bug 1589, this is probably an unreasonable expectation from the test, and at any rate now differs from upstream's behavior. It's likely that, as distributions move to newer versions of Xorg, more of them will start seeing this. comment See Bug #1589 in the LSB Bugzilla. comment See also TestPilot 3.1.1: http://www.linux-foundation.org/en/TestPilot311#lsb-test-vsw4 end # LSB 3.1 test /tset/CH10/crtimg/crtimg 1 expected_severity unresolved marker XCreateImage() returned NULL lsb_report_id 0151 comment Under certain circumstances, it's possible for XCreateImage to return NULL, but the test does not allow for this. A patch has been applied to fix both xts5 and vsw4 (see bug 1693), but some testers are still seeing this. comment See Bug #1693 in the LSB Bugzilla. end # --- test Test comments Case-05 0 expected_severity failed marker Case > still in comment --> | 05 | comment This is a contradiction with HTML standart, not LSB. resolution Wrong behaviour of the application quell end test Checking the port 80 0 expected_severity failed marker httpd: Could not marker determine the server's fully qualified domain name, using comment `apachectl' returns the error code 1, but it works normally. resolution Warning message quell end test /tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5 expected_severity failed marker pam_authenticate returned Authentication failure when expected to succeed marker euid : 0 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. comment The details haven't been explored, but this failure doesn't appear if the test runned without DTK Manager. resolution TEF's fault quell end # --- test /tset/LSB.os/genuts/ftw_L/T.ftw_L 4 expected_severity warning marker FTW_SL comment The linux ftw() function follows symlinks, it does not report them. resolution Insignificant quell end test /tset/ANSI.os/maths/pow/T.pow 4 expected_severity warning marker pow(0.0, -1.0) marker expected: -inf marker observed: inf comment Both -inf and +inf are equally artificial results, Linux libc picks this one. resolution Insignificant quell end test /tset/ANSI.os/streamio/fopen/T.fopen 28 expected_severity warning marker fopen() succeeded marker FOPEN_MAX streams marker already open comment FOPEN_MAX is just an advisory limit, there is probably no real limit except memory. resolution Insignificant quell end test /tset/POSIX.os/procprim/kill_X/T.kill_X 1 expected_severity warning marker process calling kill() marker did not receive signal comment The Linux implementation of kill() sends the signal to everyone except its own process, comment which is also logical. resolution Insignificant quell end test /tset/ANSI.os/streamio/remove_X/T.remove_X 1 expected_severity warning marker expected: 26 (ETXTBSY) marker observed: 0 (NO ERROR) comment Linux allows to remove a running executable file without any side effects. resolution Feature quell end test /tset/ANSI.os/streamio/tmpfile/T.tmpfile 2 expected_severity warning marker mode 0666 marker found 0600 comment Not a bug but feature. Linux tmpfile() creates files with access rights 0600 comment which is more secure than POSIX mandated 0666. resolution Feature quell end test /tset/POSIX.os/dataform/tar/T.tar 12 expected_severity fip marker create utility exited with code 1 comment This test tries to call tar with a file with too long name (>100 chars). comment The tar utility can either skip the file, or fail completely; both results comment are correct. resolution Correct quell end test /tset/POSIX.os/devclass/c_iflag/T.c_iflag 19 expected_severity warning marker 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). resolution Normal quell end test /tset/POSIX.os/devclass/c_lflag/T.c_lflag 6 expected_severity warning marker 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). resolution Normal quell end test /tset/POSIX.os/devclass/tcdrain/T.tcdrain 2 expected_severity warning marker 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). resolution Normal quell end test /tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 8 expected_severity warning marker 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). resolution Normal quell end test /tset/POSIX.os/files/access_X/T.access_X 1 expected_severity warning marker did not give correct results marker expected: -1, observed: 0 marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR) comment On Linux, running executable files are normally accessible. resolution Feature quell end test /tset/POSIX.os/files/rename_X/T.rename_X 1 expected_severity warning marker did not give correct results marker expected: -1, observed: 0 marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR) comment Not a bug but feature. On Linux, running executable files are normally accessible. resolution Feature quell end test /tset/POSIX.os/files/stat_X/T.stat_X 1 expected_severity fip marker stat("/dev/sda", buf) marker returned st_rdev value of 0x800 comment This is a correct result, /dev/sda has major/minor number 0x0800. resolution Correct quell end test /tset/POSIX.os/files/stat_X/T.stat_X 2 expected_severity fip marker stat("/dev/tty", buf) marker returned st_rdev value of 0x500 comment This is a correct result, /dev/tty has major/minor number 0x0500. resolution Correct quell end test /tset/POSIX.os/files/unlink_X/T.unlink_X 1 expected_severity warning marker did not give correct results marker expected: -1, observed: 0 marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR) comment On Linux, running executable files are normally accessible. resolution Feature quell end test /tset/POSIX.os/procenv/sysconf/T.sysconf 3 expected_severity warning marker CLK_TCK not defined comment Insignificant; CLK_TCK is obsolete anyway. resolution Insignificant quell end test /tset/LSB.os/procenv/chroot/T.chroot 4 expected_severity fip marker execve() of ./chroot_t4 marker failed - errno 2 (ENOENT) comment This is correct behavior. The ./chroot_t4 executable cannot be run comment because the needed shared libraries are not present comment in the chrooted environment. resolution Correct quell end test /tset/LSB.fhs/var/spool-lpd/spool-lpd-tc 2 expected_severity fip marker /var/spool/lpd/lpd.lock: marker file not found comment Normal when lpd is not installed. resolution Normal quell end test /tset/LSB.fhs/var/spool-rwho/spool-rwho-tc 1 expected_severity fip marker /var/spool/rwho: marker directory not found comment Normal when rwho is not installed. resolution Normal quell end test /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 17 expected_severity fip marker sysconf(_SC_2_C_VERSION) returned -1 marker sysconf(_SC_XOPEN_ENH_I18N) returned 1 marker sysconf(_SC_XOPEN_SHM) returned 1 marker sysconf(_SC_XOPEN_LEGACY) returned 1 comment This is a typical result on Linux. resolution Correct quell end test /tset/LI18NUX2K.L1/utils/localedef/T.localedef 3 expected_severity warning marker created locale unexpectedly marker eixt code of localedef is 0 marker This test result is waived now. comment This test is waived by the LSB committee. resolution Waived quell end test /tset/LSB.os/genuts/getopt/T.getopt 1 expected_severity warning marker getopt() failed when called with :- marker optstring : [ab:cd:e] marker arguments : [-a] [-d] marker getopt() failed on the following :- marker optind : expected [4], actual [3] marker arguments : [-ab] marker optind : expected [3], actual [2] comment This is a known minor bug related to locale handling. resolution Known minor bug quell end test /23_containers/bitset/cons/16020.cc 1 expected_severity warning marker compilation failed comment Test executable was not correctly compiled when the test was built. comment (No compilation is done during the test phase so it cannot fail). resolution False positive quell dup /23_containers/bitset/invalidation/1.cc 1 dup /23_containers/bitset/operations/13838.cc 1 dup /backward/11460.cc 1 dup /ext/enc_filebuf/char/13189.cc 1 dup /ext/enc_filebuf/wchar_t/13189.cc 1 dup /backward/strstream_members.cc 1 dup /23_containers/deque/invalidation/1.cc 1 dup /23_containers/deque/invalidation/2.cc 1 dup /23_containers/deque/invalidation/3.cc 1 dup /23_containers/deque/invalidation/4.cc 1 dup /23_containers/list/invalidation/1.cc 1 dup /23_containers/list/invalidation/2.cc 1 dup /23_containers/list/invalidation/3.cc 1 dup /23_containers/list/invalidation/4.cc 1 dup /23_containers/map/insert/16813.cc 1 dup /23_containers/map/invalidation/1.cc 1 dup /23_containers/map/invalidation/2.cc 1 dup /23_containers/multimap/invalidation/1.cc 1 dup /23_containers/multimap/invalidation/2.cc 1 dup /23_containers/multiset/invalidation/1.cc 1 dup /23_containers/multiset/invalidation/2.cc 1 dup /23_containers/set/invalidation/1.cc 1 dup /23_containers/set/invalidation/2.cc 1 dup /23_containers/vector/invalidation/1.cc 1 dup /23_containers/vector/invalidation/2.cc 1 dup /23_containers/vector/invalidation/3.cc 1 dup /23_containers/vector/invalidation/4.cc 1 end test /tset/Xlib3/vndrrls/MTest 1 expected_severity fip marker REPORT: VendorRelease() returned 60900000 instead of 40201001. comment This answer is correct provided that the X server is X.org 6.9. resolution Correct answer for X.Org 6.9 quell end test /tset/Xlib3/vndrrls/Test 1 expected_severity fip marker REPORT: XVendorRelease() returned 60900000 instead of 40201001. comment This answer is correct provided that the X server is X.org 6.9. resolution Correct answer for X.Org 6.9 quell end test /tset/Xlib3/srvrvndr/MTest 1 expected_severity fip marker REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation" marker REPORT: Observed value "The X.Org Foundation" comment This answer is correct provided that the X server is X.Org-based. resolution Correct answer for X.Org-based X server quell end test /tset/Xlib3/srvrvndr/Test 1 expected_severity fip marker REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation" marker REPORT: Observed value "The X.Org Foundation" comment This answer is correct provided that the X server is X.Org-based. resolution Correct answer for X.Org-based X server quell end test /tset/POSIX.os/ioprim/write/T.write 13 expected_severity failed marker returned -1, expected > 0 marker errno was set to 11 (EAGAIN) comment This problem was faced earlier. comment See http://osdir.com/ml/linux.debian.ports.ia64/2005-10/msg00004.html dup /tset/LSB.os/ioprim/writev_L/T.writev_L 13 end test /tset/POSIX.os/procprim/exec/T.execl 30 expected_severity failed resolution May be a known problem comment See, http://bugs.linuxbase.org/show_bug.cgi?id=1827; comment More details at http://lkml.org/lkml/2008/2/27/164; comment Please, send this journal to linux@ispras.ru. We need more details on this problem but can't reproduce the bug. Thank you. dup /tset/POSIX.os/procprim/exec/T.execle 30 dup /tset/POSIX.os/procprim/exec/T.execlp 30 dup /tset/POSIX.os/procprim/exec/T.execv 30 dup /tset/POSIX.os/procprim/exec/T.execve 30 dup /tset/POSIX.os/procprim/exec/T.execvp 30 dup /tset/POSIX.os/procprim/fork/T.fork 18 end #################### test /tset/Xlib14/vcnlist/Test 2 expected_severity failed resolution Test suite bug marker REPORT: Returned value does not match expected value for foreground marker REPORT: returned 0 marker REPORT: expected 1 marker TRACE: background marker CHECK: XVaCreateNestedList-2 7, line 673 comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla end test /tset/Xlib14/vcnlist/Test 3 expected_severity failed resolution Test suite bug marker REPORT: Returned value does not match expected value for foreground marker REPORT: returned 0 marker REPORT: expected 1 marker TRACE: background comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla end test /tset/Xlib14/vcnlist/Test 4 expected_severity failed resolution Test suite bug marker 4 marker 5 marker TRACE: foreground marker REPORT: Returned value does not match expected value for foreground marker REPORT: returned 0 marker REPORT: expected 1 marker 5 marker TRACE: background comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla end test /tset/Xlib13/allwevnts/Test 20 expected_severity failed resolution Appears in multiple distros comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, comment see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html dup /tset/Xlib13/allwevnts/Test 24 dup /tset/Xt11/tcalbrcrl/Test 1 dup /tset/Xt8/tmkgmreqt/Test 4 dup /tset/Xt8/tmkrsizrt/Test 4 dup /tset/Xlib17/gtdflt/Test 3 dup /tset/Xlib17/gtdflt/Test 5 end test libX11.so.6 478 expected_severity failed resolution The LSB disposition of this failure is not yet determined comment http://www.linux-foundation.org/en/TestPilot31#lsblibchk comment These tests are likely to fail on an X.org 7.0 or later release. comment The problem is four interfaces that have moved from libX11 to libXau: XauDisposeAuth, XauFileName, XauGetBestAuthByAddr, XauReadAuth. As written, the LSB 3.1 spec still requires these to be present in libX11. comment See bug 1330: http://bugs.linuxbase.org/show_bug.cgi?id=1330 dup libX11.so.6 479 dup libX11.so.6 480 dup libX11.so.6 481 end test /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 5 expected_severity failed resolution These failures occur with cpio 2.6. There is a patch to fix this problem. comment http://www.linux-foundation.org/en/TestPilot31#cpio comment 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. comment There is a patch to cpio to fix this problem, follow the link above. comment Also see Debian bug 381348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348 dup /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 6 dup /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 7 end test /tset/PTHR.os/procenv/ttyname_r/T.ttyname_r 2 expected_severity failed resolution There are patches to glibc for Mandriva 2007.0, that could help. comment relevant patches to glibc look to be be here: http://sourceware.org/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/ttyname_r.c.diff?r1=1.17&r2=1.18&cvsroot=glibc http://sourceware.org/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/ttyname.c.diff?r1=1.20&r2=1.21&cvsroot=glibc comment See: http://www.linux-foundation.org/en/TestPilot31#lsb-runtime-test_on_Mandriva_2007.0.2C_Cooker end ############################# # Known problems revealed by the Desktop-t2c tests test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 46 expected_severity failed resolution Known problem (waived) marker g_main_context_check: sources with higher numerical priority than specified are being checked. comment This failure occurs due to the following problem:
comment The "g_main_context_check" interface ignores it's "max_priority" parameter.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_hooks/glib_hooks 3 expected_severity unresolved resolution Known problem marker g_hook_free marker unexpected signal 11 (SIGSEGV) received comment This failure occurs due to the following problem:
comment Invocation of the interface "g_hook_free" fails in certain conditions.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_unicode/glib_unicode 39 expected_severity unresolved resolution Known problem marker Child process calling 'g_utf8_strreverse' died unexpectedly. comment This failure occurs due to the following problem:
comment Invocation of the interface "g_utf8_strreverse" crashes for certain input values.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_automatic_string_completion/glib_automatic_string_completion 11 expected_severity unresolved resolution Known problem marker g_completion_complete_utf8 marker unexpected signal 11 (SIGSEGV) received comment This failure occurs due to the following problem:
comment Invocation of the interface "g_completion_complete_utf8" with certain values causes an abnormal termination with SIGSEGV signal.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkObject_relation/AtkObject_relation 2 expected_severity failed resolution Known problem (waived) marker atk_object_add_relationship marker Function returned TRUE, but didn't add the relationship comment This failure occurs due to the following problem:
comment atk_object_add_relationship doesn't add relationship, which already exists, but returns TRUE.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkObject_relation/AtkObject_relation 6 expected_severity failed resolution Known problem (waived) marker atk_object_remove_relationship marker Function shouldn't delete other relationships comment This failure occurs due to the following problem:
comment atk_object_remove_relationship can remove more relationships than it should.
comment Detailed description of this problem is available here. quell dup /atk-t2c/tests/AtkObject_relation/AtkObject_relation 7 end test /atk-t2c/tests/AtkHyperlink/AtkHyperlink 19 expected_severity failed resolution Known problem (waived) marker Value of property should coincide with value returned by atk_hyperlink_get_start_index. marker {start_index.05} comment This failure occurs due to the following problem:
comment Incorrect registration of the "start-index" property for AtkHyperlink.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 82 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment failed: expected value = "Fourth Comment", returned value = "Fourth Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 83 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment from above group failed: expected value = "Third Comment", returned value = "Third Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 84 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment from above first group failed: expected value = "First Comment", returned value = "First Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 88 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment failed: expected value = "Fourth Comment", returned value = "Fourth Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 89 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment from above group failed: expected value = "Third Comment", returned value = "Third Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 90 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker get comment from above first group failed: expected value = "First Comment", returned value = "First Comment comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 106 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker set comment = "comment 1" get comment = "comment 1 comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 107 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker set comment = "comment 2" get comment = "#comment 2" comment This failure occurs due to the following problem:
comment The "g_key_file_set_comment" interface prepends '#' character to the comment.
comment Detailed description of this problem is available here. quell dup /glib-t2c/tests/glib_key_parser/glib_key_parser 118 end test /glib-t2c/tests/glib_key_parser/glib_key_parser 108 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker set comment = "comment 3" get comment = "comment 3 comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell dup /glib-t2c/tests/glib_key_parser/glib_key_parser 119 end test /glib-t2c/tests/glib_key_parser/glib_key_parser 114 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker Comment above the Group = "Second Group" not removed , Get comment should be NULL, now is "Third Comment comment This failure occurs due to the following problem:
comment Invocation of the interface "g_key_file_remove_comment" does not remove comment in specific case.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 117 expected_severity failed resolution Known problem (waived) marker g_key_file_new.01 marker Trying to set comment: set comment = "comment 1" get comment = "comment 1 comment This failure occurs due to the following problem:
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_unicode/glib_unicode 206 expected_severity failed resolution Known problem marker g_unichar_isdefined comment This failure occurs due to the following problem:
comment g_unichar_isdefined returns TRUE for 'surrogate' code points.
comment Detailed description of this problem is available here. quell dup /glib-t2c/tests/glib_unicode/glib_unicode 207 dup /glib-t2c/tests/glib_unicode/glib_unicode 208 end test /atk-t2c/tests/AtkUtils/AtkUtils 5 expected_severity failed resolution Known problem (waived) marker should return 0 on failure. comment This failure occurs due to the following problem:
comment atk_add_global_event_listener, atk_add_key_event_listener return incorrect value in case of error.
comment Detailed description of this problem is available here. quell dup /atk-t2c/tests/AtkUtils/AtkUtils 8 end test /atk-t2c/tests/AtkStateSet/AtkStateSet 24 expected_severity failed resolution Known problem (waived) marker When called for empty sets, the function should return NULL. marker But it returned comment This failure occurs due to the following problem:
comment atk_state_set_or_sets returns an empty set rather than NULL.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkObject_signals/AtkObject_signals 16 expected_severity failed resolution Known problem (waived) marker The signal "property-change" should be emitted when an object's property value changes. comment This failure occurs due to the following problem:
comment "property-change" signal is not always emitted when the value of the "accessible-role" property changes.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkObject_properties/AtkObject_properties 4 expected_severity failed resolution Known problem (waived) marker Initial value of the role is marker Value of the property should be 0 just after creation of an object. comment This failure occurs due to the following problem:
comment "accessible-role" - invalid default value.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkRelationSet/AtkRelationSet 10 expected_severity failed resolution Known problem (waived) marker should not add a relation to the set if the relation is already present in it. comment This failure occurs due to the following problem:
comment atk_relation_set_add always adds relation to the set.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_thread_pools/glib_thread_pools 13 expected_severity unresolved resolution Known problem marker g_thread_pool_free.01 marker g_thread_pool_free.04.02 marker g_thread_pool_free.03 marker g_thread_pool_free.02.01 marker Error reported in glib_thread_pools.c comment This failure occurs due to the following problem:
comment Invocation of the interface "g_thread_pool_free" with certain values causes an error.
comment Detailed description of this problem is available here. quell end test /gmodule-t2c/tests/gmodule/gmodule 15 expected_severity failed resolution Known problem (waived) marker gmodule-t2c/testdata/gmodule/open/la1/test.la comment This failure occurs due to the following problem:
comment g_module_open fails to open modules with ".la" extension.
comment Detailed description of this problem is available here. quell end test /gmodule-t2c/tests/gmodule/gmodule 31 expected_severity failed resolution Known problem (waived) marker Error occurs in g_module_open, but g_module_error doesn't reveal it. comment This failure occurs due to the following problem:
comment g_module_error returns NULL after g_module_open has failed to open a module with ".la" extension.
comment Detailed description of this problem is available here. quell end test /atk-t2c/tests/AtkObject_properties/AtkObject_properties 16 expected_severity failed resolution Known problem (waived) marker Type of property should be gdouble. comment This failure occurs due to the following problem:
comment Spurious gdouble in "accesible-value" property of an AtkObject.
comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_memchunks/glib_memchunks 1 expected_severity failed resolution Known problem (waived) comment Memory chunks are deprecated since glib version 2.10.
quell dup /glib-t2c/tests/glib_memchunks/glib_memchunks 2 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 3 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 4 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 5 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 6 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 7 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 8 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 9 dup /glib-t2c/tests/glib_memchunks/glib_memchunks 10 end test /fontconfig-t2c/tests/FcPattern/FcPattern 57 expected_severity unresolved resolution Known problem #marker Abnormal child process termination comment This failure occurs due to the following problem:
comment Crash after FcPatternAdd is called several times.
comment Detailed description of this problem is available here. quell end test /fontconfig-t2c/tests/FcFontSet/FcFontSet 11 expected_severity unresolved resolution Known problem marker FcFontSetSort comment This failure may occur in fontconfig versions older that 2.4. FcFontSetSort() causes segmentation fault.
comment The reason is probably incorrect handling of csp parameter of FcFontSetSort() when csp is NULL.
quell end test /glib-t2c/tests/glib_random/glib_random 9 expected_severity failed resolution FIP comment There is no criteria out there that can guarantee that the numbers from a sequence are uniformly distributed random values.
comment There is always probability for any criterion to return wrong result.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_random/glib_random 10 dup /glib-t2c/tests/glib_random/glib_random 11 dup /glib-t2c/tests/glib_random/glib_random 12 dup /glib-t2c/tests/glib_random/glib_random 13 dup /glib-t2c/tests/glib_random/glib_random 14 dup /glib-t2c/tests/glib_random/glib_random 15 dup /glib-t2c/tests/glib_random/glib_random 16 dup /glib-t2c/tests/glib_random/glib_random 17 dup /glib-t2c/tests/glib_random/glib_random 18 dup /glib-t2c/tests/glib_random/glib_random 19 dup /glib-t2c/tests/glib_random/glib_random 20 dup /glib-t2c/tests/glib_random/glib_random 21 dup /glib-t2c/tests/glib_random/glib_random 22 dup /glib-t2c/tests/glib_random/glib_random 23 end test /glib-t2c/tests/glib_caches/glib_caches 7 expected_severity failed resolution Known problem marker g_cache_value_foreach.01 comment g_cache_value_foreach is deprecated since glib version 2.10.
end test /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 6 expected_severity unresolved resolution Known problem marker unexpected signal 11 (SIGSEGV) received comment This failure occurs due to the following problem:
comment Calling FcDirScan causes segmentation fault.
comment Detailed description of this problem is available here. quell end test /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 7 expected_severity failed resolution Known problem (waived) marker FcDirSave comment This failure occurs due to the following:
comment According to the documentation for fontconfig 2.5.91, FcDirSave is deprecated and should do nothing aside from returning FcFalse. But still it may try to do something and return FcTrue in older versions of this library.
#comment Detailed description of this problem is available here. quell end test /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 7 expected_severity unresolved resolution FIP #marker unexpected signal 1 (SIGHUP) received comment This failure may occur if gdb is set up incorrectly (e.g. 32-bit gdb on a 64-bit machine or vice versa). If the tests were executed in a chroot environment, there can be something wrong with this environment as well.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 9 dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 5 dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 6 dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 8 end test /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 9 expected_severity failed resolution FIP #marker unexpected signal 1 (SIGHUP) received comment This failure may occur if gdb is set up incorrectly (e.g. 32-bit gdb on a 64-bit machine or vice versa). If the tests were executed in a chroot environment, there can be something wrong with this environment as well.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 4 expected_severity failed resolution FIP marker try_iconv(): unable to create an iconv-based converter comment It seems that iconv() itself fails to perform required operations on this system.
comment The problem is probably not in GLib.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 5 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 6 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 7 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 27 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 28 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 29 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 32 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 33 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 34 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 37 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 43 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 49 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 52 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 53 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 54 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 55 end test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 9 expected_severity unresolved resolution FIP marker try_iconv(): unable to create an iconv-based converter comment It seems that iconv() itself fails to perform required operations on this system.
comment The problem is probably not in GLib.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 10 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 11 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 12 dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 56 end test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 58 expected_severity unresolved resolution FIP marker Standard iconv() error comment It seems that iconv() itself fails to perform required operations on this system.
comment The problem is probably not in GLib.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 59 end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 58 expected_severity failed resolution FIP marker g_timeout_add.01 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 32 expected_severity failed resolution Test suite deficiency marker The err must be NULL comment There is a problem in the tests for glib_character_set_conversion. comment It should be fixed in a newer version of the test suite. quell dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 33 end test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 32 expected_severity failed resolution Test suite deficiency marker The number of bytes stored comment There is a problem in the tests for glib_character_set_conversion. comment It should be fixed in a newer version of the test suite. quell dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 33 end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 7 expected_severity failed resolution FIP marker g_main_loop_run.02 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 17 expected_severity unresolved resolution FIP marker Unable to initialize comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell dup /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 18 end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 57 expected_severity failed resolution FIP marker g_timeout_source_new comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 87 expected_severity failed resolution FIP marker g_child_watch_source_new.01 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 74 expected_severity failed resolution FIP marker g_idle_source_new comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_threads/glib_threads 31 expected_severity failed resolution FIP marker g_static_rw_lock_reader_lock.01 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_threads/glib_threads 26 expected_severity failed resolution FIP marker g_static_rec_mutex_lock_full.01 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_thread_pools/glib_thread_pools 11 expected_severity failed resolution FIP marker g_thread_pool_unprocessed.01 comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.
comment This test needs to be investigated manually. quell end test /glib-t2c/tests/glib_simple_xml_subset_parser/glib_simple_xml_subset_parser 29 expected_severity failed resolution Test suite deficiency marker g_markup_parse_context_parse marker The data need not be valid UTF-8 comment The test did not take into account that g_markup_parse_context_parse may also return G_MARKUP_ERROR_PARSE when invalid UTF-8 sequence is encountered.
comment The problem should be fixed in a newer version of the test suite. quell end test /glib-t2c/tests/glib_key_parser/glib_key_parser 36 expected_severity failed resolution Specification error marker assertion `group_name != NULL' failed comment In LSB 3, the specification incorrectly described the behavior of comment several g_key_file_* interfaces when the group_name parameter is comment set to NULL. These tests rely on the behavior described in the comment specification. Please see comment bug 1722 in the LSB bug tracker for more information. quell dup /glib-t2c/tests/glib_key_parser/glib_key_parser 60 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 64 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 76 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 87 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 101 end test /glib-t2c/tests/glib_key_parser/glib_key_parser 104 expected_severity failed resolution Specification error marker assertion `g_key_file_is_group_name (group_name)' failed comment In LSB 3, the specification incorrectly described the behavior of comment several g_key_file_* interfaces when the group_name parameter is comment set to NULL. These tests rely on the behavior described in the comment specification. Please see comment bug 1722 in the LSB bug tracker for more information. quell dup /glib-t2c/tests/glib_key_parser/glib_key_parser 110 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 113 dup /glib-t2c/tests/glib_key_parser/glib_key_parser 116 end test /glib-t2c/tests/glib_unicode/glib_unicode 18 expected_severity failed resolution Change in an external standard marker g_unichar_isdefined: error to determine comment This test was used to ensure that the function comment g_unichar_isdefined returns FALSE for an unassigned comment Unicode code point. The test used code point U+0372 comment as its unassigned code point, which received an comment assignment in Unicode 5.1. Newer glib versions comment correctly recognize this, which cause the test to fail. quell end test /glib-t2c/tests/glib_messagelog/glib_messagelog 9 expected_severity failed resolution Known problem marker signal 5 comment This test may fail on development versions of Glib library as well as any other versions comment compiled with '-DG_ENABLE_DEBUG' option. comment These versions of Glib behave differently from what is stated in the description of g_log* functions comment in Glib Reference (section: "Message Logging"): comment they do not call abort() but rather call G_BREAKPOINT() first, which may result in SIGTRAP. comment This problem should not take place with stable versions of Glib: they are compiled without '-DG_ENABLE_DEBUG' by default. quell dup /glib-t2c/tests/glib_messagelog/glib_messagelog 10 end ############################# test xdg-desktop-icon 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-desktop-menu 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-email 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-icon-resource 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-mime 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-open 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test xdg-screensaver 1 expected_severity failed resolution Trial Use Module comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module. quell end test java 1 expected_severity failed resolution Trial Use Module comment This failure does not affect distribution compliance because comment Java is a Trial Use Module. quell end # --- GObject --- test /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 41 expected_severity failed resolution Test suite deficiency marker g_type_class_unref_uncached comment It was not taken into account that the callbacks should be called for each class that is unref'd, not only for the one of interest in this test.
comment The problem should be fixed in a newer version of the test suite. quell end test /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 1 expected_severity unresolved resolution Test suite deficiency comment It was not taken into account that reference to the class may be not existed in class_init function. So g_class_peek may return NULL.
comment The problem should be fixed in a newer version of the test suite. quell dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 2 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 3 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 4 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 5 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 6 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 11 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 12 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 13 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 14 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 15 dup /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject 16 end test /gobject-t2c/tests/gobject_type_module/gobject_type_module 5 expected_severity unresolved resolution Known problem comment This failure occures due to the following problem:
comment Glib dynamic type system crashes when one calls g_type_add_interface_{static|dynamic} with interface, comment registered via g_type_register_dynamic.
comment Detailed description of this problem is available here. dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 34 dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 37 dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 38 dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 39 dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 40 dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 41 end # --- Gdk-pixbuf --- test /gdk-pixbuf-t2c/tests/InlineData/InlineData 17 expected_severity failed resolution Known problem marker #error MY_IMAGE_RUN_LENGTH_DECODE comment This failure occurs due to the following problem:
comment gdk_pixdata_to_csource does not always add a macro for rle stream decoding to the code
comment Detailed description of this problem is available here. end test /gdk-pixbuf-t2c/tests/InlineData/InlineData 16 expected_severity failed resolution Known problem marker make error output start comment This failure occurs due to the following problem:
comment LSB SDK is not installed or some parts of it are missing
comment Please install appropriate LSB SDK package. You can download it from this site. quell dup /gdk-pixbuf-t2c/tests/InlineData/InlineData 17 dup /gdk-pixbuf-t2c/tests/InlineData/InlineData 18 dup /gdk-pixbuf-t2c/tests/InlineData/InlineData 19 end test /gdk-pixbuf-t2c/tests/SubPixbuf/SubPixbuf 2 expected_severity failed resolution Known problem marker gdk_pixbuf_saturate_and_pixelate comment This failure occurs due to the following problem:
comment gdk_pixbuf_saturate_and_pixelate may corrupt memory
comment Detailed description of this problem is available here. quell end test /gdk-pixbuf-t2c/tests/Scaling/Scaling 24 expected_severity failed resolution Known problem marker GDK_INTERP_HYPER comment This failure occurs due to the following problem:
comment Images change when scaled 1:1 with GDK_INTERP_HYPER filter
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/Scaling/Scaling 49 end test /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 8 expected_severity failed resolution Known problem marker license comment This failure occurs due to the following problem:
comment gdk_pixbuf_format_get_license returns NULL for any of the loaders
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 9 dup /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 10 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 3 end test /gdk-pixbuf-t2c/tests/Animation/Animation 8 expected_severity failed resolution Known problem marker GDK_PIXBUF_ERROR_CORRUPT_IMAGE comment This failure occurs due to the following problem:
comment gdk_pixbuf loader 'ani' does not always set error on failure
comment Detailed description of this problem is available here. quell end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 35 expected_severity failed resolution Known problem marker area_updated comment This failure occurs due to the following problem:
comment "area-updated" signal is emitted with incorrect parameters
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 42 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 43 end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 48 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment gdk_pixbuf_loader_set_size does not always set image size correctly
comment Detailed description of this problem is available here. dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 49 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 50 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 51 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 52 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 53 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 33 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 35 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 36 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 37 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 43 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 44 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 51 dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 52 end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 34 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment gdk_pixbuf_loader_get_pixbuf returns different results if gdk_pixbuf_loader_set_size has been called
comment Detailed description of this problem is available here. quell end test /gdk-pixbuf-t2c/tests/Scaling/Scaling 69 expected_severity failed resolution Known problem marker gdk_pixbuf_composite_color comment This failure occurs due to the following problem:
comment The gdk_pixbuf_composite_color function uses wrong checkboard offset
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/Scaling/Scaling 70 end test /gdk-pixbuf-t2c/tests/Utils/Utils 13 expected_severity failed resolution Known problem marker gdk_pixbuf_saturate_and_pixelate comment This failure occurs due to the following problem:
comment gdk_pixbuf_saturate_and_pixelate changes not only saturation but also hue of the colour
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/Utils/Utils 14 end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 44 expected_severity failed resolution Known problem marker gdk_pixbuf_animation_iter_on_currently_loading_frame comment This failure occurs due to the following problem:
comment gdk_pixbuf_animation_iter_on_currently_loading_frame returns FALSE while the contents of the frame are still subject to change
comment Detailed description of this problem is available here. quell end test /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 8 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment Incorrect handling of "tEXt::key" parameters
comment Detailed description of this problem is available here. dup /gdk-pixbuf-t2c/tests/Structure/Structure 7 end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 20 expected_severity failed resolution Known problem marker gdk_pixbuf_loader_close comment This failure occurs due to the following problem:
comment The relationship between the return value and the set error is unclear in the description of gdk_pixbuf_loader_close
comment Detailed description of this problem is available here. quell dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 21 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 22 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 23 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 24 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 25 end test /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 29 expected_severity unresolved resolution Known problem marker Couldn't recognize the image file format comment This failure occurs due to the following problem:
comment

A custom pixbuf loader required by the tests is missing. Normally, it should comment have been set up during the installation of the package containing this test comment suite. Please check install logs for the package.

comment See the description of this issue for details.
comment To get around this problem, you can try the following:
comment
  1. Find a directory on your system that contains configuration files for comment GTK+-2.0. It is usually something like /etc/gtk-2.0, /etc/opt/gnome/gtk-2.0, comment /etc/gtk-2.0/x86_64-redhat-linux-gnu, etc.
    2. comment
  2. If there is no file with a name like gdk-pixbuf.loaders, comment gdk-pixbuf64.loaders or anything similar in this directory, create file gdk-pixbuf.loaders there. comment You may also try gdk-pixbuf64.loaders on 64-bit systems, or some other comment platform-specific variant.
    3. comment
  3. Change current directory to comment /opt/lsb/test/desktop-t2c/gdk-pixbuf-t2c/testdata/ModuleInterface_external and
    comment execute install_loader.sh -u (as root). This should populate the comment .loaders file with the list of default loaders.
    4. comment
  4. Execute install_loader.sh (as root). This should install the custom comment image loader.
    5. comment
  5. Re-run the tests.
dup /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 30 dup /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 31 dup /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 32 dup /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 33 dup /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 34 end test /gdk-pixbuf-t2c/tests/GdkPixbufLoader_external/GdkPixbufLoader_external 1 expected_severity uninitiated resolution Known problem marker Loader with name "checkboard" is not installed although it is required for this test comment This failure occurs due to the following problem:
comment

A custom pixbuf loader required by the tests is missing. Normally, it should comment have been set up during the installation of the package containing this test comment suite. Please check install logs for the package.

comment See the description of this issue for details.
comment To get around this problem, you can try the following:
comment
  1. Find a directory on your system that contains configuration files for comment GTK+-2.0. It is usually something like /etc/gtk-2.0, /etc/opt/gnome/gtk-2.0, comment /etc/gtk-2.0/x86_64-redhat-linux-gnu, etc.
    2. comment
  2. If there is no file with a name like gdk-pixbuf.loaders, comment gdk-pixbuf64.loaders or anything similar in this directory, create file gdk-pixbuf.loaders there. comment You may also try gdk-pixbuf64.loaders on 64-bit systems, or some other comment platform-specific variant.
    3. comment
  3. Change current directory to comment /opt/lsb/test/desktop-t2c/gdk-pixbuf-t2c/testdata/ModuleInterface_external and
    comment execute install_loader.sh -u (as root). This should populate the comment .loaders file with the list of default loaders.
    4. comment
  4. Execute install_loader.sh (as root). This should install the custom comment image loader.
    5. comment
  5. Re-run the tests.
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader_external/GdkPixbufLoader_external 2 dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader_external/GdkPixbufLoader_external 3 end test /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 1 expected_severity uninitiated resolution Known problem marker Failed to load a custom pixbuf loader required by the tests comment This failure occurs due to the following problem:
comment

A custom pixbuf loader required by the tests is missing. Normally, it should comment have been set up during the installation of the package containing this test comment suite. Please check install logs for the package.

comment See the description of this issue for details.
comment To get around this problem, you can try the following:
comment
  1. Find a directory on your system that contains configuration files for comment GTK+-2.0. It is usually something like /etc/gtk-2.0, /etc/opt/gnome/gtk-2.0, comment /etc/gtk-2.0/x86_64-redhat-linux-gnu, etc.
    2. comment
  2. If there is no file with a name like gdk-pixbuf.loaders, comment gdk-pixbuf64.loaders or anything similar in this directory, create file gdk-pixbuf.loaders there. comment You may also try gdk-pixbuf64.loaders on 64-bit systems, or some other comment platform-specific variant.
    3. comment
  3. Change current directory to comment /opt/lsb/test/desktop-t2c/gdk-pixbuf-t2c/testdata/ModuleInterface_external and
    comment execute install_loader.sh -u (as root). This should populate the comment .loaders file with the list of default loaders.
    4. comment
  4. Execute install_loader.sh (as root). This should install the custom comment image loader.
    5. comment
  5. Re-run the tests.
dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 2 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 3 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 4 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 5 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 6 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 7 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 8 dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 9 end #---- FreeType ---- test /freetype-t2c/tests/type_1_tables/type_1_tables 12 expected_severity failed resolution Known problem marker unique_id comment This failure occurs due to the following problem:
comment FT_Get_PS_Font_Private returns wrong unique_id values
comment Detailed description of this problem is available here. quell dup /freetype-t2c/tests/type_1_tables/type_1_tables 13 end test /freetype-t2c/tests/opentype_validation/opentype_validation 1 expected_severity uninitiated resolution Known problem marker OpenType validation module is not available comment This failure occurs due to the following problem:
comment OpenType validation module is not available by default in certain versions of FreeType. quell dup /freetype-t2c/tests/opentype_validation/opentype_validation 2 dup /freetype-t2c/tests/opentype_validation/opentype_validation 3 dup /freetype-t2c/tests/opentype_validation/opentype_validation 4 dup /freetype-t2c/tests/opentype_validation/opentype_validation 5 dup /freetype-t2c/tests/opentype_validation/opentype_validation 6 dup /freetype-t2c/tests/opentype_validation/opentype_validation 7 dup /freetype-t2c/tests/opentype_validation/opentype_validation 8 dup /freetype-t2c/tests/opentype_validation/opentype_validation 9 dup /freetype-t2c/tests/opentype_validation/opentype_validation 10 dup /freetype-t2c/tests/opentype_validation/opentype_validation 11 dup /freetype-t2c/tests/opentype_validation/opentype_validation 12 dup /freetype-t2c/tests/opentype_validation/opentype_validation 13 dup /freetype-t2c/tests/opentype_validation/opentype_validation 14 dup /freetype-t2c/tests/opentype_validation/opentype_validation 15 dup /freetype-t2c/tests/opentype_validation/opentype_validation 16 dup /freetype-t2c/tests/opentype_validation/opentype_validation 17 dup /freetype-t2c/tests/opentype_validation/opentype_validation 18 dup /freetype-t2c/tests/opentype_validation/opentype_validation 19 dup /freetype-t2c/tests/opentype_validation/opentype_validation 20 dup /freetype-t2c/tests/opentype_validation/opentype_validation 21 dup /freetype-t2c/tests/opentype_validation/opentype_validation 22 dup /freetype-t2c/tests/opentype_validation/opentype_validation 23 dup /freetype-t2c/tests/opentype_validation/opentype_validation 24 dup /freetype-t2c/tests/opentype_validation/opentype_validation 25 dup /freetype-t2c/tests/opentype_validation/opentype_validation 26 dup /freetype-t2c/tests/opentype_validation/opentype_validation 27 end test /freetype-t2c/tests/base_interface_basic_glyph/base_interface_basic_glyph 19 expected_severity failed resolution Known problem marker FT_Get_Name_Index comment This failure occurs due to the following problem:
comment FT_Get_Name_Index returns 0 instead of a glyph index
comment Detailed description of this problem is available here. quell dup /freetype-t2c/tests/base_interface_basic_glyph/base_interface_basic_glyph 20 dup /freetype-t2c/tests/base_interface_basic_glyph/base_interface_basic_glyph 21 dup /freetype-t2c/tests/base_interface_basic_glyph/base_interface_basic_glyph 22 end test /freetype-t2c/tests/multiple_masters/multiple_masters 4 expected_severity failed resolution Known problem marker FreeType computes meaningful default values for MM comment This failure occurs due to the following problem:
comment FT_Get_MM_Var returns incorrect default values for design coordinates
comment Detailed description of this problem is available here. quell dup /freetype-t2c/tests/multiple_masters/multiple_masters 5 dup /freetype-t2c/tests/multiple_masters/multiple_masters 6 end test /freetype-t2c/tests/bitmap_handling/bitmap_handling 20 expected_severity failed resolution Known problem marker FT_Bitmap_Convert comment This failure occurs due to the following problem:
comment FT_Bitmap_Convert does not handle pixel modes FT_PIXEL_MODE_LCD and FT_PIXEL_MODE_LCD_V
comment Detailed description of this problem is available here. dup /freetype-t2c/tests/bitmap_handling/bitmap_handling 21 end test /freetype-t2c/tests/pfr_fonts/pfr_fonts 5 expected_severity failed resolution Known problem marker If the input face is not a PFR, this function will return an error comment This failure occurs due to the following problem:
comment FT_Get_PFR_Metrics returns incorrect value for non-PFR fonts
comment Detailed description of this problem is available here. dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 8 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 11 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 14 end test /freetype-t2c/tests/pfr_fonts/pfr_fonts 6 expected_severity unresolved resolution Known problem marker signal 11 comment This failure occurs due to the following problem:
comment Calling FT_Get_PFR_Metrics for a non-PFR font causes segmentation fault
comment Detailed description of this problem is available here. dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 7 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 9 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 10 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 12 dup /freetype-t2c/tests/pfr_fonts/pfr_fonts 13 end test /freetype-t2c/tests/x11_font_format/x11_font_format 10 expected_severity unresolved resolution Known problem marker Checked requirement marker FT_Get_X11_Font_Format.01 comment This failure occurs due to the following problem:
comment Operations with some Type 42 fonts cause invalid free()
comment Detailed description of this problem is available here. end ## C++ # ??? test /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 103 expected_severity failed resolution Known problem marker uncaught_exception.02 comment This failure occurs due to the following problem:
comment std::uncaught_exception() returns wrong value after entering terminate() in some cases
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 105 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 106 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 108 end # Needs interpretation by JTC1. - JAL - test /libstdcxx-t2c/tests/codecvt/codecvt 24 expected_severity failed resolution Known problem marker _mbstate.do comment This failure occurs due to the following problem:
comment codecvt::do_in/do_out functions return "ok" when the output sequence has zero length
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/codecvt/codecvt 27 dup /libstdcxx-t2c/tests/codecvt/codecvt 29 end # Bug accepted, no progress on a fix. - JAL - test /libstdcxx-t2c/tests/time_get/time_get 37 expected_severity failed resolution Known problem marker do_get_weekday comment This failure occurs due to the following problem:
comment time_get<>::do_get_weekday does not always recognize full names of weekdays
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/time_get/time_get 38 dup /libstdcxx-t2c/tests/time_get/time_get 39 dup /libstdcxx-t2c/tests/time_get/time_get 40 end # Fixed for gcc 4.4.0 - JAL - test /libstdcxx-t2c/tests/num_put_do_put5/num_put_do_put5 9 expected_severity failed resolution Known problem marker do_put_pvoid comment This failure occurs due to the following problem:
comment num_put<>::do_put(void*) performs padding incorrectly when adjustfield==internal
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_put_do_put5/num_put_do_put5 18 end # Fixed for gcc 4.4.0 - JAL - test /libstdcxx-t2c/tests/num_put_do_put7/num_put_do_put7 55 expected_severity failed resolution Known problem marker do_put_bool comment This failure occurs due to the following problem:
comment num_put<>::do_put(bool) performs 'internal' padding incorrectly when boolalpha==true
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_put_do_put7/num_put_do_put7 58 dup /libstdcxx-t2c/tests/num_put_do_put7/num_put_do_put7 61 dup /libstdcxx-t2c/tests/num_put_do_put7/num_put_do_put7 64 end # Possibly fixed for gcc 4.4.0. - JAL - test /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 15 expected_severity failed resolution Known problem marker do_get_bool comment This failure occurs due to the following problem:
comment num_get<>::do_get(bool) sets eofbit flag incorrectly when boolalpha == true
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 16 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 21 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 22 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 33 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 34 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 36 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 38 end # Claimed fixed with other bugfix, for gcc 4.4.0 - JAL - test /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 28 expected_severity failed resolution Known problem marker do_get_bool comment This failure occurs due to the following problem:
comment Wrong behaviour of num_get<>::do_get(bool) in the case when one target sequence is a prefix of the other one
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 29 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 31 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 32 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 35 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 37 end # Missing linuxtesting.org report. - JAL - test /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 3 expected_severity failed resolution Known problem marker String is marker but should be marker val is unchanged comment This failure occurs due to the following problem:
comment Contradiction of requirements for num_get<>::do_get() functions concerning setting an error flag and changing the value of 'val'
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 4 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 5 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 8 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 9 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 10 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 13 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 14 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 15 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 18 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 19 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 20 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 23 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 24 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 25 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 28 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 29 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 30 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 33 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 34 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 35 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 38 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 39 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 40 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 43 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 44 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 47 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 48 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 52 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 53 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 57 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 58 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 62 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 63 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 67 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 68 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 72 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 73 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 77 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 78 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 81 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 84 # dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 4 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 7 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 12 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 15 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 20 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 23 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 28 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 31 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 36 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 39 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 44 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 47 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 52 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 55 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 60 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 63 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 68 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 73 end test /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 3 expected_severity failed resolution Known problem marker String is marker but should be marker but it is 0 comment This failure occurs due to the following problem:
comment Contradiction of requirements for num_get<>::do_get() functions concerning setting an error flag and changing the value of 'val'
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 4 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 5 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 8 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 9 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 10 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 13 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 14 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 15 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 18 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 19 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 20 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 23 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 24 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 25 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 28 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 29 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 30 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 33 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 34 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 35 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 38 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 39 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 40 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 43 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 44 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 47 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 48 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 52 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 53 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 57 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 58 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 62 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 63 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 67 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 68 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 72 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 73 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 77 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 78 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 81 dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 84 # dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 4 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 7 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 12 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 15 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 20 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 23 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 28 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 31 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 36 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 39 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 44 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 47 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 52 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 55 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 60 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 63 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 68 dup /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 73 end test /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 81 expected_severity failed resolution Known problem marker String is marker but should be marker but it is 0x5. comment This failure occurs due to the following problem:
comment Contradiction of requirements for num_get<>::do_get() functions concerning setting an error flag and changing the value of 'val'
comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 84 end test /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 37 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment Current working draft for C++ specifies that negative values are accepted by num_get<>::do_get() for unsigned types.
comment But ISO C++ standard, referred to by LSB, states that such values should not be accepted.
comment gcc 4.4 and newer implement current working draft.
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 40 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 41 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 44 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 45 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 48 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 53 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 56 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 57 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 60 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 61 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 64 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 67 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 72 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 77 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 82 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 87 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 92 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 98 dup /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 102 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 136 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 138 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 139 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 141 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 142 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 144 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 148 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 150 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 151 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 153 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 154 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 156 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 162 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 164 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 166 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 167 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 169 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 171 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 172 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 174 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 176 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 177 # dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 179 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 181 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 187 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 189 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 191 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 192 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 194 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 196 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 197 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 199 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 201 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 202 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 204 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 206 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 211 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 214 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 215 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 218 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 219 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 222 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 227 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 230 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 231 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 234 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 235 dup /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 238 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 18 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 19 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 20 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 24 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 25 dup /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 26 end test /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 16 expected_severity failed resolution Known problem (waived) marker should be suitably aligned comment This failure occurs due to the following problem:
comment ::operator new() returns misaligned pointer on PPC32 and S390
comment Detailed description of this problem is available here. quell dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 17 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 18 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 34 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 35 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 36 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 47 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 48 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 58 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 59 end test /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 46 expected_severity unresolved resolution No problem marker Cannot restrict memory by size marker Current memory usage probably exceeds this value. comment This failure occurs due to the following problem:
comment Cannot force new operator with some argument to fail allocate memory using setrlimit,
comment because currently memory usage of memory-subsystem of libstdcxx exceeds this value. quell dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 47 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 48 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 49 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 50 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 57 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 58 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 59 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 60 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 61 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 71 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 72 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 73 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 74 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 81 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 82 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 83 dup /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport 84 end test /libstdcxx-t2c/tests/money_put/money_put 41 expected_severity failed resolution Known problem marker Resulting stream content is marker 2,222" comment This failure occurs due to the following problem:
comment Value CHAR_MAX in grouping string isn't treated as disabling successive grouping (on architectures with char ~ signed char). comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/money_put/money_put 42 end test /libstdcxx-t2c/tests/money_get/money_get 106 expected_severity failed resolution Known problem marker rest of stream is marker ",345". comment This failure occurs due to the following problem:
comment string(1, CHAR_MAX) as grouping string isn't treated as disabling grouping at al (on architectures with char ~ signed char). comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/money_get/money_get 108 dup /libstdcxx-t2c/tests/money_get/money_get 110 dup /libstdcxx-t2c/tests/money_get/money_get 112 end test /libstdcxx-t2c/tests/money_get/money_get 189 expected_severity failed resolution Known problem marker rest of stream is marker "". comment This failure occurs due to the following problem:
comment Implementation reads decimal point when frac_digits() returns non-positive value. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/money_get/money_get 190 dup /libstdcxx-t2c/tests/money_get/money_get 191 dup /libstdcxx-t2c/tests/money_get/money_get 192 end test /libstdcxx-t2c/tests/money_get/money_get 119 expected_severity failed resolution Known problem marker If input sequence is invalide for monetary value, doesn't change units or digits comment This failure occurs due to the following problem:
comment Implementation stores monetary value when grouping is incorrect. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/money_get/money_get 128 dup /libstdcxx-t2c/tests/money_get/money_get 137 dup /libstdcxx-t2c/tests/money_get/money_get 146 dup /libstdcxx-t2c/tests/money_get/money_get 205 dup /libstdcxx-t2c/tests/money_get/money_get 207 end test /libstdcxx-t2c/tests/locale/locale 53 expected_severity failed resolution Known problem marker LC_TYPE=* comment This failure occurs due to the following problem:
comment locale(const locale& other, const const locale& one, locale::category) may create named locale from unnamed and named ones. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/locale/locale 54 dup /libstdcxx-t2c/tests/locale/locale 55 dup /libstdcxx-t2c/tests/locale/locale 56 end test /libstdcxx-t2c/tests/locale/locale 80 expected_severity failed resolution Known problem marker Last argument, passed to locale::global(), has name comment This failure occurs due to the following problem:
comment locale(const locale& other, const const locale& one, locale::category) may create named locale from unnamed and named ones. comment Detailed description of this problem is available here. end test /libstdcxx-t2c/tests/locale/locale 82 expected_severity failed resolution Known problem marker LC_TIME=ru_RU_test comment This failure occurs due to the following problem:
comment locale::name return string, where locale names for LC_TIME and LC_COLLATE catergories are confused. comment Detailed description of this problem is available here. end test /libstdcxx-t2c/tests/locale/locale 86 expected_severity failed resolution Known problem marker LC_COLLATE=ru_RU_test comment This failure occurs due to the following problem:
comment locale::name return string, where locale names for LC_TIME and LC_COLLATE catergories are confused. comment Detailed description of this problem is available here. end test /libstdcxx-t2c/tests/locale/locale 83 expected_severity failed resolution Known problem marker thousands_sep marker moneypunct comment This failure occurs due to the following problem:
comment When locale(char const*) compounds categories from different locales, some categories from C locale may differ from expeted ones. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/locale/locale 85 dup /libstdcxx-t2c/tests/locale/locale 87 end test /libstdcxx-t2c/tests/locale/locale 88 expected_severity failed resolution Known problem marker thousands_sep marker numpunct comment This failure occurs due to the following problem:
comment When locale(char const*) compounds categories from different locales, some categories from C locale may differ from expeted ones. comment Detailed description of this problem is available here. end test /libstdcxx-t2c/tests/locale/locale 84 expected_severity failed resolution Known problem marker monetary comment This failure occurs due to the following problem:
comment When locale(char const*) compounds categories from different locales, some categories from non-"C" locale may be broken. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/locale/locale 36 dup /libstdcxx-t2c/tests/locale/locale 35 dup /libstdcxx-t2c/tests/locale/locale 71 end test /libstdcxx-t2c/tests/locale/locale 84 expected_severity unresolved resolution Known problem comment This failure occurs due to the following problem:
comment When locale(char const*) compounds categories from different locales, some categories from non-"C" locale may be broken. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/locale/locale 36 dup /libstdcxx-t2c/tests/locale/locale 35 dup /libstdcxx-t2c/tests/locale/locale 71 end test /libstdcxx-t2c/tests/facets_common/facets_common 396 expected_severity unresolved resolution Known problem marker SIGSEGV comment This failure occurs due to the following problem:
comment Constructor locale(locale const&, char const*, locale::category) creates broken locale. comment Detailed description of this problem is available here. dup /libstdcxx-t2c/tests/facets_common/facets_common 397 dup /libstdcxx-t2c/tests/facets_common/facets_common 398 dup /libstdcxx-t2c/tests/facets_common/facets_common 399 end test /libstdcxx-t2c/tests/basic_istream/basic_istream 322 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment This version of libstdcxx implements the resolution of the defect report comment "136. seekp, seekg setting wrong streams?"
comment That is, the discrepancy between the current version of the ISO C++ standard and the implementation is intentional.
comment See also the comments from gcc team. quell dup /libstdcxx-t2c/tests/basic_istream/basic_istream 324 dup /libstdcxx-t2c/tests/basic_istream/basic_istream 329 dup /libstdcxx-t2c/tests/basic_istream/basic_istream 330 end test /libstdcxx-t2c/tests/basic_ostream/basic_ostream 314 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment This version of libstdcxx implements the resolution of the defect report comment "136. seekp, seekg setting wrong streams?"
comment That is, the discrepancy between the current version of the ISO C++ standard and the implementation is intentional.
comment See also the comments from gcc team. quell dup /libstdcxx-t2c/tests/basic_ostream/basic_ostream 316 dup /libstdcxx-t2c/tests/basic_ostream/basic_ostream 361 dup /libstdcxx-t2c/tests/basic_ostream/basic_ostream 362 end test /libstdcxx-t2c/tests/operator_shift_left/operator_shift_left 5 expected_severity failed resolution Known problem comment This failure occurs due to the following problem:
comment This version of libstdcxx implements the resolution of the defect report comment "136. seekp, seekg setting wrong streams?"
comment That is, the discrepancy between the current version of the ISO C++ standard and the implementation is intentional.
comment See also the comments from gcc team. quell dup /libstdcxx-t2c/tests/operator_shift_left/operator_shift_left 6 end test /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 253 expected_severity failed resolution Known problem marker should return NULL comment This failure occurs due to the following problem:
comment This version of libstdcxx implements the resolution of the defect report comment "596. 27.8.1.3 Table 112 omits "a+" and "a+b" modes"
comment That is, the discrepancy between the current version of the ISO C++ standard and the implementation is intentional. quell dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 256 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 335 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 338 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 258 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 263 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 340 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 345 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 260 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 265 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 342 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 347 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 268 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 274 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 350 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 356 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 270 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 276 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 352 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 358 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 279 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 283 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 361 dup /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 365 end ## Shallow test /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 6 expected_severity unresolved resolution Known problem marker QGLWidget::grabFrameBuffer(bool) marker unexpected signal 11 comment This error appears if the test fails to create an OpenGL context. comment See bug comment 2406 in the LSB Bugzilla for details. quell end test /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 21 expected_severity unresolved resolution Known problem marker QGLWidget::renderText(double, double, double, QString const&, QFont const&, int) marker unexpected signal comment This error appears if the test fails to create an OpenGL context. comment See bug comment 2406 in the LSB Bugzilla for details. quell end test /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 41 expected_severity unresolved resolution Known problem marker QGLWidget::renderText(int, int, QString const&, QFont const&, int) marker unexpected signal comment This error appears if the test fails to create an OpenGL context. comment See bug comment 2406 in the LSB Bugzilla for details. quell end test /Qt3_OpenGL-t2c/tests/QGLContext/QGLContext 16 expected_severity unresolved resolution Known problem marker QGLContext::generateFontDisplayLists(QFont const&, int) marker unexpected signal 11 comment This error appears if the test fails to create an OpenGL context, comment which can happen when running under Xvfb. See comment bug 2406 comment in the LSB Bugzilla for details. quell end ## Olver test /olver/util/search/tests/insque_spec 028 expected_severity failed resolution Known problem marker Registered bug: bug028(insque) comment The insque(element, pred) function shall insert the element pointed to by comment element into a queue immediately after the element pointed to by pred. comment According to LSB, if the queue is to be used as a linear list, invoking comment insque(element, NULL), where element is the initial element of the queue, comment shall initialize the forward and backward pointers of element to null pointers. comment But this function causes the segmentation fault if the second parameter is NULL. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0028. end test /olver/process/meta/tests/setuid_spec 102 expected_severity failed resolution Known problem marker Registered bug: bug102(setuid) comment The LSB specification says nothing that setreuid() function may comment change the saved set-user-ID value. comment But actually, if the real user ID is set to or comment the effective user ID is set to a value not equal to comment the previous real user ID, the saved set-user-ID will be set to the new effective user ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/process/meta/tests/setreuid_spec 103 expected_severity failed resolution Known problem marker Registered bug: bug103(setreuid) comment The LSB specification says nothing that setreuid() function may comment change the saved set-user-ID value. comment But actually, if the real user ID is set to or comment the effective user ID is set to a value not equal to comment the previous real user ID, the saved set-user-ID will be set to the new effective user ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/process/meta/tests/setgid_spec 104 expected_severity failed resolution Known problem marker Registered bug: bug104(setgid) comment The LSB specification says nothing that setregid() function may comment change the saved set-group-ID value. comment But actually, if the real group ID is set to or comment the effective group ID is set to a value not equal to comment the previous real group ID, the saved set-group-ID will be set to the new effective group ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/process/meta/tests/setregid_spec 106 expected_severity failed resolution Known problem marker Registered bug: bug106(setregid) comment The LSB specification says nothing that setregid() function may comment change the saved set-group-ID value. comment But actually, if the real group ID is set to or comment the effective group ID is set to a value not equal to comment the previous real group ID, the saved set-group-ID will be set to the new effective group ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/process/resources/tests/ulimit_spec 167 expected_severity failed resolution Known problem marker Registered bug: bug167(ulimit) comment The ulimit() function shall control process limits. The process limits that can be controlled comment by this function include the maximum size of a single file that can be written. comment According to LSB, the return value shall be the integer part of the soft file size comment limit divided by 512. comment But on the target machine the function always returns 0 upon successful completion. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0167. end test /olver/system/user/tests/getgrouplist_spec 177 expected_severity failed resolution Known problem marker Registered bug: bug177(getgrouplist) comment The getgrouplist() function shall fill in the supplied array with the supplementary groups for the comment specified user. According to LSB, if such user doesn't exist function shall return 0. comment But it returns 1 on the system under test. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0177. quell end test /olver/fs/name/tests/basename_spec 207 expected_severity failed resolution Known problem marker Registered bug: bug207(basename) comment The basename() function shall take the pathname pointed to by path comment and return a pointer to the final component of the pathname, comment deleting any trailing '/' characters. comment But the input "err////" causes segmentation fault. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0207. end test /olver/ncurses/move/tests/mvcur_spec 313 expected_severity failed resolution Known problem marker Registered bug: bug313(mvcur) comment According to LSB, if screen position (newrow, newcol) is not a valid address for comment the terminal in use, mvcur(int xpos, int ypos) function call to this cursor position should fail comment (mvcur() is the function from Ncurses library that moves the cursor), but error doesn't occur on comment inputs (-1000000, -1000000), (10000000, 10000000). comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0313. quell end test /olver/ncurses/line/tests/ripoffline_spec 319 expected_severity failed resolution Known problem marker Registered bug: bug319(ripoffline) comment Function ripoffline() is one from Ncurses library and reserves one screen line for use by comment the application (for example, for menu). According to LSB, up to five lines can be ripped off comment for use by the application and calls to ripoffline() above this limit have no effect but report comment success. comment But this function on sixth call returns error value -1. This contradicts the standard. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0319. quell end test /olver/ncurses/window/tests/refresh_spec 329 expected_severity failed resolution Known problem marker Registered bug: bug329(chgat) comment Function chgat() is one from Ncurses library and it changes renditions (for example, color, bold, comment italic attributes etc.) of characters in a window. comment This function doesn't work if it is applied to the text that was output to the window and this comment window was refreshed. It still works if it is applied after the text was output to the window comment but before refresh() call. This behavior is unclear from standard. comment Additional information about this bug may be found at bug-ncurses@gnu.org, archive is comment http://www.nabble.com/chgat%28%29-function-does-not-work-correctly-after-refresh%28%29-tf3777004.html. comment This bug has been fixed since patch 20060715 for ncurses 5.5. quell end test /olver/ncurses/slk/tests/slk_label_spec 342 expected_severity failed resolution Known problem marker Registered bug: bug342(slk_label) comment Upon successful completion, slk_label(labnum) function from ncurses library comment returns the requested label with number labnum with leading and trailing comment blanks stripped. comment But on the target machine there are outputs with unstripped blanks. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0342. quell end test /olver/ncurses/misc/tests/keyname_spec 357 expected_severity failed resolution Known problem marker Registered bug: bug357(keyname) comment The keyname() function generates a character string whose value describes the key comment specified as the argument of the functions. comment The meta-character notation in function keyname() from ncurses library, when running it comment with meta-character parameter, shall be used only if meta-characters are enabled comment (according to the LSB standard). But it is used irrespectively of enabling of comment meta-characters. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0357. quell end test /olver/time/time/tests/stime_spec 377 expected_severity failed resolution Known problem marker Registered bug: bug377(stime) comment The stime() function shall set the system's idea of the time and date to the time comment referenced by function argument. According to LSB, if this argument is NULL then comment stime() shall set error code to EINVAL. comment But it sets error code to EFAULT instead of EINVAL. comment The bug was fixed in libc 2.4. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0377. quell end test /olver/time/conversion/tests/asctime_r_spec 379 expected_severity failed resolution Known problem marker Registered bug: bug379(asctime_r) comment The asctime_r() function converts date and time to a string and returns it. comment According to LSB, if the function is unsuccessful, it should return NULL, comment But on the target machine it returns a string with '?' symbols, for comment example "??? Oct 9 09:09:09 1909". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. quell end test /olver/time/conversion/tests/asctime_spec 380 expected_severity failed resolution Known problem marker Registered bug: bug380(asctime) comment The asctime() function converts date and time to a string and returns it. comment According to LSB, if the function is unsuccessful, it should return NULL, comment But on the target machine it returns a string with '?' symbols, for comment example "??? Oct 9 09:09:09 1909". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. quell end test /olver/util/float/tests/nexttoward_spec 424 expected_severity failed resolution Known problem marker Registered bug: bug424(nexttoward) comment The nexttoward(x, y) function shall compute the next representable floating-point value following comment x in the direction of y. comment The function gives incorrect result on the input (3fffffff ffffffff, 3fffffffffff ffffffff). end test /olver/locale/messages/tests/strerror_spec 443 expected_severity failed resolution Known problem marker Registered bug: bug443(strerror_r) comment According to LSB, the strerror_r() function shall return a pointer to the string corresponding to errno comment and shall place the string with description of the error in the buffer, specified as argument of comment the strerror_r() function. comment But in this buffer no valid error description string was found. comment The problem is a consequence of a bug in LSB SDK, comment which is registered at http://bugs.linuxbase.org/show_bug.cgi?id=1256. comment It was fixed in LSB 3.2. quell end test /olver/util/assert/tests/warnx_spec 486 expected_severity failed resolution Known problem marker Registered bug: bug486(warnx) comment The warnx() function shall display a formatted error message on the standard error stream. comment According to LSB, the formatted error message, the last component of the program name, a colon comment character, a space and a newline character shall be output. comment But on the target machine colon character, and a space are not output after the formatted error comment message. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. quell end test /olver/util/assert/tests/errx_spec 488 expected_severity failed resolution Known problem marker Registered bug: bug488(errx) comment The errx() function shall display a formatted error message on the standard error stream. comment According to LSB, the formatted error message, the last component of the program name, a colon comment character, a space and a newline character shall be output. comment But on the target machine colon character, and a space are not output after the formatted error comment message. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. quell end test /olver/util/assert/tests/verrx_spec 489 expected_severity failed resolution Known problem marker Registered bug: bug489(verrx) comment The verrx() function shall display a formatted error message on the standard error stream. comment According to LSB, the formatted error message, the last component of the program name, a colon comment character, a space and a newline character shall be output. comment But on the target machine colon character, and a space are not output after the formatted error comment message. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. quell end test /olver/math/chyper/tests/cacosh_spec 496 expected_severity failed resolution Known problem marker Registered bug: bug496(cacosh) comment The cacosh() family of functions shall compute the complex arc hyperbolic cosine of comment their argument. comment From mathematical definition of the complex arc hyperbolic cosine there is the comment requirement "cacos(conj(z)) = conj(cacos(z)), where conj(z) is the complex conjugate of z". comment But on the target machine cacosh(-1 + 0*I) = cacosh(-1 - 0*I) = Pi * I. quell end test /olver/signal/sigset/tests/sigandset_spec 4981 expected_severity failed resolution Known problem marker Registered bug: bug498_1(sigandset) comment The sigandset() shall combine the two signal sets (specified as arguments) using a logical AND comment operation and shall place the result in the location supplied as the third argument. comment According to LSB, if one or more of the function arguments is NULL then it shall cause comment EINVAL error. comment But it causes crash on the target machine. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0498. quell end test /olver/signal/sigset/tests/sigorset_spec 4982 expected_severity failed resolution Known problem marker Registered bug: bug498_2(sigorset) comment The sigorset() shall combine the two signal sets (specified as arguments) using a logical OR comment operation and shall place the result in the location supplied as the third argument. comment According to LSB, if one or more of the function arguments is NULL then it shall cause comment EINVAL error. comment But it causes crash on the target machine. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0498. quell end test /olver/signal/sigset/tests/sigisemptyset_spec 4983 expected_severity failed resolution Known problem marker Registered bug: bug498_3(sigisemptyset) comment The sigisemptyset() shall check its argument for empty signal set. comment According to LSB, if argument is NULL then it shall cause EINVAL error. comment But it causes crash on the target machine. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0498. quell end test /olver/pthread/mutex/tests/pthread_mutex_trylock_spec 5011 expected_severity failed resolution Known problem marker Registered bug: bug501_1(pthread_mutexattr) comment Function pthread_mutex_trylock() tries to lock a mutex. It shall return EBUSY error code comment if the mutex could not be acquired because it was already locked. comment But it returns error code EDEADLK. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0501. end test /olver/pthread/mutex/tests/pthread_mutex_trylock_spec 5012 expected_severity failed resolution Known problem marker Registered bug: bug501_2(pthread_mutex_trylock) comment Function pthread_mutex_trylock() tries to lock a mutex. It shall return EBUSY error code comment if the mutex could not be acquired because it was already locked. comment But it returns error code EDEADLK. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0501. end test /olver/math/cexp/tests/csqrt_spec 503 expected_severity failed resolution Known problem marker Registered bug: bug503(csqrt) comment The csqrt() family of functions shall compute the complex square root of z, with a comment branch cut along the negative real axis. Thus the functions shall return result from right comment half-plane. comment But csqrtf(0 - i) returns (-0.7071068 + 0.7071068*I) from left half-plane. comment It leads to the requirement "csqrt(conj(z)) = conj(csqrt(z)), where conj(z) is the comment complex conjugate of z" to be failed. quell end test /olver/process/scheduler/tests/sched_setscheduler_spec 504 expected_severity failed resolution Known problem marker Registered bug: bug504(sched_setscheduler) comment The sched_setscheduler() function shall set the scheduling policy and scheduling parameters of the comment specified process. According to LSB, upon successful completion, the function shall return the former comment scheduling policy of the specified process. comment But it always returns 0 on the target machine. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0504. quell end test /olver/util/format/tests/swprintf_spec 505 expected_severity failed resolution Known problem marker Registered bug: bug505(swprintf) comment According to LSB, on error swprintf() function shall return -1 and set errno global variable. comment On the target machine, swprintf() function returns -1, but doesn't set error code in errno comment global variable. This contradicts LSB standard for this function. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. quell end test /olver/util/format/tests/vswprintf_spec 506 expected_severity failed resolution Known problem marker Registered bug: bug506(vswprintf) comment According to LSB, on error vswprintf() function shall return -1 and set errno global variable. comment On the target machine, vswprintf() function returns -1, but doesn't set error code in errno comment global variable. This contradicts LSB standard for this function. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. quell end test /olver/math/rand/tests/initstate_spec 5111 expected_severity failed resolution Known problem marker Registered bug: bug511_1(initstate) comment The initstate() function handles restarting of random-number generator. comment One of the argument to initstate() function is size of the state array. comment The larger the state array, the more random the numbers. comment According to LSB, values for the amount of state information are 8, 32, 64, 128, and 256 bytes comment and if initstate() is called with size less than 8, it shall return NULL. comment But on the target machine the function doesn't return NULL when called with size less comment than 8. quell end test /olver/math/rand/tests/initstate_spec 5112 expected_severity failed resolution Known problem marker Registered bug: bug511_2(initstate) comment The initstate() function handles restarting of random-number generator. comment According to LSB, upon successful completion, initstate() shall return a pointer to the previous state comment array; otherwise, a null pointer shall be returned. comment But on the target machine the function returns neither a pointer to the previous state, comment nor NULL pointer. quell end test /olver/math/hyper/tests/atanh_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(atanh) comment The atanh(x) family of functions shall compute the inverse hyperbolic tangent of their argument x. comment According to LSB, if the x argument is +1 or -1 then the functions shall fail and comment set error code to ERANGE. comment But on the target machine, these functions set error code EDOM instead of ERANGE comment in this case. quell end test /olver/math/trig/tests/cos_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(cos) comment The cos() family of functions shall compute the cosine of their argument, measured in radians. comment According to LSB, if the x is +-Inf then the function shall fail with EDOM error. comment But on the target machine cos() sets error code EOK instead of EDOM on infinity. quell end test /olver/math/real/tests/drem_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(drem) comment The drem(x, y) family of functions shall return the floating-point remainder r = x-ny when y is non-zero. comment According to LSB, if the x argument is +Inf or -Inf, and the other argument is non-NaN then error code shall comment be set to EDOM. comment But on the target machine, the functions set error code EOK instead of EDOM in this case. quell end test /olver/math/exp/tests/expm1_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(expm1) comment The expm1(x) family of functions shall compute exp(x)-1.0. comment According to LSB, if the correct value would cause overflow, a range error shall occur comment and error code shall be set to ERANGE. comment But on the target machine the functions set error code EOK instead of comment ERANGE when overflow occurs. quell end test /olver/math/real/tests/fdim_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(fdim) comment The fdim(x, y) family of functions shall determine the positive difference between their arguments. comment According to LSB, if the result overflows then fdim() shall fail and shall set ERANGE error code. comment But on the target machine, the functions set error code EOK instead of ERANGE when overflow occurs. quell end test /olver/math/real/tests/fmod_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(fmod) comment The fmod(x, y) family of functions shall return the floating-point remainder of the division of x by y. comment According to LSB, if the x argument is infinite then the functions() shall set error code to EDOM. comment But on the target machine, the functions set error code EOK instead of EDOM when x is infinity. quell end test /olver/math/gamma/tests/lgamma_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(lgamma) comment According to LSB, lgamma(x) family of functions shall set error code to ERANGE if x argument is comment negative integer or zero. comment But on the target machine the functions sets error code EDOM instead of ERANGE on comment zero argument. quell end test /olver/math/gamma/tests/lgamma_r_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(lgamma_r) comment According to LSB, lgamma_r(x) family of functions shall set error code to ERANGE if x argument is comment negative integer or zero. comment But on the target machine the functions sets error code EDOM instead of ERANGE on comment zero argument. quell end test /olver/math/real/tests/llrint_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(llrint) comment The llrint() family of functions shall round their argument to the nearest integer value, comment rounding according to the current rounding direction. comment According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an comment integer then the functions shall set EDOM error code. comment But on the target machine, the functions set error code EOK instead of EDOM in these cases. quell end test /olver/math/real/tests/llround_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(llround) comment The llround() family of functions shall round their argument to the nearest integer value, comment rounding halfway cases away from zero, regardless of the current rounding direction. comment According to LSB, if argument is NaN, +Inf -Inf, or the correct value is not representable as an comment integer then the functions shall set EDOM error code. comment But on the target machine, the functions set error code EOK instead of EDOM in these cases. quell end test /olver/math/real/tests/lrint_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(lrint) comment The lrint() family of functions shall round their argument to the nearest integer value, comment rounding according to the current rounding direction. comment According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an comment integer then the functions shall set EDOM error code. comment But on the target machine, the functions set error code EOK instead of EDOM in these cases. quell end test /olver/math/real/tests/lround_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(lround) comment The lround() family of functions shall round their argument to the nearest integer value, comment rounding halfway cases away from zero, regardless of the current rounding direction. comment According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an comment integer then the functions shall set EDOM error code. comment But on the target machine, the functions set error code EOK instead of EDOM in these cases. quell end test /olver/math/exp/tests/pow_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(pow) comment The pow(x, y) family of functions shall compute the value of x raised to the power y. comment According to LSB, if x is +-0 and y is negative the functions shall fail and set error code comment to ERANGE. comment But on the target machine, the functions set error code EDOM instead of ERANGE in this comment case. quell end test /olver/math/real/tests/remainder_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(remainder) comment The remainder(x, y) family of functions shall return the floating-point remainder r = x-ny when y is non-zero. comment According to LSB, if the x argument is +Inf or -Inf, and the other argument is non-NaN then error code shall comment be set to EDOM. comment But on the target machine, the functions set error code EOK instead of EDOM in this case. quell end test /olver/math/real/tests/remquo_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(remquo) comment The remquo(x, y, quo) family of functions shall return the floating-point remainder r = x-ny when y is non-zero comment und update quo variable. comment According to LSB, if the x argument is +Inf, -Inf, or the y argument is +0 or -0 and the other argument is non-NaN. comment then error code shall be set to EDOM. comment But on the target machine, the functions set error code EOK instead of EDOM in these cases. quell end test /olver/math/trig/tests/sin_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(sin) comment The sin() family of functions shall compute the sine of their argument, measured in radians. comment According to LSB, if the x is +-Inf then the function shall fail with EDOM error. comment But on the target machine sin() sets error code EOK instead of EDOM on infinity. quell end test /olver/math/trig/tests/tan_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(tan) comment The tan() family of functions shall compute the tangent of their argument, measured in radians. comment According to LSB, if the x is +-Inf then the function shall fail with EDOM error. comment But on the target machine tan() sets error code EOK instead of EDOM on infinity. quell end test /olver/math/gamma/tests/tgamma_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(tgamma) comment The tgamma(x) family of functions shall compute the mathematical gamma() function of x. comment According to LSB, if x is negative infinity then a domain error shall occur and error comment code shall be set to EDOM. comment But on the target machine, the functions set error code EOK instead of EDOM. quell end test /olver/math/bessel/tests/y0_spec 512 expected_severity failed resolution Known problem marker Registered bug: bug512(y0) comment The y0() function is Bessel function of the second kind. comment According to LSB, if the value of the argument is zero then ERANGE comment error shall occur. comment But on the target machine the function sets error code EDOM comment instead of ERANGE on an input 0. quell end test /olver/math/exp/tests/log1p_spec 5121 expected_severity failed resolution Known problem marker Registered bug: bug512_1(log1p) comment The log1p(x) family of functions shall compute log(1.0 + x). comment According to LSB, the functions shall fail if argument is less than -1 comment and set error code to EDOM. comment But on the target machine the functions set error code EOK instead of EDOM if comment the argument is less than -1. quell end test /olver/math/bessel/tests/y1_spec 5121 expected_severity failed resolution Known problem marker Registered bug: bug512_1(y1) comment The y1() function is Bessel function of the second kind. comment According to LSB, if the value of the argument is zero then ERANGE comment error shall occur. comment But on the target machine the function sets error code EDOM comment instead of ERANGE on an input 0. quell end test /olver/math/bessel/tests/yn_spec 5121 expected_severity failed resolution Known problem marker Registered bug: bug512_1(yn) comment The yn() function is Bessel function of the second kind. comment According to LSB, if the value of the argument is zero then ERANGE comment error shall occur. comment But on the target machine the function sets error code EDOM comment instead of ERANGE on an input 0. quell end test /olver/math/exp/tests/log1p_spec 5122 expected_severity failed resolution Known problem marker Registered bug: bug512_2(log1p) comment The log1p(x) family of functions shall compute log(1.0 + x). comment According to LSB, the functions shall fail if argument equals to -1 comment and set error code to ERANGE. comment But on the target machine the functions set error code EOK instead of ERANGE comment in this case. quell end test /olver/math/trig/tests/atan_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(atan) comment At the specified point the inaccuracy of the result of atan() family of functions is more then comment 20 bits from the end of the floating point number. quell end test /olver/math/trig/tests/cos_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(cos) comment At the specified point the inaccuracy of the result of cos() family of functions is more then comment 20 bits from the end of the floating point number. quell end test /olver/math/bessel/tests/j0_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(j0) comment The j0() function is Bessel function of the first kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/bessel/tests/j1_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(j1) comment The j1() function is Bessel function of the first kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/bessel/tests/jn_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(jn) comment The jn() function is Bessel function of the first kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/trig/tests/sin_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(sin) comment At the specified point the inaccuracy of the result of sin() family of functions is more then comment 20 bits from the end of the floating point number. quell end test /olver/math/trig/tests/sincos_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(sincos) comment The sincos() family of functions calculates sin and cos simultaneously. comment At the specified point the inaccuracy of the result of sincos() function is more then comment 20 bits from the end of the floating point number. quell end test /olver/math/trig/tests/tan_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(tan) comment At the specified point the inaccuracy of the result of tan() family of functions is more then comment 20 bits from the end of the floating point number. quell end test /olver/math/bessel/tests/y0_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(y0) comment The y0() function is Bessel function of the second kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/bessel/tests/y1_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(y1) comment The y1() function is Bessel function of the second kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/bessel/tests/yn_spec 513 expected_severity failed resolution Known problem marker Registered bug: bug513(yn) comment The yn() function is Bessel function of the second kind. comment At the specified point the inaccuracy of the result is more then 20 bits from the comment end of the floating point number. quell end test /olver/math/chyper/tests/cacosh_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(cacosh) comment The cacosh() family of functions shall compute the complex arc hyperbolic cosine of comment their argument. comment According to LSB, the functions shall return result in the range of a half-strip of non-negative comment values along the real axis and in the interval [-i, +i] along the imaginary axis. comment But at the specified point the result doesn't lay in appropriate area of the complex comment plane. quell end test /olver/math/chyper/tests/catanh_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(catanh) comment The catanh() family of functions shall compute the complex arc hyperbolic tangent of their comment argument. comment But at the specified point the result is very imprecise (inaccuracy is more then 20 bits from the end of the comment floating point number). quell end test /olver/math/cexp/tests/cpow_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(cpow) comment The cpow(x, y) family of functions shall compute the complex power function x^y, comment with a branch cut for the first parameter along the negative real axis. comment If the argument is x = -Inf+i*1 and y = -2+i*0 then the functions return 0-i*0 comment instead of 0+i*0. This result is logical from definition of mathematical complex comment power function. quell end test /olver/math/ctrig/tests/ctan_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(ctan) comment The ctan() family of functions shall compute the complex tangent of their comment argument. comment At the specified point the functions don't satisfy to the property comment ctan(z) == -i * ctanh(iz). quell end test /olver/math/chyper/tests/ctanh_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(ctanh) comment The ctanh() family of functions shall compute the complex hyperbolic tangent of their comment argument. comment But at the specified point the result is very imprecise (inaccuracy is more then 20 bits from the end of the comment floating point number). quell end test /olver/math/gamma/tests/gamma_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(gamma) comment According to LSB, gamma(x) family of functions shall return either HUGE_VAL or NaN if comment x is a non-positive integer. comment But on the target machine the functions don't return HUGE_VAL or NaN if the argument comment is not positive. quell end test /olver/math/gamma/tests/lgamma_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(lgamma) comment According to LSB, lgamma(x) family of functions shall return +HUGE_VAL if comment x is a non-positive integer. comment But on the target machine the functions don't return +HUGE_VAL if the argument comment is not positive. quell end test /olver/math/gamma/tests/lgamma_r_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(lgamma_r) comment According to LSB, lgamma_r(x) family of functions shall return +HUGE_VAL if comment x is a non-positive integer. comment But on the target machine the functions don't return +HUGE_VAL if the argument comment is not positive. quell end test /olver/math/gamma/tests/tgamma_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(tgamma) comment The tgamma(x) family of functions shall compute the mathematical gamma() function of x. comment According to LSB, if x is a negative integer NaN shall be returned. comment But on the target machine, the functions don't return NaN if the argument is negative. quell end test /olver/math/bessel/tests/yn_spec 516 expected_severity failed resolution Known problem marker Registered bug: bug516(yn) comment The yn() function is Bessel function of the second kind. comment At the specified point, when overflow occured, function return NaN instead of 0 or -Infinity comment according to LSB. quell end test /olver/math/cexp/tests/cexp_spec 5161 expected_severity failed resolution Known problem marker Registered bug: bug516_1(cexp) comment The cexp() family of functions shall compute the complex exponent of z. comment But on the target machine the functions don't return NaN+i*Inf if the argument comment is NaN+i*Inf. This result is logical from definition of mathematical exponent comment function. quell end test /olver/math/bessel/tests/jn_spec 5161 expected_severity failed resolution Known problem marker Registered bug: bug516_1(jn) comment The jn() function is Bessel function of the first kind. comment At the specified point function return -0 instead of 0 comment according to LSB. quell end test /olver/math/cexp/tests/cexp_spec 5162 expected_severity failed resolution Known problem marker Registered bug: bug516_2(cexp) comment The cexp() family of functions function shall compute the complex exponent of their comment argument. comment At the specified point the result of computing the exponent is very imprecise comment (inaccuracy is more then 20 bits from the end of the floating point number). quell end test /olver/math/bessel/tests/jn_spec 5162 expected_severity failed resolution Known problem marker Registered bug: bug516_2(jn) comment The jn() function is Bessel function of the first kind. comment At the specified point function return value with the wrong sign. quell end test /olver/util/float/tests/ilogb_spec 5181 expected_severity failed resolution Known problem marker Registered bug: bug518_1(ilogb) comment The ilogb() function shall return the exponent part of its argument. comment According to LSB, if this argument is infinity, EDOM error shall be set in errno. comment But on the target machine this function sets error code EOK instead of EDOM. end test /olver/util/float/tests/logb_spec 5182 expected_severity failed resolution Known problem marker Registered bug: bug518_2(logb) comment The logb() function shall compute the exponent of the integral part of logarithm comment of its argument as a signed floating-point value. comment According to LSB, if this argument is 0, ERANGE error shall be set in errno. comment But on the target machine this function sets error code EOK instead of ERANGE. end test /olver/util/float/tests/nextafter_spec 5183 expected_severity failed resolution Known problem marker Registered bug: bug518_3(nextafter) comment The nextafter(x, y) family of functions functions shall compute the next representable comment floating-point value following x in the direction of y. comment According to LSB, if the correct value is subnormal or underflows then ERANGE error code comment shall be set. comment But on the target machine the function sets error code EOK instead of ERANGE. end test /olver/util/float/tests/nexttoward_spec 5184 expected_severity failed resolution Known problem marker Registered bug: bug518_4(nexttoward) comment The nexttoward(x, y) family of functions functions shall compute the next representable comment floating-point value following x in the direction of y. comment According to LSB, if the correct value is subnormal or underflows then ERANGE error code comment shall be set. comment But on the target machine the function sets error code EOK instead of ERANGE. end test /olver/util/float/tests/scalb_spec 5185 expected_severity failed resolution Known problem marker Registered bug: bug518_5(scalb) comment The scalb() family of functions shall compute x*r^n, where r is the radix of the machine's comment floating-point arithmetic. comment According to LSB, the functions shall set EDOM error code when x is zero and n is +Inf, or x is Inf and n comment is -Inf and ERANGE when overflow occurs. comment But the functions sets error code EOK in these cases. end test /olver/util/float/tests/scalbln_spec 5186 expected_severity failed resolution Known problem marker Registered bug: bug518_6(scalbln) comment The scalbln() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing comment FLT_RADIX^n explicitly. comment According to LSB, the functions shall set ERANGE error code when overflow occurs. comment But on the target machine the function sets error code EOK instead of ERANGE in comment this case. end test /olver/util/float/tests/scalbn_spec 5187 expected_severity failed resolution Known problem marker Registered bug: bug518_7(scalbn) comment The scalbn() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing comment FLT_RADIX^n explicitly. comment According to LSB, the functions shall set ERANGE error code when overflow occurs. comment But on the target machine the function sets error code EOK instead of ERANGE in comment this case. end test /olver/util/format/tests/getdate_spec 5201 expected_severity failed resolution Known problem marker Registered bug: bug520_1(getdate) comment The getdate() function shall convert a string representation of a date or time into a broken-down time comment according to conversion specification. comment But on the target machine it is detected incorrect processing of conversion patterns comment %S, %M, %p, %y, %Y, %d, %C. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0520_1. end test /olver/memory/mman/tests/mmap_spec 522 expected_severity failed resolution Known problem marker Registered bug: bug522(mmap) comment The mmap() function shall establish a mapping between a process' address space and a file, comment shared memory object, or typed memory object. The length of the mapping is set up by comment function parameter. comment According to LSB, if this parameter equals to zero then function shall cause EINVAL error. comment But it returns success on the target machine. comment The bug was fixed in libc 2.4. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0522. end test /olver/time/clock/tests/clock_getres_spec 523 expected_severity failed resolution Known problem marker Registered bug: bug523(clock_getres) comment The clock_getres() function shall return the resolution of any clock and write this comment value to the second parameter. comment According to LSB, if this parameter is NULL then the clock resolution is not returned. comment But on the target machine clock_getres() crashes if second parameter is NULL. comment The bug was fixed in libc 2.4. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0523. end test /olver/ncurses/string/tests/scanw_spec 5241 expected_severity failed resolution Known problem marker Registered bug: bug524_1(scanw) comment According to the standard, upon successful completion, scanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function scanw() returned 1 when it is called with first argument " %i". comment Bug was added to linuxtesting.ru as bug number S0524. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/ncurses/string/tests/vw_scanw_spec 5242 expected_severity failed resolution Known problem marker Registered bug: bug524_2(vw_scanw) comment According to the standard, upon successful completion, vw_scanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function vw_scanw() returned 1 when it is called with first argument " %i". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/ncurses/string/tests/vwscanw_spec 5243 expected_severity failed resolution Known problem marker Registered bug: bug524_3(vwscanw) comment According to the standard, upon successful completion, vwscanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function vwscanw() returned 1 when it is called with first argument " %i". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/ncurses/string/tests/scanw_spec 5244 expected_severity failed resolution Known problem marker Registered bug: bug524_4(mvwscanw) comment According to the standard, upon successful completion, mvwscanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function mvwscanw() returned 1 when it is called with fmt argument " %i". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/ncurses/string/tests/scanw_spec 5245 expected_severity failed resolution Known problem marker Registered bug: bug524_5(mvscanw) comment According to the standard, upon successful completion, mvscanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function mvscanw() returned 1 when it is called with fmt argument " %i". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/ncurses/string/tests/scanw_spec 5246 expected_severity failed resolution Known problem marker Registered bug: bug524_6(wscanw) comment According to the standard, upon successful completion, wscanw() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment But on the target machine, the function wscanw() returned 1 when it is called with fmt argument " %i". comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. quell end test /olver/system/user/tests/getgrouplist_spec 525 expected_severity failed resolution Known problem marker Registered bug: bug525(getgrouplist) comment The getgrouplist() function shall fill in the supplied array with the supplementary groups comment for the specified user and update its parameter to contain the number of groups copied. comment According to LSB, if there was not sufficient room to copy all the supplementary group comment identifiers, getgrouplist() shall return -1, and update the value referenced by this parameter comment to the number actually copied. comment But on the target machine this parameter was set to the value, greater then array size. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0525. quell end test /olver/pthread/attr/tests/pthread_attr_setstack_spec 5261 expected_severity failed resolution Known problem marker Registered bug: bug526_1(pthread_attr_setstack) comment The function pthread_attr_setstack() is not implemented in libraries on the system comment of the target machine. end test /olver/pthread/pthread/tests/pthread_create_spec 5262 expected_severity failed resolution Known problem marker Registered bug: bug526_2(pthread_attr_setstack) comment The function pthread_attr_setstack() is not implemented in libraries on the system comment of the target machine, thus pthread_create() was not successful. end test /olver/util/format/tests/getdate_spec 527 expected_severity failed resolution Known problem marker Registered bug: bug527(getdate) comment The getdate() function shall convert a string representation of a date or time into a broken-down time comment structure using template. comment On the target machine if this template is '%C' then getdate() crashes. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0520_1. end test /olver/math/exp/tests/log1p_spec 530 expected_severity failed resolution Known problem marker Registered bug: bug530(log1pl) comment The log1pl(x) function shall compute log(1.0 + x). comment According to LSB, for finite values of x that are less than -1, or if x is -Inf, comment a domain error shall occur, and NaN shall be returned. comment But on the target machine the function returns -Inf instead of NaN on -Inf. comment The bug was fixed in libc 2.6. quell end test /olver/math/chyper/tests/cacosh_spec 532 expected_severity failed resolution Known problem marker Registered bug: bug532(cacosh) comment The cacosh() family of functions shall compute the complex arc hyperbolic cosine of comment their argument. comment The cacosh(-1) function shall return Pi * I according to definition of arc hyperbolic cosine. comment But on the target machine it returns Pi/2 * I. quell end test /olver/math/exp/tests/pow_spec 533 expected_severity failed resolution Known problem marker Registered bug: bug533(pow) comment The pow(x, y) family of functions shall compute the value of x raised to the power y. comment According to LSB, if x is -Inf and y is Nan then the functions shall return NaN. comment But on the target machine it returns Inf instead of NaN on (-Inf, NaN). comment The bug was fixed in libc 2.6. quell end test /olver/util/float/tests/logb_spec 535 expected_severity failed resolution Known problem marker Registered bug: bug535(logb) comment The logb() family of functions shall compute the exponent of x, which is the integral part comment of log |x|, as a signed floating-point value. comment If the number is denormalized then its part that is stored in exponential part is comment different from log(2)(x). Function logb(x) shall return log(2)(x). comment But on the target machine, the family of functions does not produce correct results comment on denormalized arguments, because it simply returns exponential part of the number comment which is not correct for this type of arguments. comment The bug was fixed in libc 2.6. end test /olver/util/float/tests/scalbln_spec 536 expected_severity failed resolution Known problem marker Registered bug: bug536(scalbln) comment The scalbln() family of functions shall compute x * FLT_RADIX at the power of n efficiently, not comment normally by computing FLT_RADIX at the power of n explicitly. comment On the target machine the functions return incorrect result on denormalized arguments - NaN or comment very big number. comment Bug was added to linuxtesting.ru as bug number S0536. end test /olver/math/exp/tests/pow_spec 537 expected_severity failed resolution Known problem marker Registered bug: bug537(powl) comment The powl(x, y) function shall compute the value of x raised to the power y. comment According to LSB, it shall return NaN on x less than 0 and finite non integer y. comment But it doesn't return NaN on such arguments on the target machine. comment Bug was added to linuxtesting.ru as bug number S0537. quell end test /olver/math/exp/tests/pow_spec 538 expected_severity failed resolution Known problem marker Registered bug: bug538(powl) comment The powl(x, y) function shall compute the value of x raised to the power y. comment But at the given point on the target machine it produces incorrect result after chain of comment calls of powl() on positive x and negative y. quell end test /olver/math/exp/tests/hypot_spec 543 expected_severity failed resolution Known problem marker Registered bug: bug543(hypotl) comment The hypotl() function shall compute the value of the square root of x^2+ y^2 without comment undue overflow or underflow. comment According to LSB, if both arguments are subnormal and the correct result is subnormal, comment a range error may occur and the correct result is returned. comment But on the target machine the function returns Inf instead of correct subnormal result on comment both subnormal arguments. quell end test /olver/time/timer/tests/timer_getoverrun_spec 5441 expected_severity failed resolution Known problem marker Registered bug: bug544_1(timer_getoverrun) comment When a timer expiration signal is delivered to or accepted by a process, if the implementation comment supports the Realtime Signals Extension, the timer_getoverrun() function shall return the timer comment expiration overrun count for the specified timer. comment But on the target machine simple call to timer_getoverrun() crashes. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0544. quell end test /olver/time/timer/tests/timer_delete_spec 5442 expected_severity failed resolution Known problem marker Registered bug: bug544_2(timer_delete) comment The timer_delete() function deletes the specified timer. comment But on the target machine simple call to timer_delete() function crashes. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0544. quell end test /olver/time/timer/tests/timer_gettime_spec 5443 expected_severity failed resolution Known problem marker Registered bug: bug544_3(timer_gettime) comment The timer_gettime() function shall store the amount of time until the specified timer, comment expires and the reload value of the timer into the space pointed to by the value argument. comment But on the target machine simple call to timer_gettime() crashes. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0544. quell end test /olver/process/fenv/tests/fesetround_spec 545 expected_severity failed resolution Known problem marker Registered bug: bug545(fesetround_spec) comment The fesetround() function shall establish the rounding direction represented by its argument. comment According to LSB, the fesetround() function shall return a zero value if and only if the comment requested rounding direction was established. If the argument is not equal to the value of a comment rounding direction macro, the rounding direction is not changed. comment But on the target machine fesetround() function returns 0 on any invalid negative value. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0545. end test /olver/math/exp/tests/pow_spec 548 expected_severity failed resolution Known problem marker Registered bug: bug548(pow) comment The pow(x, y) family of functions shall compute the value of x raised to the power y. comment According to LSB, if x is +-0 and y is negative infinity +Inf shall be retuned comment an no error shall occur. comment But on the target machine pow() returns EDOM error in this case. quell end test /olver/math/exp/tests/pow_spec 549 expected_severity failed resolution Known problem marker Registered bug: bug549(pow) comment The pow(x, y) family of functions shall compute the value of x raised to the power y. comment According to LSB, if the correct value would cause underflow, and is representable, comment a range error may occur and the correct value shall be returned. comment But on the target machine this function returns 0 when the correct result underflows but comment is still representable. comment Bug was added to linuxtesting.ru as bug number S0549. quell end test /olver/util/float/tests/ilogb_spec 550 expected_severity failed resolution Known problem marker Registered bug: bug550(ilogb) comment The ilogb() family of functions shall return the exponent part of its argument. comment According to LSB, it shall set error code to EDOM when computing radix-independent comment exponent of +0 or -0. comment But on the target machine ilogb() sets error code ERANGE in this case. end test /olver/util/float/tests/logb_spec 551 expected_severity failed resolution Known problem marker Registered bug: bug551(logb) comment The logb() family of functions shall compute the exponent of x, which is the integral part of log |x|, as a comment signed floating-point value. comment According to LSB, it shall set error code to ERANGE when computing exponent of +0 or -0. comment But on the target machine logb() sets error code EDOM in this case. end test /olver/util/float/tests/__signbit_spec 552 expected_severity failed resolution Known problem marker Registered bug: bug552(__signbit) comment The function __signbit() shall determine whether the sign of its argument value is negative. comment NaNs, zeros, and infinities have a sign bit. It returns a non-zero value if and only if the comment sign of its argument value is negative. comment But on the target machine, the function __signbit() returns 0 on -NaN while the correct comment result shall be non-zero. end test /olver/util/float/tests/__signbit_spec 552 expected_severity failed resolution Known problem marker Registered bug: bug552(__signbitf) comment The __signbit() function shall determine whether the sign of its argument value is negative. NaNs, zeros, comment and infinities have a sign bit. comment According to LSB, the __signbit() shall return a non-zero value if and only if the sign of its comment argument value is negative. comment But on the target machine it returns 0 on -NaN while the correct result shall be non-zero. end test /olver/math/gamma/tests/tgamma_spec 553 expected_severity failed resolution Known problem marker Registered bug: bug553(tgamma) comment The tgamma(x) family of functions shall compute the mathematical gamma() function of x. comment According to LSB, if x is zero then pole error shall occur and error code shall comment be set to ERANGE. comment But on the target machine, the functions set error code EDOM instead of ERANGE. quell end test /olver/time/timer/tests/timer_create_spec 558 expected_severity failed resolution Known problem marker Registered bug: bug558(timer_create) comment The timer_create() function shall create a per-process timer using the specified comment clock, clock_id, as the timing base. comment But call to timer_create with clock_id received from clock_getcpuclockid() cause comment an error EINVAL on the target machine. comment The bug was fixed in libc 2.4. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0558. end test /olver/util/format/tests/wcsftime_spec 561 expected_severity failed resolution Known problem marker Registered bug: bug561(wcsftime) comment %z Replaced by the offset from UTC in the ISO 8601:2000 standard format, comment or by no characters if no timezone is determinable; depending on the field tm_isdst in tm structure. comment But on the target machine it is detected incorrect processing of this conversion pattern comment when tm_isdst is set to a positive number - no daylight savings time offset is used. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0561. end test /olver/time/clock/tests/clock_getres_spec 6021 expected_severity failed resolution Known problem marker Registered bug: bug602_1(clock_getres) comment The clock_getres() function shall return the resolution of any clock. comment But on the target machine this function returns error when it is comment executed with correct clock (recieved as the result of clock_getcpuclockid() comment function) as the argument. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0601. end test /olver/time/clock/tests/clock_gettime_spec 6022 expected_severity failed resolution Known problem marker Registered bug: bug602_2(clock_gettime) comment The clock_gettime() function shall return the current value for the specified clock. comment But on the target machine this function returns error when it is comment executed with correct clock (recieved as the result of clock_getcpuclockid() comment function) as the argument. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0601. end test /olver/socket/socket/tests/sockatmark_spec 610 expected_severity failed resolution Known problem marker Registered bug: bug610(sockatmark) comment The sockatmark() function shall determine whether the socket specified by the descriptor comment is at the out-of-band data mark. comment But on the target machine this function returns error EFAULT when it is comment executed with correct socket as the argument. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0610. end test /olver/process/meta/tests/setgid_spec 6111 expected_severity failed resolution Known problem marker Registered bug: bug611_1(setgid) comment If the process has appropriate privileges, setgid() shall set the real group ID, effective group ID, and comment the saved set-group-ID of the calling process to gid. comment But on the target machine this function sets the real group ID to invalid value if it is comment executed with parameter less than zero. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0611. end test /olver/process/meta/tests/setuid_spec 6112 expected_severity failed resolution Known problem marker Registered bug: bug611_2(setuid) comment If the process has appropriate privileges, setuid() shall set the real user ID, effective user ID, and comment the saved set-user-ID of the calling process to uid. comment But on the target machine this function sets the real user ID to invalid value if it is comment executed with parameter less than zero. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0611. end test /olver/math/exp/tests/exp2_spec 616 expected_severity failed resolution Known problem marker Registered bug: bug616(exp2l) comment The function exp2l() is not implemented in libraries on the system comment of the target machine. quell end test /olver/fs/dir/tests/readdir_spec 617 expected_severity failed resolution Known problem marker Registered bug: bug617(readdir_spec) comment The readdir() function shall return a pointer to a structure representing comment the directory entry at the current position in the directory. comment Each file in the filesystem should have unique file serial number. But on comment the target machine readdir() returns the same serial number for different comment file. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0617. end test /olver/math/exp/tests/hypot_spec 618 expected_severity failed resolution Known problem marker Registered bug: bug618(hypotf) comment The hypotf() function shall compute the value of the square root of x^2+ y^2 without comment undue overflow or underflow. comment According to LSB, if both arguments are subnormal and the correct result is subnormal, comment a range error may occur and the correct result is returned. comment But on the target machine the function returns 0 instead of correct subnormal result on comment both subnormal arguments. quell end test /olver/math/real/tests/llround_spec 619 expected_severity failed resolution Known problem marker Registered bug: bug619(llroundf) comment The llroundf() function shall round their argument to the nearest integer value, comment rounding halfway cases away from zero, regardless of the current rounding direction. comment But on the target machine, the function gives incorrect result on the inputs comment +-1.9999998807907104e+00 (i.e. nearest to +-2 float numbers). quell end test /olver/io/multiplex/tests/poll_spec 649 expected_severity failed resolution Known problem marker Registered bug: bug649 comment Write bit (file desc or POLLOUT | POLLWRBAND) was set to 1, but write() function returns -1. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0649. end test /olver/io/multiplex/tests/select_spec 649 expected_severity failed resolution Known problem marker Registered bug: bug649 comment Write bit (file desc or POLLOUT | POLLWRBAND) was set to 1, but write() function returns -1. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0649. end test /olver/math/real/tests/fdim_spec 664 expected_severity failed resolution Known problem marker Registered bug: bug664(fdim) comment The fdim(x, y) family of functions shall determine the positive difference between their arguments. comment According to LSB, if the result overflows then fdim() shall fail and shall set ERANGE error code. comment But on the target machine, the functions crash when overflow occurs. quell end test /olver/signal/sigstr/tests/psignal_spec 684 expected_severity failed resolution Known problem marker Registered bug: bug684(psignal) comment If string s is empty, psignal shall display only a message describing the signal number sig. comment SYNOPSIS comment ... comment void psignal(int sig, const char * s); comment ... comment DESCRIPTION comment ... comment If s is not the null pointer, and does not point to an empty string (e.g. "\0"), comment the message shall consist of the string s, a colon, a space, and a string comment describing the signal number sig; otherwise psignal() shall display only a message comment describing the signal number sig. comment ... comment But in real, psignal output a colon, a space, and a string describing the signal number sig. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0684. quell end test /olver/signal/sigstr/tests/strsignal_spec 685 expected_severity failed resolution Known problem marker Registered bug: bug685(strsignal) comment If sig is not a valid signal number, strsignal shall return either a pointer comment either a pointer to the string "unknown signal", or a null pointer. comment SYNOPSIS comment ... comment char * strsignal(int sig); comment ... comment RETURN VALUE comment If sig is a valid signal number, strsignal() shall return a pointer comment to the appropriate description string. Otherwise, strsignal() shall return comment either a pointer to the string "unknown signal", or a null pointer. comment ... comment But in real, strsignal return "Unknown signal", a space, and a number sig. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0685. quell end test /olver/ncurses/terminal/tests/tgetnum_spec 686 expected_severity failed resolution Known problem marker Registered bug: bug686(tgetnum) comment According to the standard, upon successful completion, tgetnum() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment RETURN VALUE comment ... comment Upon successful completion, functions that return an integer return OK. comment Otherwise, they return ERR. comment But the real implementation does not match LSB standard. comment Manual pages for GNU extension, that is used in real Linux systems, say: comment The tgetnum routine gets the numeric entry for id, or -1 if it is not available. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0686. quell end test /olver/ncurses/terminal/tests/tgetflag_spec 687 expected_severity failed resolution Known problem marker Registered bug: bug687(tgetflag) comment According to the standard, upon successful completion, tgetflag() function from Ncurses comment library shall return OK(0), otherwise, it shall return ERR(-1). comment RETURN VALUE comment ... comment Upon successful completion, functions that return an integer return OK. comment Otherwise, they return ERR. comment But the real implementation does not match LSB standard. comment Manual pages for GNU extension, that is used in real Linux systems, say: comment The tgetflag routine gets the boolean entry for id, or zero if it is not available. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0687. quell end test /olver/util/conversion/tests/__strtod_internal_spec 7091 expected_severity failed resolution Known problem marker Registered bug: bug709_1(__strtod_internal) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/__wcstod_internal_spec 7091 expected_severity failed resolution Known problem marker Registered bug: bug709_1(__wcstod_internal) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/conversion/tests/__strtod_internal_spec 7092 expected_severity failed resolution Known problem marker Registered bug: bug709_2(__strtof_internal) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/__wcstod_internal_spec 7092 expected_severity failed resolution Known problem marker Registered bug: bug709_2(__wcstof_internal) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/conversion/tests/__strtod_internal_spec 7093 expected_severity failed resolution Known problem marker Registered bug: bug709_3(__strtold_internal) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/__wcstod_internal_spec 7093 expected_severity failed resolution Known problem marker Registered bug: bug709_3(__wcstold_internal) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/conversion/tests/strtod_spec 7094 expected_severity failed resolution Known problem marker Registered bug: bug709_4(strtod) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/wcstod_spec 7094 expected_severity failed resolution Known problem marker Registered bug: bug709_4(wcstod) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/conversion/tests/strtod_spec 7095 expected_severity failed resolution Known problem marker Registered bug: bug709_5(strtof) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/wcstod_spec 7095 expected_severity failed resolution Known problem marker Registered bug: bug709_5(wcstof) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/conversion/tests/strtod_spec 7096 expected_severity failed resolution Known problem marker Registered bug: bug709_6(strtold) comment Functions for convert a string to a double-precision number make shift in a string with error. comment Functions __strtof_internal, __strtod_internal, __strtold_internal, strtof, strtod, strtold. comment All thise functions have signature like comment (const char *restrict nptr, char **restrict endptr); comment After return * endptr must point to final string of one or more unrecognized characters, comment including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0709. end test /olver/util/conversion/tests/wcstod_spec 7096 expected_severity failed resolution Known problem marker Registered bug: bug709_6(wcstold) comment Functions for convert a wide string to a double-precision number make shift in a string with error. comment Functions __wcstof_internal, __wcstod_internal, __wcstold_internal, wcstof, wcstod, wcstold. comment All thise functions have signature like comment (const wchar_t *restrict nptr, wchar_t **restrict endptr); comment After return * endptr must point to final wide string of one or more unrecognized wide characters, including comment the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) comment * endptr must point to symbol after closing bracket. But * endptr point to closing bracket. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0710. end test /olver/util/search/tests/hsearch_spec 790 expected_severity failed resolution Upstream bug marker Registered bug: bug790(hsearch) comment The hsearch(item, action) function shall return a pointer into a hash table created by hcreate(nel) function comment indicating the location at which an item can be found. comment The modifications of hsearch in glibc-2.9 leads to segmentation fault in some circumstances as a consequence comment of internal invariant violation or in the case size of the table created is less than 3. comment Additional information about these bugs may be found at http://linuxtesting.org/results/report?num=S0791 and comment http://linuxtesting.org/results/report?num=S0790. end test /olver/util/search/tests/hsearch_spec 792 expected_severity failed resolution Upstream bug marker Registered bug: bug792(hsearch) comment The hsearch(item, action) function shall return a pointer into a hash table indicating the location at which an item can be found. comment According to LSB, the ENTER value of the action argument indicates that the item should be inserted in the table at an appropriate point. comment But the implementation of hsearch in glibc-2.9 doesn't insert item in the case it's key value is zero comment and hence returns NULL pointer while trying to obtain the value desired. comment Additional information about these bugs may be found at http://linuxtesting.org/results/report?num=S0791 and comment http://linuxtesting.org/results/report?num=S0790. end test /olver/util/search/tests/hsearch_spec 793 expected_severity failed resolution Upstream bug marker Registered bug: bug793(hsearch) comment The hsearch(item, action) function shall return a pointer into a hash table created by hcreate(nel) function comment indicating the location at which an item can be found. comment The ENTER value of action parameter indicates that the item should be inserted in the table at an appropriate point. comment The function may fail with ENOMEM error code if insufficient storage space is available. comment But the implementation of hsearch in glibc-2.9 sets error code ENOMEM in some circumstances due to internal invariant violation. comment Additional information about these bugs may be found at http://linuxtesting.org/results/report?num=S0791 and comment http://linuxtesting.org/results/report?num=S0790. end test /olver/process/resources/tests/ulimit_spec 794 expected_severity failed resolution Test suite deficiency marker Registered bug: bug794(ulimit) comment It is a test suite deficiency that will be fixed soon. quell end test /olver/system/sysconf/tests/sysconf_spec 807 expected_severity failed resolution Specification deficiency marker Registered bug: bug807(sysconf) comment According to LSB if any of symbols _POSIX2_C_BIND, _POSIX2_C_DEV, _POSIX2_CHAR_TERM, _POSIX2_LOCALEDEF, _POSIX2_SW_DEV, comment _POSIX2_VERSION, _POSIX_ADVISORY_INFO, _POSIX_ASYNCHRONOUS_IO, _POSIX_BARRIERS, _POSIX_CLOCK_SELECTION, _POSIX_FSYNC, comment _POSIX_IPV6, _POSIX_MAPPED_FILES, _POSIX_MEMLOCK, _POSIX_MEMLOCK_RANGE, _POSIX_MEMORY_PROTECTION, _POSIX_MESSAGE_PASSING, comment _POSIX_PRIORITIZED_IO, _POSIX_PRIORITY_SCHEDULING, _POSIX_RAW_SOCKETS, _POSIX_READER_WRITER_LOCKS, _POSIX_REALTIME_SIGNALS, comment _POSIX_SEMAPHORES, _POSIX_SHARED_MEMORY_OBJECTS, _POSIX_SPAWN, _POSIX_SPIN_LOCKS, _POSIX_SYNCHRONIZED_IO, comment _POSIX_THREAD_ATTR_STACKADDR, _POSIX_THREAD_ATTR_STACKSIZE, _POSIX_THREAD_PRIO_INHERIT, _POSIX_THREAD_PRIO_PROTECT, comment _POSIX_THREAD_PRIORITY_SCHEDULING, _POSIX_THREAD_PROCESS_SHARED, _POSIX_THREADS, _POSIX_THREAD_SAFE_FUNCTIONS, comment _POSIX_TIMEOUTS, _POSIX_TIMERS, _POSIX_VERSION is defined in <unistd.h>, it shall be defined to be -1, comment 0, or 200112L. The value of this symbol reported by sysconf() shall either be -1 or 200112L. But glibc since comment version 2.10 corresponds to POSIX-2008 claiming that the value returned by sysconf() shall either be -1 or 200809L. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0807. dup /olver/other/other/tests/others 807 quell end test /olver/process/meta/tests/seteuid_spec 82 expected_severity failed resolution Known problem marker Registered bug: bug82(seteuid) comment The LSB specification says nothing that setreuid() function may comment change the saved set-user-ID value. comment But actually, if the real user ID is set to or comment the effective user ID is set to a value not equal to comment the previous real user ID, the saved set-user-ID will be set to the new effective user ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/process/meta/tests/setegid_spec 83 expected_severity failed resolution Known problem marker Registered bug: bug83(setegid) comment The LSB specification says nothing that setregid() function may comment change the saved set-group-ID value. comment But actually, if the real group ID is set to or comment the effective group ID is set to a value not equal to comment the previous real group ID, the saved set-group-ID will be set to the new effective group ID. comment This feature is described in the Linux man pages. So it should be specified in the LSB as well. comment Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. quell end test /olver/util/format/tests/getdate_spec 812 expected_severity failed marker Registered bug: bug812(getdate) comment If given format consists of conversion specifications "%C" and "%D", the function return wrong result (tm_year always equals to 100). comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0812 resolution Known problem end test /olver/util/format/tests/strptime_spec 808 expected_severity failed marker Registered bug: bug808(strptime) comment Values of all fields of struct tm shall be positive or 0. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0808 resolution Known problem end test /olver/util/format/tests/strptime_spec 816 expected_severity failed marker Registered bug: bug816(strptime) comment If given format consists of conversion specifications "%C" and "%D", the function return wrong result (tm_year always equals to 100). comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0816 resolution Known problem end test /olver/util/format/tests/getdate_spec 818 expected_severity failed marker Registered bug: bug818(getdate) comment On 64-bits architectures call of getdate() leds to segmentation fault if template = "%d". comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0818 resolution Known problem end test /olver/math/exp/tests/exp2_spec 821 expected_severity failed marker Registered bug: bug821(exp2l) comment The exp2l(x) function shall compute the base-2 exponential of x. comment According to LSB, if the correct value would cause underflow and is representable the correct value shall be returned. comment But it returns 0 on denormal arguments on the target machine. resolution Known problem end test /olver/math/exp/tests/expm1_spec 822 expected_severity failed marker Registered bug: bug822(expm1) comment The expm1l(x) function shall compute the base-e exponential of x - 1.0. comment According to LSB, if the correct value would cause overflow Inf shall be returned. comment But on the target machine the function returns NaN instead of Inf. resolution Known problem end test /olver/math/exp/tests/exp_spec 823 expected_severity failed marker Registered bug: bug823(expl) comment The expl(x) function shall compute the base-e exponential of x. comment According to LSB, if the result overflows then errno shall be set to ERANGE. comment But on the target machine error code remains to be EOK. resolution Known problem end test /olver/math/error/tests/erfc_spec 824 expected_severity failed marker Registered bug: bug824(erfc) comment Call to erfc, erfcf, erfcl make crash. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0824 resolution Known problem end test /olver/memory/mman/tests/shm_open_spec 825 expected_severity failed marker Registered bug: bug825(shm_open) comment shm_open() function set errno to unexpected error code ENOSYS comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0825 resolution Known problem end test /olver/pthread/sem/tests/sem_open_spec 826 expected_severity failed marker Registered bug: bug826(sem_open) comment sem_open() function set errno to unexpected error code ENOSYS comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0826 resolution Known problem end test /olver/process/meta/tests/nice_spec 827 expected_severity failed marker Registered bug: bug827(nice) comment The nice() function shall fail if the incr argument is negative and the calling process does not have appropriate privileges. comment But nice did not return EPERM if incr argument is negative and the calling process does not have appropriate privileges. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0827 resolution Known problem end test /olver/process/meta/tests/getpriority_spec 828 expected_severity failed marker Registered bug: bug828(getpriority) comment The getpriority() and setpriority() functions shall fail if: comment comment [ESRCH] comment No process could be located using the which and who argument values specified. comment [EINVAL] comment The value of the which argument was not recognized, or the value of the who argument comment is not a valid process ID, process group ID, or user ID. comment comment But getpriority() and setpriority() returns EOK if no process could be located using the which and who argument values specified or if the value of the which argument was not recognized, or the value of the who argument is not a valid process ID, process group ID, or user ID. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0828 resolution Known problem end test /olver/process/meta/tests/setpriority_spec 829 expected_severity failed marker Registered bug: bug829(setpriority) comment The getpriority() and setpriority() functions shall fail if: comment comment [ESRCH] comment No process could be located using the which and who argument values specified. comment [EINVAL] comment The value of the which argument was not recognized, or the value of the who argument comment is not a valid process ID, process group ID, or user ID. comment comment But getpriority() and setpriority() returns EOK if no process could be located using the which and who argument values specified or if the value of the which argument was not recognized, or the value of the who argument is not a valid process ID, process group ID, or user ID. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0829 resolution Known problem end test /olver/math/real/tests/fdim_spec 830 expected_severity failed marker Registered bug: bug830(fdimf) comment fdimf( -Infinity, -Infinity ) return NaN instead of 0 comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0830 resolution Known problem end test /olver/math/real/tests/fdim_spec 831 expected_severity failed marker Registered bug: bug831(fdim) comment fdim( -Infinity, -Infinity ) return NaN instead of 0 comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0831 resolution Known problem end test /olver/math/real/tests/drem_spec 832 expected_severity failed marker Registered bug: bug832(drem) comment dremf, dreml not set errno to EDOM if x == Infinity and y != NaN comment dremf not set errno to EDOM if x != NaN and y == 0 comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0832 resolution Known problem end test /olver/util/search/tests/hsearch_spec 833 expected_severity failed marker Registered bug: bug833(hsearch) comment hsearch() function set errno to unexpected error code ESRCH comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0833 resolution Known problem end test /olver/math/real/tests/fdim_spec 834 expected_severity failed marker Registered bug: bug834(fdiml) comment fdiml( -Infinity, -Infinity ) return NaN instead of 0 comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0834 resolution Known problem end test /olver/math/real/tests/lrint_spec 835 expected_severity failed marker Registered bug: bug835(lrint) comment These functions shall round their argument to the nearest integer value, comment rounding according to the current rounding direction. comment comment But lrintl( 1.9999999999999999999999999999999998e+00 ) return 1 instead of 2 , comment lrintl( -1.9999999999999999999999999999999998e+00 ) return -1 instead of -2 , comment lrintl( 1.2345001000000000000000000000000000e+03 ) return 1234 instead of 1235, comment lrintl( -1.2345001000000000000000000000000000e+03 ) return -1234 instead of -1235 comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0835 resolution Known problem end test /olver/ncurses/window/tests/refresh_spec 836 expected_severity failed marker Registered bug: bug836(refresh) comment Errors in ncurses on OS "Moblin release 2.1 (Moblin)". comment Become apparent under call to refresh or wrefresh. comment Additional information about this bug may be found at comment http://linuxtesting.org/results/report?num=S0836 resolution Known problem end test /tset/LSB.fhs/var/lib-hwclock/lib-hwclock-tc 1 expected_severity failed resolution Still in transition marker Found /etc/adjtime, should be in /var/lib/hwclock comment The FHS mandated that this file move out of /etc, but comment not everyone has caught up to this requirement, so comment it is temporary waived for now. quell end test /fhs/share-ppd/share-ppd 1 expected_severity failed resolution Still in transition marker /usr/share/ppd: directory not found comment Not all distributions have moved to supporting the standard comment PPD directory yet. quell end test /tset/LI18NUX2K.L1/utils/diff/T.diff 2 expected_severity failed resolution Waived comment Some utilities are not yet able to handle multibyte characters. comment The patches to fix this are not yet acceptable to some upstream comment maintainers. While this situation is being resolved, the failure comment of those utilities is not considered a violation of the spec. quell dup /tset/LI18NUX2K.L1/utils/diff/T.diff 3 dup /tset/LI18NUX2K.L1/utils/fold/T.fold 1 dup /tset/LI18NUX2K.L1/utils/fold/T.fold 2 dup /tset/LI18NUX2K.L1/utils/fold/T.fold 3 dup /tset/LI18NUX2K.L1/utils/join/T.join 3 dup /tset/LI18NUX2K.L1/utils/join/T.join 4 dup /tset/LI18NUX2K.L1/utils/pr/T.pr 1 dup /tset/LI18NUX2K.L1/utils/pr/T.pr 3 dup /tset/LI18NUX2K.L1/utils/pr/T.pr 4 dup /tset/LI18NUX2K.L1/utils/pr/T.pr 5 dup /tset/LI18NUX2K.L1/utils/pr/T.pr 6 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 8 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 9 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 10 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 11 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 12 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 13 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 14 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 15 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 16 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 24 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 25 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 26 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 27 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 28 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 29 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 30 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 31 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 32 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 40 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 41 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 42 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 43 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 44 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 45 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 46 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 47 dup /tset/LI18NUX2K.L1/utils/sort/T.sort 48 dup /tset/LI18NUX2K.L1/utils/unexpand/T.unexpand 1 dup /tset/LI18NUX2K.L1/utils/uniq/T.uniq 2 dup /tset/LI18NUX2K.L1/utils/uniq/T.uniq 3 dup /tset/LI18NUX2K.L1/utils/find/T.find 2 end test /tset/LI18NUX2K.L1/base/strptime/T.strptime 32 expected_severity failed resolution Unknown comment This test fails on newer distributions with certain versions of comment glibc. See comment bug 2040 comment in the LSB Bugzilla for more details. quell end test /tset/LI18NUX2K.L1/base/__wcstold_internal/T.__wcstold_internal 8 expected_severity failed resolution Unknown marker The return value is not correct. marker The errno is not correct. comment This error is seen on the ppc64 architecture. For more information, comment see bug comment 1771 in the LSB Bugzilla. dup /tset/LI18NUX2K.L1/base/wcstold/T.wcstold 8 quell end test /testfoomaticrip/testfoomaticrip 13 expected_severity failed resolution Unknown comment This test is too sensitive to specific conditions in the various comment distributions. quell end test /tset/POSIX.os/procprim/exec/T.execl 15 expected_severity failed resolution Test suite deficiency comment In newer kernel/glibc combinations, sysconf(_SC_ARG_MAX) is comment dynamic, and has a per-argument limit as well as a total comment buffer limit. The test does not take this into account. See comment bug comment 2288 for more information. quell dup /tset/POSIX.os/procprim/exec/T.execle 15 dup /tset/POSIX.os/procprim/exec/T.execlp 15 dup /tset/POSIX.os/procprim/exec/T.execv 15 dup /tset/POSIX.os/procprim/exec/T.execve 15 dup /tset/POSIX.os/procprim/exec/T.execvp 15 end test /tset/POSIX.os/procprim/exec/T.execl 16 expected_severity unresolved resolution Test suite deficiency comment This is a side effect of the failure of a previous test. quell dup /tset/POSIX.os/procprim/exec/T.execle 16 dup /tset/POSIX.os/procprim/exec/T.execlp 16 dup /tset/POSIX.os/procprim/exec/T.execv 16 dup /tset/POSIX.os/procprim/exec/T.execve 16 dup /tset/POSIX.os/procprim/exec/T.execvp 16 end test /tset/LSB.fhs/usr/x11r6/x11r6-tc 1 expected_severity failed resolution Test mistake marker /usr/X11R6: directory not found comment Contrary to the sense of this test, the /usr/X11R6 directory comment is not required to be present by the FHS. quell end test /tset/LI18NUX2K.L1/base/__cxa_atexit/T.__cxa_atexit 2 expected_severity unreported resolution Test suite deficiency marker libm.so: cannot open shared object file: No such file or directory comment The libm.so file is not required by the LSB. See comment bug 2545 comment in the LSB bug tracker for more information. quell end test /tset/ANSI.os/time/strftime/T.strftime 9 expected_severity failed resolution Upstream issue marker expected "ABC" comment Recent glibc versions have been optimizing how time conversion comment functions call tzset(). This may be a missed corner case. See comment bug 2577 comment in the LSB bug tracker for more information. quell end test /tests/functions/GtkTreeSelection/GtkTreeSelection 45 expected_severity failed resolution Unknown comment This is caused by a vendor patch commonly seen on newer comment Debian-based systems. See comment bug comment 2170 for more information. quell dup /tests/functions/GtkTreeSelection/GtkTreeSelection 46 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 47 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 48 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 49 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 50 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 51 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 52 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 53 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 54 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 55 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 56 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 57 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 58 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 59 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 60 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 61 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 62 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 63 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 64 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 65 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 66 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 67 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 68 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 69 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 170 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 171 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 172 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 173 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 174 dup /tests/functions/GtkTreeSelection/GtkTreeSelection 175 end test /libstdcxx-t2c/tests/codecvt/codecvt 28 expected_severity unresolved resolution Test setup problem marker terminated by signal 6 comment This can be triggered when the system locale database is rebuilt. comment When this happens, the test locales used by the test must be added comment again. This can be done by running the comment "/opt/lsb/test/cpp-t2c/locales/install_locale.sh" script comment as root. See comment bug 2506 comment for more information. dup /libstdcxx-t2c/tests/codecvt/codecvt 29 dup /libstdcxx-t2c/tests/codecvt/codecvt 30 dup /libstdcxx-t2c/tests/codecvt/codecvt 31 dup /libstdcxx-t2c/tests/codecvt/codecvt 34 dup /libstdcxx-t2c/tests/codecvt/codecvt 35 dup /libstdcxx-t2c/tests/ctype/ctype 10 dup /libstdcxx-t2c/tests/ctype/ctype 12 dup /libstdcxx-t2c/tests/ctype/ctype 14 dup /libstdcxx-t2c/tests/ctype/ctype 16 dup /libstdcxx-t2c/tests/ctype/ctype 18 dup /libstdcxx-t2c/tests/ctype/ctype 19 dup /libstdcxx-t2c/tests/ctype/ctype 20 dup /libstdcxx-t2c/tests/ctype/ctype 29 dup /libstdcxx-t2c/tests/ctype/ctype 30 dup /libstdcxx-t2c/tests/ctype/ctype 31 dup /libstdcxx-t2c/tests/ctype/ctype 33 dup /libstdcxx-t2c/tests/ctype/ctype 37 dup /libstdcxx-t2c/tests/ctype/ctype 38 dup /libstdcxx-t2c/tests/ctype/ctype 39 dup /libstdcxx-t2c/tests/ctype/ctype 42 dup /libstdcxx-t2c/tests/ctype/ctype 43 dup /libstdcxx-t2c/tests/ctype/ctype 50 dup /libstdcxx-t2c/tests/ctype/ctype 51 dup /libstdcxx-t2c/tests/ctype/ctype 52 dup /libstdcxx-t2c/tests/ctype/ctype 53 dup /libstdcxx-t2c/tests/ctype/ctype 54 dup /libstdcxx-t2c/tests/ctype/ctype 55 dup /libstdcxx-t2c/tests/ctype/ctype 58 dup /libstdcxx-t2c/tests/ctype/ctype 59 dup /libstdcxx-t2c/tests/ctype/ctype 61 dup /libstdcxx-t2c/tests/ctype/ctype 62 dup /libstdcxx-t2c/tests/ctype/ctype 64 dup /libstdcxx-t2c/tests/ctype/ctype 65 dup /libstdcxx-t2c/tests/ctype/ctype 73 dup /libstdcxx-t2c/tests/ctype/ctype 74 dup /libstdcxx-t2c/tests/ctype/ctype 75 dup /libstdcxx-t2c/tests/ctype/ctype 76 dup /libstdcxx-t2c/tests/ctype/ctype 77 dup /libstdcxx-t2c/tests/ctype/ctype 78 dup /libstdcxx-t2c/tests/ctype/ctype 79 dup /libstdcxx-t2c/tests/ctype/ctype 82 dup /libstdcxx-t2c/tests/ctype/ctype 83 dup /libstdcxx-t2c/tests/ctype/ctype 84 dup /libstdcxx-t2c/tests/ctype/ctype 87 dup /libstdcxx-t2c/tests/ctype/ctype 88 dup /libstdcxx-t2c/tests/ctype/ctype 91 dup /libstdcxx-t2c/tests/ctype/ctype 92 dup /libstdcxx-t2c/tests/ctype/ctype 95 dup /libstdcxx-t2c/tests/ctype/ctype 96 dup /libstdcxx-t2c/tests/ctype/ctype 99 dup /libstdcxx-t2c/tests/ctype/ctype 100 dup /libstdcxx-t2c/tests/ctype/ctype 109 dup /libstdcxx-t2c/tests/ctype/ctype 110 dup /libstdcxx-t2c/tests/ctype/ctype 111 dup /libstdcxx-t2c/tests/ctype/ctype 112 dup /libstdcxx-t2c/tests/ctype/ctype 113 dup /libstdcxx-t2c/tests/ctype/ctype 114 dup /libstdcxx-t2c/tests/ctype/ctype 115 dup /libstdcxx-t2c/tests/ctype/ctype 116 dup /libstdcxx-t2c/tests/ctype/ctype 117 dup /libstdcxx-t2c/tests/ctype/ctype 118 dup /libstdcxx-t2c/tests/ctype/ctype 119 dup /libstdcxx-t2c/tests/ctype/ctype 120 dup /libstdcxx-t2c/tests/ctype/ctype 123 dup /libstdcxx-t2c/tests/ctype/ctype 124 dup /libstdcxx-t2c/tests/ctype/ctype 125 dup /libstdcxx-t2c/tests/ctype/ctype 134 dup /libstdcxx-t2c/tests/ctype/ctype 135 dup /libstdcxx-t2c/tests/ctype/ctype 136 dup /libstdcxx-t2c/tests/ctype/ctype 137 dup /libstdcxx-t2c/tests/ctype/ctype 138 dup /libstdcxx-t2c/tests/ctype/ctype 139 dup /libstdcxx-t2c/tests/ctype/ctype 140 dup /libstdcxx-t2c/tests/ctype/ctype 141 dup /libstdcxx-t2c/tests/ctype/ctype 142 dup /libstdcxx-t2c/tests/ctype/ctype 143 dup /libstdcxx-t2c/tests/ctype/ctype 144 dup /libstdcxx-t2c/tests/ctype/ctype 145 dup /libstdcxx-t2c/tests/ctype/ctype 148 dup /libstdcxx-t2c/tests/ctype/ctype 149 dup /libstdcxx-t2c/tests/ctype/ctype 150 dup /libstdcxx-t2c/tests/time_get/time_get 4 dup /libstdcxx-t2c/tests/time_get/time_get 6 dup /libstdcxx-t2c/tests/time_get/time_get 8 dup /libstdcxx-t2c/tests/time_get/time_get 10 dup /libstdcxx-t2c/tests/time_get/time_get 11 dup /libstdcxx-t2c/tests/time_get/time_get 12 dup /libstdcxx-t2c/tests/time_get/time_get 25 dup /libstdcxx-t2c/tests/time_get/time_get 26 dup /libstdcxx-t2c/tests/time_get/time_get 27 dup /libstdcxx-t2c/tests/time_get/time_get 28 dup /libstdcxx-t2c/tests/time_get/time_get 35 dup /libstdcxx-t2c/tests/time_get/time_get 36 dup /libstdcxx-t2c/tests/time_get/time_get 37 dup /libstdcxx-t2c/tests/time_get/time_get 38 dup /libstdcxx-t2c/tests/time_get/time_get 39 dup /libstdcxx-t2c/tests/time_get/time_get 40 dup /libstdcxx-t2c/tests/collate/collate 13 dup /libstdcxx-t2c/tests/collate/collate 14 dup /libstdcxx-t2c/tests/collate/collate 15 dup /libstdcxx-t2c/tests/collate/collate 16 dup /libstdcxx-t2c/tests/collate/collate 17 dup /libstdcxx-t2c/tests/collate/collate 18 dup /libstdcxx-t2c/tests/collate/collate 27 dup /libstdcxx-t2c/tests/collate/collate 28 dup /libstdcxx-t2c/tests/collate/collate 29 dup /libstdcxx-t2c/tests/collate/collate 30 dup /libstdcxx-t2c/tests/collate/collate 31 dup /libstdcxx-t2c/tests/collate/collate 32 dup /libstdcxx-t2c/tests/collate/collate 33 dup /libstdcxx-t2c/tests/collate/collate 34 dup /libstdcxx-t2c/tests/collate/collate 35 dup /libstdcxx-t2c/tests/collate/collate 36 dup /libstdcxx-t2c/tests/collate/collate 37 dup /libstdcxx-t2c/tests/collate/collate 38 dup /libstdcxx-t2c/tests/collate/collate 39 dup /libstdcxx-t2c/tests/collate/collate 40 dup /libstdcxx-t2c/tests/collate/collate 41 dup /libstdcxx-t2c/tests/collate/collate 42 dup /libstdcxx-t2c/tests/collate/collate 43 dup /libstdcxx-t2c/tests/collate/collate 50 dup /libstdcxx-t2c/tests/collate/collate 51 dup /libstdcxx-t2c/tests/collate/collate 52 dup /libstdcxx-t2c/tests/collate/collate 53 dup /libstdcxx-t2c/tests/collate/collate 54 dup /libstdcxx-t2c/tests/collate/collate 55 dup /libstdcxx-t2c/tests/collate/collate 56 dup /libstdcxx-t2c/tests/collate/collate 57 dup /libstdcxx-t2c/tests/collate/collate 58 dup /libstdcxx-t2c/tests/collate/collate 65 dup /libstdcxx-t2c/tests/collate/collate 66 dup /libstdcxx-t2c/tests/collate/collate 67 dup /libstdcxx-t2c/tests/collate/collate 68 dup /libstdcxx-t2c/tests/collate/collate 69 dup /libstdcxx-t2c/tests/collate/collate 70 dup /libstdcxx-t2c/tests/collate/collate 71 dup /libstdcxx-t2c/tests/collate/collate 72 dup /libstdcxx-t2c/tests/collate/collate 73 dup /libstdcxx-t2c/tests/time_put/time_put 38 dup /libstdcxx-t2c/tests/time_put/time_put 39 dup /libstdcxx-t2c/tests/time_put/time_put 40 dup /libstdcxx-t2c/tests/time_put/time_put 41 dup /libstdcxx-t2c/tests/time_put/time_put 42 dup /libstdcxx-t2c/tests/time_put/time_put 43 dup /libstdcxx-t2c/tests/time_put/time_put 44 dup /libstdcxx-t2c/tests/time_put/time_put 45 dup /libstdcxx-t2c/tests/time_put/time_put 46 dup /libstdcxx-t2c/tests/time_put/time_put 47 dup /libstdcxx-t2c/tests/time_put/time_put 48 dup /libstdcxx-t2c/tests/time_put/time_put 49 dup /libstdcxx-t2c/tests/time_put/time_put 50 dup /libstdcxx-t2c/tests/time_put/time_put 51 dup /libstdcxx-t2c/tests/time_put/time_put 52 dup /libstdcxx-t2c/tests/time_put/time_put 53 dup /libstdcxx-t2c/tests/time_put/time_put 54 dup /libstdcxx-t2c/tests/time_put/time_put 55 dup /libstdcxx-t2c/tests/time_put/time_put 56 dup /libstdcxx-t2c/tests/time_put/time_put 57 dup /libstdcxx-t2c/tests/time_put/time_put 58 dup /libstdcxx-t2c/tests/time_put/time_put 59 dup /libstdcxx-t2c/tests/time_put/time_put 60 dup /libstdcxx-t2c/tests/time_put/time_put 61 dup /libstdcxx-t2c/tests/time_put/time_put 62 dup /libstdcxx-t2c/tests/time_put/time_put 63 dup /libstdcxx-t2c/tests/time_put/time_put 64 dup /libstdcxx-t2c/tests/time_put/time_put 65 dup /libstdcxx-t2c/tests/time_put/time_put 66 dup /libstdcxx-t2c/tests/time_put/time_put 67 dup /libstdcxx-t2c/tests/time_put/time_put 68 dup /libstdcxx-t2c/tests/time_put/time_put 69 dup /libstdcxx-t2c/tests/time_put/time_put 70 dup /libstdcxx-t2c/tests/time_put/time_put 71 dup /libstdcxx-t2c/tests/time_put/time_put 72 dup /libstdcxx-t2c/tests/time_put/time_put 73 dup /libstdcxx-t2c/tests/time_put/time_put 74 dup /libstdcxx-t2c/tests/time_put/time_put 112 dup /libstdcxx-t2c/tests/time_put/time_put 113 dup /libstdcxx-t2c/tests/time_put/time_put 114 dup /libstdcxx-t2c/tests/time_put/time_put 115 dup /libstdcxx-t2c/tests/time_put/time_put 116 dup /libstdcxx-t2c/tests/time_put/time_put 117 dup /libstdcxx-t2c/tests/time_put/time_put 118 dup /libstdcxx-t2c/tests/time_put/time_put 119 dup /libstdcxx-t2c/tests/time_put/time_put 120 dup /libstdcxx-t2c/tests/time_put/time_put 121 dup /libstdcxx-t2c/tests/time_put/time_put 122 dup /libstdcxx-t2c/tests/time_put/time_put 123 dup /libstdcxx-t2c/tests/time_put/time_put 124 dup /libstdcxx-t2c/tests/time_put/time_put 125 dup /libstdcxx-t2c/tests/time_put/time_put 126 dup /libstdcxx-t2c/tests/time_put/time_put 127 dup /libstdcxx-t2c/tests/time_put/time_put 128 dup /libstdcxx-t2c/tests/time_put/time_put 129 dup /libstdcxx-t2c/tests/time_put/time_put 130 dup /libstdcxx-t2c/tests/time_put/time_put 131 dup /libstdcxx-t2c/tests/time_put/time_put 132 dup /libstdcxx-t2c/tests/time_put/time_put 133 dup /libstdcxx-t2c/tests/time_put/time_put 134 dup /libstdcxx-t2c/tests/time_put/time_put 135 dup /libstdcxx-t2c/tests/time_put/time_put 136 dup /libstdcxx-t2c/tests/time_put/time_put 137 dup /libstdcxx-t2c/tests/time_put/time_put 138 dup /libstdcxx-t2c/tests/time_put/time_put 139 dup /libstdcxx-t2c/tests/time_put/time_put 140 dup /libstdcxx-t2c/tests/time_put/time_put 141 dup /libstdcxx-t2c/tests/time_put/time_put 142 dup /libstdcxx-t2c/tests/time_put/time_put 143 dup /libstdcxx-t2c/tests/time_put/time_put 144 dup /libstdcxx-t2c/tests/time_put/time_put 145 dup /libstdcxx-t2c/tests/time_put/time_put 146 dup /libstdcxx-t2c/tests/time_put/time_put 147 dup /libstdcxx-t2c/tests/time_put/time_put 148 dup /libstdcxx-t2c/tests/time_put/time_put 156 dup /libstdcxx-t2c/tests/time_put/time_put 157 dup /libstdcxx-t2c/tests/time_put/time_put 158 dup /libstdcxx-t2c/tests/time_put/time_put 159 dup /libstdcxx-t2c/tests/time_put/time_put 160 dup /libstdcxx-t2c/tests/time_put/time_put 161 dup /libstdcxx-t2c/tests/time_put/time_put 162 dup /libstdcxx-t2c/tests/time_put/time_put 170 dup /libstdcxx-t2c/tests/time_put/time_put 171 dup /libstdcxx-t2c/tests/time_put/time_put 172 dup /libstdcxx-t2c/tests/time_put/time_put 173 dup /libstdcxx-t2c/tests/time_put/time_put 174 dup /libstdcxx-t2c/tests/time_put/time_put 175 dup /libstdcxx-t2c/tests/time_put/time_put 176 dup /libstdcxx-t2c/tests/time_put/time_put 190 dup /libstdcxx-t2c/tests/time_put/time_put 191 dup /libstdcxx-t2c/tests/time_put/time_put 192 dup /libstdcxx-t2c/tests/time_put/time_put 193 dup /libstdcxx-t2c/tests/time_put/time_put 194 dup /libstdcxx-t2c/tests/time_put/time_put 195 dup /libstdcxx-t2c/tests/time_put/time_put 196 dup /libstdcxx-t2c/tests/time_put/time_put 197 dup /libstdcxx-t2c/tests/time_put/time_put 198 dup /libstdcxx-t2c/tests/time_put/time_put 199 dup /libstdcxx-t2c/tests/time_put/time_put 200 dup /libstdcxx-t2c/tests/time_put/time_put 201 dup /libstdcxx-t2c/tests/time_put/time_put 202 dup /libstdcxx-t2c/tests/time_put/time_put 216 dup /libstdcxx-t2c/tests/time_put/time_put 217 dup /libstdcxx-t2c/tests/time_put/time_put 218 dup /libstdcxx-t2c/tests/time_put/time_put 219 dup /libstdcxx-t2c/tests/time_put/time_put 220 dup /libstdcxx-t2c/tests/time_put/time_put 221 dup /libstdcxx-t2c/tests/time_put/time_put 222 dup /libstdcxx-t2c/tests/time_put/time_put 223 dup /libstdcxx-t2c/tests/time_put/time_put 224 dup /libstdcxx-t2c/tests/time_put/time_put 225 dup /libstdcxx-t2c/tests/time_put/time_put 226 dup /libstdcxx-t2c/tests/time_put/time_put 227 dup /libstdcxx-t2c/tests/time_put/time_put 228 dup /libstdcxx-t2c/tests/time_put/time_put 233 dup /libstdcxx-t2c/tests/time_put/time_put 234 dup /libstdcxx-t2c/tests/time_put/time_put 235 dup /libstdcxx-t2c/tests/time_put/time_put 236 dup /libstdcxx-t2c/tests/time_put/time_put 241 dup /libstdcxx-t2c/tests/time_put/time_put 242 dup /libstdcxx-t2c/tests/time_put/time_put 243 dup /libstdcxx-t2c/tests/time_put/time_put 244 dup /libstdcxx-t2c/tests/time_put/time_put 247 dup /libstdcxx-t2c/tests/time_put/time_put 248 dup /libstdcxx-t2c/tests/time_put/time_put 251 dup /libstdcxx-t2c/tests/time_put/time_put 252 end test /tset/lsb_release/testcases/lsb_release/lsb_release-tc 2 expected_severity failed resolution Distribution problem comment The lsb_release command is not reporting that the distribution comment attempts to be compliant with the version of the LSB being comment tested. Update the lsb_release command to report this comment LSB version. end test /tset/initd/misc/install/general-tc 1 expected_severity failed resolution Specification ambiguity comment There is disagreement about the interpretation of the LSB comment init script specification; specifically, whether certain comment fields may be optional. See comment bug 2479 comment for details. quell end test /tset/POSIX.os/ioprim/select/T.select 6 expected_severity failed resolution Test suite deficiency marker errno is expected to be 22[EINVAL] comment This is caused by a bug in the test. Please see comment bug 2528 comment in the LSB bug tracker for more information. quell end test /tset/LSB.os/network/accept/T.accept 7 expected_severity failed resolution Test suite deficiency marker errno is set to 14 comment This is caused by a bug in the test. Please see comment bug 2529 comment in the LSB bug tracker for more information. quell end test /tset/LSB.os/network/setsockopt/T.setsockopt 3 expected_severity failed resolution Test suite deficiency marker setsockopt() returned 0, expected to return -1 comment This is caused by a bug in the test. Please see comment bug 2530 comment in the LSB bug tracker for more information. quell end test /tset/LSB.os/network/connect/T.connect 2 expected_severity failed resolution Inappropriate reliance on network comment This test will often report failures depending on what network a comment host may be on, or whether Internet access is available. See comment bug 2332 comment in the LSB Bugzilla for more information. quell end test /tset/LSB.fhs/usr/share-misc/share-misc-tc 3 expected_severity failed resolution Test suite deficiency marker /usr/share/misc/magic: file not found comment Since this is an optional component, it should not fail. quell end test /tset/profile.d/testcases/profile.d/profile.d-tc 2 expected_severity failed resolution Known problem marker Expected $LSB_CORE_TEST_VAL to be set to 'ABC123', got '' comment This problem occurs when scripts in /etc/profile.d are not comment read by the shell at startup. quell end test /tset/POSIX.os/ioprim/pipe/T.pipe 4 expected_severity failed resolution Possible test bug marker deletion reason: unable to find an unused file descriptor comment The method used to determine the lowest-number unused file comment descriptor does not seem to work on newer distributions. See comment bug 2627 comment on the LSB Bugzilla for more information. quell end # --- printing --- test /testfoomaticrip/testfoomaticrip 3 expected_severity failed resolution Upstream bug comment Some snapshots of foomatic 3.x contained a regression that comment has produced incorrect behavior. Upstream has fixed the bug, comment and recommends that all distributions failing this test comment upgrade to a version of foomatic 3.x newer than 2008-11-19. comment More information is available at comment bug comment 2418 on the LSB bug tracker. dup /testfoomaticrip/testfoomaticrip 11 end test /testgs/testgs 5 expected_severity failed resolution Test suite deficiency marker /usr/bin/gs returned 1 using the ijs driver, expected 0 comment The test requires that hpijs be installed, which is not comment specified. See comment bug 2553 comment in the LSB Bugzilla for more information. quell end # --- pango --- test /pango-t2c/tests/pango_matrix/pango_matrix 1 expected_severity failed resolution Known problem marker The yy part oth the matrix was not calculated properly comment This failure occurs due to the following problem:
comment There was a typo in implementation of this function. It was reported and it is fixed now.
comment Detailed description of this problem is available here. end test /pango-t2c/tests/pango_language/pango_language 4 expected_severity failed resolution Known problem marker This stripping was no good comment This failure occurs due to the following problem:
comment Probably pango version is too old.
dup /pango-t2c/tests/pango_language/pango_language 9 dup /pango-t2c/tests/pango_language/pango_language 10 end # --- cmdchk --- # --- libstdcpp --- test /22_locale/codecvt/always_noconv/char/wrapped_locale.cc 1 expected_severity failed resolution Missing locales marker locale name not valid comment Some of the locales used for this test are missing. Please comment see the comment gcc manual comment for the list of locales used by the test suites, and install comment them on the test machine. dup /22_locale/codecvt/always_noconv/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/encoding/char/wrapped_locale.cc 1 dup /22_locale/codecvt/encoding/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/in/char/wrapped_locale.cc 1 dup /22_locale/codecvt/in/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/length/char/wrapped_locale.cc 1 dup /22_locale/codecvt/length/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/max_length/char/wrapped_locale.cc 1 dup /22_locale/codecvt/max_length/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/out/char/wrapped_locale.cc 1 dup /22_locale/codecvt/out/wchar_t/wrapped_locale.cc 1 dup /22_locale/codecvt/unshift/char/wrapped_locale.cc 1 dup /22_locale/codecvt/unshift/wchar_t/wrapped_locale.cc 1 dup /22_locale/collate/compare/char/wrapped_locale.cc 1 dup /22_locale/collate/compare/wchar_t/wrapped_locale.cc 1 dup /22_locale/collate/hash/char/wrapped_locale.cc 1 dup /22_locale/collate/hash/wchar_t/wrapped_locale.cc 1 dup /22_locale/collate/transform/char/wrapped_locale.cc 1 dup /22_locale/collate/transform/wchar_t/wrapped_locale.cc 1 dup /22_locale/ctype/cons/char/wrapped_locale.cc 1 dup /22_locale/ctype/is/char/wrapped_locale.cc 1 dup /22_locale/ctype/is/wchar_t/wrapped_locale.cc 1 dup /22_locale/ctype/narrow/char/wrapped_locale.cc 1 dup /22_locale/ctype/narrow/wchar_t/wrapped_locale.cc 1 dup /22_locale/ctype/scan/char/wrapped_locale.cc 1 dup /22_locale/ctype/scan/wchar_t/wrapped_locale.cc 1 dup /22_locale/ctype/to/char/wrapped_locale.cc 1 dup /22_locale/ctype/to/wchar_t/wrapped_locale.cc 1 dup /22_locale/ctype/widen/char/wrapped_locale.cc 1 dup /22_locale/ctype/widen/wchar_t/wrapped_locale.cc 1 dup /22_locale/messages/members/char/wrapped_locale.cc 1 dup /22_locale/money_get/get/char/wrapped_locale.cc 1 dup /22_locale/money_get/get/wchar_t/wrapped_locale.cc 1 dup /22_locale/money_put/put/char/wrapped_locale.cc 1 dup /22_locale/money_put/put/wchar_t/wrapped_locale.cc 1 dup /22_locale/moneypunct/members/char/wrapped_locale.cc 1 dup /22_locale/moneypunct/members/wchar_t/wrapped_locale.cc 1 dup /22_locale/num_get/get/char/wrapped_locale.cc 1 dup /22_locale/num_get/get/wchar_t/wrapped_locale.cc 1 dup /22_locale/num_put/put/char/wrapped_locale.cc 1 dup /22_locale/num_put/put/wchar_t/wrapped_locale.cc 1 dup /22_locale/numpunct/members/char/wrapped_locale.cc 1 dup /22_locale/numpunct/members/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/date_order/char/wrapped_locale.cc 1 dup /22_locale/time_get/date_order/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/get_date/char/wrapped_locale.cc 1 dup /22_locale/time_get/get_date/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/get_monthname/char/wrapped_locale.cc 1 dup /22_locale/time_get/get_monthname/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/get_time/char/wrapped_locale.cc 1 dup /22_locale/time_get/get_time/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/get_weekday/char/wrapped_locale.cc 1 dup /22_locale/time_get/get_weekday/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_get/get_year/char/wrapped_locale.cc 1 dup /22_locale/time_get/get_year/wchar_t/wrapped_locale.cc 1 dup /22_locale/time_put/put/char/wrapped_locale.cc 1 dup /22_locale/time_put/put/wchar_t/wrapped_locale.cc 1 dup /27_io/basic_filebuf/imbue/wchar_t/12868.cc 1 dup /27_io/basic_streambuf/imbue/char/13007-1.cc 1 dup /27_io/basic_streambuf/imbue/wchar_t/13007-1.cc 1 end test /22_locale/money_put/put/char/9780-3.cc 1 expected_severity failed resolution Test suite deficiency comment This is caused by a test that is overly sensitive to the output comment text. See comment bug 2596 comment in the LSB Bugzilla for more information. quell end test /22_locale/time_get/get_date/wchar_t/4.cc 1 expected_severity failed resolution Known problem comment This is thought to be related to an upstream bug in the C++ library. comment See the comment linuxtesting.org report for details. quell end test /22_locale/money_get/get/char/1.cc 1 expected_severity failed resolution Locale database issue comment Some versions of Ubuntu have a bug in their locale databases comment where the local money symbol (the Euro symbol) is not displayed comment for at least the German locale using the ISO 8859-15 character comment set (the text letters "EUR" appear instead). The C++ locale support comment code in question is actually working properly, in that it reports comment the value that is stored in the database. As the LSB does not comment specify the contents of the locale database, this bug is not an comment issue with the LSB. It should not affect Ubuntu-based distributions, comment as they have moved exclusively to UTF-8 (where the problem does not comment appear). dup /22_locale/money_get/get/char/wrapped_env.cc 1 dup /22_locale/money_get/get/char/wrapped_locale.cc 1 dup /22_locale/money_get/get/wchar_t/1.cc 1 dup /22_locale/money_get/get/wchar_t/wrapped_env.cc 1 dup /22_locale/money_get/get/wchar_t/wrapped_locale.cc 1 dup /22_locale/money_put/put/char/1.cc 1 dup /22_locale/money_put/put/char/3.cc 1 dup /22_locale/money_put/put/char/wrapped_env.cc 1 dup /22_locale/money_put/put/char/wrapped_locale.cc 1 dup /22_locale/money_put/put/wchar_t/1.cc 1 dup /22_locale/money_put/put/wchar_t/3.cc 1 dup /22_locale/money_put/put/wchar_t/wrapped_env.cc 1 dup /22_locale/money_put/put/wchar_t/wrapped_locale.cc 1 quell end test /27_io/basic_istream/extractors_other/char/1.cc 1 expected_severity failed resolution Unknown comment This failure is currrently being evaluated. See comment bug 2533 comment in the LSB Bugzilla for more information. quell dup /27_io/basic_istream/extractors_other/wchar_t/1.cc 1 end test /26_numerics/complex/13450.cc 1 expected_severity failed resolution Unknown marker void test01_do(T, T) [with T = long double]: Assertion `abs(ref - res1) < eps' failed. comment This is caused by improper precision in measuring the long double comment result. Please see comment bug 2447 comment in the LSB bug tracker for more information. quell end test /27_io/basic_istream/extractors_arithmetic/char/exceptions_badbit_throw.cc 1 expected_severity failed resolution Unknown marker void test_badbit() [with T = bool]: Assertion `false' failed. comment Please see comment bug 2450 comment in the LSB bug tracker for more information. dup /27_io/basic_istream/extractors_arithmetic/wchar_t/exceptions_badbit_throw.cc 1 dup /27_io/basic_ostream/inserters_arithmetic/char/exceptions_badbit_throw.cc 1 dup /27_io/basic_ostream/inserters_arithmetic/wchar_t/exceptions_badbit_throw.cc 1 quell end # --- qt4 --- test tst_QTextDocumentFragment_html_anchorColor 112 expected_severity failed resolution Unknown comment This problem appears to be caused by an interaction with Qt 4.4 comment and Xvfb. For more information, see comment bug 2517 comment in the LSB Bugzilla. quell end test tst_QColor_setNamedColor 4 expected_severity failed resolution Unknown comment These failures are seen with Qt 4.4. See comment bug 2519 comment in the LSB Bugzilla for more details. quell dup tst_QItemSelectionModel_selectedRows 10 dup tst_QLineEdit_selectedText 30 dup tst_QPixmapCache_cacheLimit 1 dup tst_QTreeView_construction 2 dup tst_QTreeView_itemDelegate 14 dup tst_QUuid_less 6 dup tst_QItemSelectionModel_selectedColumns 11 end test tst_QDataWidgetMapper_mappedWidgetAt 7 expected_severity failed resolution Test suite deficiency comment The Qt 4 tests assume that some changes made in Qt 4.2.3 were comment made, when they should not have. See comment bug 2515 comment in the LSB Bugzilla for more details. quell dup tst_QHeaderView_moveSectionAndReset 38 dup tst_QLabel_focusPolicy 13 dup tst_QListView_batchedMode 16 dup tst_QStyleOption_qstyleoptioncast 1 dup tst_QTableWidget_itemData 18 dup tst_QTextDocumentFragment_html_rowSpans2 109 dup tst_QTextDocumentFragment_css_nodeNameCaseInsensitivity 123 dup tst_QTextTable_splitCells 14 end test tst_QListView_singleSelectionRemoveRow 12 expected_severity failed resolution Possible test suite issue marker Compared values are not the same comment When the current item in a QListView is deleted, the Qt spec comment does not appear to define which item becomes current, but the comment test assumes that the preceding item becomes current. See comment bug 2601 comment in the LSB Bugzilla for more information. quell end test tst_QMetaObject_invokeQueuedMetaMember 3 expected_severity failed resolution Test suite deficiency marker QMetaMethod::invoke comment The test expects a specific message to be received to indicate comment success of the test, which does not take into account the comment possibility of that string changing in the implementation. See comment bug 2602 comment in the LSB Bugzilla for more information. quell end test tst_QTextDocumentFragment_whitespaceWithFragmentMarkers 66 expected_severity failed resolution Possible test issue comment The test assumes that whitespace added to the HTML document comment is unchanged when converted to plain text, but that assumption comment is not mentioned in the spec. See comment bug 2603 comment in the LSB Bugzilla for more information. quell end test tst_QDateTime_addSecs 18 expected_severity failed resolution Possible test issue comment There is some dispute as to whether this test properly calculates comment the time zone in these cases. See comment bug 2505 comment in the LSB Bugzilla for more information. quell dup tst_QDateTime_addMSecs 19 dup tst_QDateTime_toTimeSpec 20 dup tst_QDateTime_toLocalTime 21 dup tst_QDateTime_toUTC 22 dup tst_QDateTime_secsTo 24 end test tst_QItemModel_rowCount 2 expected_severity failed resolution Missing test requirement comment Although not specified in the LSB, the tests for Qt 4 database comment support require a working database driver. This is best comment supplied by installing the SQLite driver for Qt 4. Installing comment this driver should cause this test to pass. dup tst_QItemModel_columnCount 3 dup tst_QItemModel_hasIndex 4 dup tst_QItemModel_index 5 dup tst_QItemModel_data 7 dup tst_QItemModel_sort 12 end # --- azov-qt4 --- test /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 1 expected_severity failed resolution Missing test requirement comment Although not specified in the LSB, the tests for Qt 4 database comment support require a working database driver. This is best comment supplied by installing the SQLite driver for Qt 4. Installing comment this driver should cause this test to pass. dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 2 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 3 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 4 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 7 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 11 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 13 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 18 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 19 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 20 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 21 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 22 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 23 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 24 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 25 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 26 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 28 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 30 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 32 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 33 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 34 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 35 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 36 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 37 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 39 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 41 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 43 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 44 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 45 dup /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase 46 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 1 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 6 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 7 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 12 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 17 dup /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel 18 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 2 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 3 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 6 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 9 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 13 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 18 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 19 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 20 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 22 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 26 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 38 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 41 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 42 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 43 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 46 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 47 dup /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 48 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 5 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 6 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 8 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 12 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 14 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 15 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 21 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 24 dup /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel 27 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 2 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 4 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 5 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 6 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 7 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 8 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 9 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 11 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 13 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 14 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 15 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 16 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 17 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 18 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 22 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 25 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 27 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 31 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 32 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 35 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 36 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 38 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 39 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 43 dup /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery 44 end test /Qt4_Drag_and_Drop-t2c/tests/QDropEvent/QDropEvent 3 expected_severity failed resolution Test suite deficiency comment Newer versions of Qt allow new drop actions, but the test assumes comment these drop actions will fail. See comment bug 2598 comment in the LSB Bugzilla for more information. quell end test /Qt4_Network-t2c/tests/QNetworkAddressEntry/QNetworkAddressEntry 11 expected_severity failed resolution Test suite deficiency comment This test fails to account for a different netmask in the presence comment of IPv6. See comment bug 2599 comment in the LSB Bugzilla for more information. quell end test /Qt4_Widgets-t2c/tests/QDial/QDial 7 expected_severity unresolved resolution Unknown comment On newer versions of Qt, this test crashes. See comment bug 2600 comment in the LSB Bugzilla for more information. quell end test /Qt4_Paint_Device-t2c/tests/QPrinter/QPrinter 7 expected_severity failed resolution Test suite deficiency comment This failure is caused by an incorrect test. See comment bug 2614 comment in the LSB Bugzilla for more information. quell dup /Qt4_Paint_Device-t2c/tests/QPrinter/QPrinter 36 dup /Qt4_Paint_Device-t2c/tests/QPrinter/QPrinter 53 end test /Qt4_Menus-t2c/tests/QMenuBar/QMenuBar 22 expected_severity failed resolution Test suite deficiency marker CONSTRAINT FOR RETURN FAILED: '$0 > 0' comment This is caused by a bug in the test suite, which has been fixed comment in newer versions of the test suite. quell end # --- xts5 --- test /tset/Xlib8/flushgc/Test 1 expected_severity unresolved resolution Possible test issue marker unexpected signal 6 (SIGABRT) received comment This may be an issue with the test's use of xcb. See comment bug 2636 comment in the LSB Bugzilla for more information. quell dup /tset/Xlib8/flushgc/Test 2 end test /tset/Xlib13/grbpntr/Test 20 expected_severity failed resolution Possible test issue comment This failure occasionally happens when the test suite is run comment on a virtual machine. So far, it hasn't been seen on a native comment test run. See comment bug 2532 comment in the LSB Bugzilla for more information. quell end test /tset/Xlib12/sndevnt/Test 21 expected_severity unresolved resolution Test interaction issue with extension comment These tests do not appear to interact well with the XGE extension. See comment bug 2581 comment in the LSB Bugzilla for more information. quell end test /tset/Xlib12/staftrfnct/Test 1 expected_severity failed resolution Test interaction issue with extension comment These tests do not appear to interact well with the XGE extension. See comment bug 2581 comment in the LSB Bugzilla for more information. quell end # --- python --- test /usr/bin/python 21 expected_severity failed resolution Unknown comment This failure occurs on some distributions, and may be a test comment issue. See comment bug 2516 comment in the LSB Bugzilla for details. quell end test /usr/bin/python 54 expected_severity failed resolution Possible test issue comment This may be caused on systems where the "site-packages" directory comment is not on sys.path. See comment bug 2595 comment in the LSB Bugzilla for details. quell end test /usr/bin/python 87 expected_severity failed resolution Possible network issue marker gaierror: [Errno -2] Name or service not known comment This may be caused when the hostname of the test machine cannot comment be resolved. end # --- perl --- test ../ext/B/t/concise-xs.t 768 expected_severity failed resolution Test suite deficency comment The Perl tests, in some cases, depend on Perl internals that are comment allowed to change. When this happens, we waive the results. See comment bug 1889 comment in the LSB Bugzilla for details. quell dup ../ext/B/t/concise-xs.t 752 dup ../ext/B/t/f_sort.t 763 dup ../ext/B/t/f_sort.t 776 dup ../ext/B/t/f_map.t 758 dup ../ext/B/t/f_map.t 778 dup ../ext/Devel/Peek/t/Peek.t 658 dup ../ext/Devel/Peek/t/Peek.t 827 end test ../lib/Pod/t/htmlview.t 437 expected_severity failed resolution Test suite deficiency comment A number of tests in the Perl test suite have been determined to be comment inappropriate for testing the API, and have been dropped. See comment bug 2508 comment in the LSB bug tracker for more information. quell dup ../lib/Pod/t/basic.t 448 dup ../lib/ExtUtils/t/INST.t 583 dup ../lib/ExtUtils/t/INST_PREFIX.t 591 dup ../lib/ExtUtils/t/Embed.t 592 end test ../lib/Term/Cap.t 380 expected_severity failed resolution Test suite deficiency comment The /etc/termcap file, required for this test, is not required by comment the LSB. quell end test op/groups.t 110 expected_severity failed resolution Test suite deficiency comment This is caused by older versions of DTK Manager, when running comment the Perl tests with an incorrect path. See comment bug 2567 comment in the LSB Bugzilla for more information. quell end test ../lib/Benchmark.t 420 expected_severity failed resolution Timing issue comment This failure has been seen occasionally when running the test comment suite within a VM. Try running the test again, or run the tests comment on native hardware. end test ../ext/Sys/Syslog/t/syslog.t 686 expected_severity failed resolution Test suite deficiency comment The facility used to test the syslog module doesn't work on some comment distributions. The facility is not required to work by the comment specification. See comment bug 2613 comment in the LSB Bugzilla for more information. quell end test ../lib/Net/Ping/t/200_ping_tcp.t 655 expected_severity unreported comment This may happen on machines without Internet access. quell FIP dup ../lib/Net/Ping/t/400_ping_syn.t 657 dup ../lib/Net/Ping/t/410_syn_host.t 658 end # --- libchk --- test libstdc++.so.6 3144 expected_severity failed resolution Known problem comment This problem is caused by a bug in libstdc++ from gcc versions comment before 4.3. See comment bug 1235 comment in the LSB Bugzilla for more information. quell dup libstdc++.so.6 3152 end # these are the same tests as the previous two, # but bug 2745 caused the test numbers to all change test libstdc++.so.6 151 expected_severity failed resolution Known problem comment This problem is caused by a bug in libstdc++ from gcc versions comment before 4.3. See comment bug 2844 comment in the LSB Bugzilla for more information. quell dup libstdc++.so.6 159 end test libasound.so.2 1 expected_severity failed resolution Trial Use Module marker Unable to find library comment The ALSA module is classified as trial use, and so distributions comment are not required to provide this library. quell end test libnspr4.so 1 expected_severity failed resolution Trial Use Module marker Unable to find library comment The NSS module is classified as trial use, and so distributions comment are not required to provide this library. quell dup libnss3.so 1 dup libssl3.so 1 end # --- gtkvts --- test /tests/functions/GdkImages/GdkImages 2 expected_severity failed resolution Test suite deficiency marker it's not a GDK_TYPE_IMAGE comment When run under Xvfb, some of the test images aren't registered comment correctly for some reason. See comment bug 1893 comment in the LSB Bugzilla for more information. quell end test /tests/functions/GtkToolbar/GtkToolbar 15 expected_severity failed resolution Specification deficiency marker tooltips is 1, should be 0 comment The tooltip ABI changed upstream in a compatible way. quell end test /tests/functions/GMisc/GMisc 2 expected_severity failed resolution Known problem marker g_get_prgname: failed comment This was an upstream regression with glib-2.23 comment See GNOME bug 563627 comment or LSB bug 2849 for more information end test /tests/functions/GTimer/GTimer 2 expected_severity failed resolution Timing problem when testing in a VM comment When running the tests within a virtual machine, the timing comment may differ from the expected timing on native hardware. comment Try running the tests using a different VM technology, or comment on a non-virtualized system. dup /tests/functions/MainLoop/MainLoop 6 dup /tests/functions/MainLoop/MainLoop 7 end test /tests/functions/GdkCursors/GdkCursors 9 expected_severity failed resolution Possible test issue comment This test uses reference counting to determine test success or comment failure, but does not take into account the possibility of comment additional references being created by the implementation. See comment bug 2589 comment in the LSB Bugzilla for more information. quell dup /tests/functions/GdkCursors/GdkCursors 10 dup /tests/functions/GdkCursors/GdkCursors 11 dup /tests/functions/GdkCursors/GdkCursors 12 dup /tests/functions/GdkCursors/GdkCursors 13 dup /tests/functions/GdkCursors/GdkCursors 14 dup /tests/functions/GdkCursors/GdkCursors 15 dup /tests/functions/GdkCursors/GdkCursors 16 dup /tests/functions/GdkCursors/GdkCursors 17 dup /tests/functions/GdkCursors/GdkCursors 18 dup /tests/functions/GdkCursors/GdkCursors 19 dup /tests/functions/GdkCursors/GdkCursors 20 dup /tests/functions/GdkCursors/GdkCursors 21 dup /tests/functions/GdkCursors/GdkCursors 22 dup /tests/functions/GdkCursors/GdkCursors 23 dup /tests/functions/GdkCursors/GdkCursors 24 end test /tests/functions/GtkEntry/GtkEntry 20 expected_severity failed resolution Test suite deficiency marker text length is 0 but it should be > 0 comment GTK+ has disabled clipboard functions for invisible entry comment widgets. See comment bug 2589 comment in the LSB Bugzilla for more information. quell dup /tests/functions/GtkEntry/GtkEntry 21 dup /tests/functions/GtkEntry/GtkEntry 22 dup /tests/functions/GtkEntry/GtkEntry 23 dup /tests/functions/GtkEntry/GtkEntry 28 dup /tests/functions/GtkEntry/GtkEntry 29 dup /tests/functions/GtkEntry/GtkEntry 30 dup /tests/functions/GtkEntry/GtkEntry 31 dup /tests/functions/GtkEntry/GtkEntry 32 dup /tests/functions/GtkEntry/GtkEntry 33 dup /tests/functions/GtkEntry/GtkEntry 34 dup /tests/functions/GtkEntry/GtkEntry 35 dup /tests/functions/GtkEntry/GtkEntry 36 dup /tests/functions/GtkEntry/GtkEntry 37 dup /tests/functions/GtkEntry/GtkEntry 38 dup /tests/functions/GtkEntry/GtkEntry 39 dup /tests/functions/GtkEntry/GtkEntry 40 dup /tests/functions/GtkEntry/GtkEntry 41 dup /tests/functions/GtkEntry/GtkEntry 42 dup /tests/functions/GtkEntry/GtkEntry 43 dup /tests/functions/GtkEntry/GtkEntry 44 dup /tests/functions/GtkEntry/GtkEntry 45 dup /tests/functions/GtkEntry/GtkEntry 46 dup /tests/functions/GtkEntry/GtkEntry 47 dup /tests/functions/GtkEntry/GtkEntry 48 dup /tests/functions/GtkEntry/GtkEntry 49 dup /tests/functions/GtkEntry/GtkEntry 50 dup /tests/functions/GtkEntry/GtkEntry 51 dup /tests/functions/GtkEntry/GtkEntry 52 dup /tests/functions/GtkEntry/GtkEntry 53 dup /tests/functions/GtkEntry/GtkEntry 54 dup /tests/functions/GtkEntry/GtkEntry 55 dup /tests/functions/GtkEntry/GtkEntry 56 dup /tests/functions/GtkEntry/GtkEntry 57 dup /tests/functions/GtkEntry/GtkEntry 58 dup /tests/functions/GtkEntry/GtkEntry 59 end test /tests/functions/GtkAdjustment/GtkAdjustment 61 expected_severity failed resolution Possible test issue comment GTK+ 2.14 deprecated setting the page size to a nonzero value. See comment bug 2589 comment in the LSB Bugzilla for more information. quell dup /tests/functions/GtkAdjustment/GtkAdjustment 62 dup /tests/functions/GtkAdjustment/GtkAdjustment 63 dup /tests/functions/GtkAdjustment/GtkAdjustment 69 dup /tests/functions/GtkAdjustment/GtkAdjustment 72 dup /tests/functions/GtkAdjustment/GtkAdjustment 73 dup /tests/functions/GtkAdjustment/GtkAdjustment 74 dup /tests/functions/GtkAdjustment/GtkAdjustment 75 dup /tests/functions/GtkSpinButton/GtkSpinButton 48 end