### Problem Record #1
# LSB 3.0
TESTSUITE libchk < 3.0.99
TEST libstdc++.so.6 {3052,3059}
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0071
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #2
# LSB 3.0
TESTSUITE libstdcpp
TEST /24_iterators/istreambuf_iterator/2.cc 1
SEVERITY failed
MARKER _24_iterators_istreambuf_iterator_2.exe
COMMENT Probably a bug in test suite header files (works with normal header files).
LINK https://www.linuxfoundation.org/lsbprs/pr/0065
LINK https://www.linuxfoundation.org/lsbprs/pr/0095
LINK https://www.linuxfoundation.org/lsbprs/pr/0129
LINK https://www.linuxfoundation.org/lsbprs/pr/0079
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #3
# LSB 3.0
TESTSUITE libstdcpp
TEST /demangle/abi_examples/01.cc 1
| /demangle/abi_examples/02.cc 1
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0080
LINK https://www.linuxfoundation.org/lsbprs/pr/0130
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #4
# LSB 3.0
TESTSUITE core
TEST /tset/PTHR.os/thread/pthread_create/T.pthread_create 4
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0082
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #5
# LSB 3.0
TESTSUITE libstdcpp
TEST /thread/pthread{1..6}.cc 1
SEVERITY unreported
LINK https://www.linuxfoundation.org/lsbprs/pr/0083
RESOLUTION Withdrawn
WAIVE
END
### Problem Record #6
# LSB 3.0
TESTSUITE core
TEST /tset/PTHR.os/thread/pthread_join/T.pthread_join 4
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0102
LINK https://www.linuxfoundation.org/lsbprs/pr/0084
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #7
TESTSUITE vsw4
TEST /tset/CH03/mprsd/mprsd 12
| /tset/CH03/mpsbws/mpsbws {11,12}
| /tset/CH03/mpwdw/mpwdw {12,13}
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, 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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0085
RESOLUTION This problem is because of runnig tests on Xvfb.
WAIVE
END
### Problem Record #8
TESTSUITE tcl
TEST http-4.15
SEVERITY failed
MARKER This test may fail if you use a proxy server
MARKER not a problem with Tcl
OR
MARKER # This test may fail if you use a proxy server. That is to be
MARKER # expected and is 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.
COMMENT It may also fail if use OpenDNS for DNS services
RESOLUTION Check if you use a proxy server.
WAIVE FIP
END
### Problem Record #9
# LSB 3.0
STANDARD LSB >= 3.0
TESTSUITE tcl
TEST httpold-4.12
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0088
COMMENT
COMMENT Update: This issue has returned in LSB-4.0+ on newer distributions. Extending the deficiency/waiver. See: http://bugs.linuxbase.org/show_bug.cgi?id=2861
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #10
# LSB 3.0
# comment See also:
# LINK https://www.linuxfoundation.org/lsbprs/pr/0089
# LINK https://www.linuxfoundation.org/lsbprs/pr/0093
# LINK https://www.linuxfoundation.org/lsbprs/pr/0094
TESTSUITE core
TEST /tset/POSIX.os/procprim/sigconcept/T.sigconcept 41
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.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1065 | Bug #1065
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #11
# LSB 3.0
TESTSUITE libchk < 3.0.99
TEST libstdc++.so.6 {3401,3414}
SEVERITY failed
MARKER _ZNSt15basic_streambuf
MARKER showmanyc
COMMENT Test suite issue, the basic_streambuf::showmanyc() method was reimplemented in basic_streambuf instead of being inherited starting from gcc 4.0.
LINK https://www.linuxfoundation.org/lsbprs/pr/0090
LINK https://www.linuxfoundation.org/lsbprs/pr/0127
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #12
# LSB 3.0
TESTSUITE libstdcpp
TEST /21_strings/char_traits/requirements/wchar_t/1.cc 1
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
LINK http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23550.
COMMENT Also tracked here:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1069 | Bug #1069
LINK https://www.linuxfoundation.org/lsbprs/pr/0091
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #13
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.os/jump/makecontext/T.makecontext {1,3}
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0067
LINK https://www.linuxfoundation.org/lsbprs/pr/0092
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #14
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 8
SEVERITY unreported
COMMENT The 32-bit binary test fails on PPC64 because mprotect() modifies permissions of some of the pages in the specified range even if it later fails; the test does not take this into account.
LINK https://www.linuxfoundation.org/lsbprs/pr/0099
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #15
# LSB 3.0
TESTSUITE core
TEST /tset/PTHR.os/thread/pthread_create/T.pthread_create 11
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0103
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #16
# LSB 3.0
TESTSUITE core
TEST /tset/POSIX.os/procprim/sleep/T.sleep 1
SEVERITY failed
MARKER sleep returned after 26 seconds instead of 25 seconds
LINK https://www.linuxfoundation.org/lsbprs/pr/0096
LINK https://www.linuxfoundation.org/lsbprs/pr/0104
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #17
# LSB 3.0
TESTSUITE core
TEST /tset/ANSI.os/streamio/fwrite 3
SEVERITY unresolved
MARKER fwrite() on non-blocking pipe failed with errno set to EAGAIN
TEST /tset/LSB.os/ioprim/writev_L 13
SEVERITY failed
MARKER writev() returned -1, expected > 0
TEST /tset/POSIX.os/ioprim/write 13
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0105
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #18
# LSB 1.3
TESTSUITE core
TEST /test/LSB.os/mfiles/mmap_P/T.mmap_P 23
SEVERITY failed
MARKER vsrt_wait_for: Timed-out waiting for
MARKER child to exit
COMMENT This is an S390 issue:
LINK https://www.linuxfoundation.org/lsbprs/pr/0108
RESOLUTION Regression
END
### Problem Record #19
# LSB 3.0
TESTSUITE expect
TEST expect-1.3 0
SEVERITY failed
MARKER expect -ex hi {set x 3}
COMMENT See LSB Bugzilla #1116.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1116 | Bug #1116
LINK https://www.linuxfoundation.org/lsbprs/pr/0109
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #20
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.os/mfiles/msync_P/T.msync_P 5
| /tset/ANSI.os/streamio/freopen/T.freopen 17
| /tset/LSB.os/ipc/msgget/T.msgget {2,3}
SEVERITY failed
LINK https://www.linuxfoundation.org/lsbprs/pr/0110
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #21
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.pam/testcases/pam_start/pam_start 3
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 make sense.
COMMENT Entered into LSB Bugzilla as bug #1281.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1281 | Bug #1281
LINK https://www.linuxfoundation.org/lsbprs/pr/0111
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #22
# LSB 3.0
TESTSUITE core
TEST /tset/POSIX.os/procenv/sysconf/T.sysconf 2
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 of the CHILD_MAX constant.
COMMENT Entered into LSB bugzilla as bug #1188.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1188 | Bug #1188
LINK https://www.linuxfoundation.org/lsbprs/pr/0112
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #23
# LSB 3.0
TESTSUITE core
TEST /tset/LI18NUX2K.L1/base/setlocale/T.setlocale {1,2}
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 and fixed for LSB 3.1.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1151 | Bug #1151
LINK https://www.linuxfoundation.org/lsbprs/pr/0113
RESOLUTION Test is too strict
WAIVE
END
### Problem Record #24
# LSB 3.0
TESTSUITE core
TEST /tset/LI18NUX2K.L1/utils/shell/T.shell 8
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.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1151
LINK https://www.linuxfoundation.org/lsbprs/pr/0114
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #25
# LSB 3.0
TESTSUITE libchk < 3.0.99
TEST libpam.so.0 {15..27}
SEVERITY failed
MARKER ((unversioned))
COMMENT The lsblibcheck tool does not expect symbols in libpam to be versioned, so it fails on every such symbol.
COMMENT Reported to LSB bugzilla as bug #1122 and fixed for LSB 3.1.
LINK https://www.linuxfoundation.org/lsbprs/pr/0115
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #26
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.os/ioprim/writev_L/T.writev_L 30
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.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=844 | Bug #844
COMMENT See also LSB bugzilla bug #6.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=6 | Bug #6
LINK https://www.linuxfoundation.org/lsbprs/pr/0116
LINK https://www.linuxfoundation.org/lsbprs/pr/0144
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #27
# LSB 3.0
TESTSUITE core
TEST /tset/LSB.os/ioprim/readv_L/T.readv_L 24
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).
LINK https://www.linuxfoundation.org/lsbprs/pr/0117
LINK https://www.linuxfoundation.org/lsbprs/pr/0143
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #28
# LSB 3.1
TESTSUITE vsw4
TEST /tset/CH02/clsdsply/clsdsply 8
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).
LINK https://www.linuxfoundation.org/lsbprs/pr/0118
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #29
# LSB 3.1
TESTSUITE libstdcpp
TEST /22_locale/locale/cons/12352.cc 1
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0119
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #30
# LSB 3.1
TESTSUITE vsw4
TEST /tset/CH02/vndrrls/{vndrrls,mvndrrls} 1
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:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1339 | Bug #1339
LINK https://www.linuxfoundation.org/lsbprs/pr/0122
LINK https://www.linuxfoundation.org/lsbprs/pr/0123
LINK https://www.linuxfoundation.org/lsbprs/pr/0124
RESOLUTION OK for Xserver 7.XX
WAIVE
END
### Problem Record #31
# LSB 3.1
TESTSUITE libchk < 3.1.99
TEST libX11.so.6 {478..481}
SEVERITY failed
MARKER Did not find Xau
MARKER ((unversioned)) in libX11.so.6
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1330 | Bug #1330
LINK https://www.linuxfoundation.org/lsbprs/pr/0125
LINK https://www.linuxfoundation.org/lsbprs/pr/0126
LINK https://www.linuxfoundation.org/lsbprs/pr/0128
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #32
TESTSUITE core
TEST /tset/LSB.os/genuts/nftw/T.nftw 9
| /tset/LSB.os/mfiles/msync_P/T.msync_P 7
SEVERITY failed
LINK https://www.linuxfoundation.org/lsbprs/pr/0132
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2190
RESOLUTION Known problem
END
### Problem Record #33
TESTSUITE libstdcpp
TEST /22_locale/locale/cons/12438.cc 1
SEVERITY failed
MARKER St9bad_alloc
LINK https://www.linuxfoundation.org/lsbprs/pr/0133
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #34
# LSB 3.1
TESTSUITE core
TEST /tset/PTHR.os/threadattr/pthread_attr_getstacksize/T.pthread_attr_getstacksize {1,2}
SEVERITY failed
COMMENT This failure is caused by VSTH_VALID_STACKSIZE=16384 which is too small for ppc{32,64} in glibc-2.5, due to the decision to go with 64KB pages.
LINK https://www.linuxfoundation.org/lsbprs/pr/0134
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #35
# LSB 3.1
TESTSUITE core
TEST /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r {1,2}
SEVERITY failed
MARKER The system does not support the PTHREAD_SCOPE_PROCESS
LINK https://www.linuxfoundation.org/lsbprs/pr/0137
RESOLUTION Known problem
END
### Problem Record #36
# LSB 3.1
TESTSUITE core
TEST /tset/POSIX.os/procenv/getlogin/T.getlogin 1
SEVERITY failed
MARKER getlogin() returned failed - errno 2 (ENOENT)
LINK https://www.linuxfoundation.org/lsbprs/pr/0138
RESOLUTION Known problem
END
### Problem Record #37
# LSB 3.1
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GdkProperties/GdkProperties 5
SEVERITY failed
MARKER gdk_atom_name: doesnt match the expected string
TEST /tests/functions/GdkProperties/GdkProperties 11
SEVERITY failed
MARKER gdk_atom_intern: not a expected atom
COMMENT The test should not intern a random atom and expect to always get the same number back from the X server.
LINK https://www.linuxfoundation.org/lsbprs/pr/0139
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #38
# LSB 3.1
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkTreeStore/GtkTreeStore 53
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.
LINK https://www.linuxfoundation.org/lsbprs/pr/0140
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #39
# LSB 3.1
TESTSUITE core
TEST /tset/LI18NUX2K.L1/base/getwchar/T.getwchar 3
SEVERITY failed
MARKER path tracing error: path counter 0, expected 1
LINK https://www.linuxfoundation.org/lsbprs/pr/0141
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #40
# LSB 3.1
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkContainer/GtkContainer 65
SEVERITY unreported
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1551 | See also LSB Bugzilla #1551.
LINK https://www.linuxfoundation.org/lsbprs/pr/0142
RESOLUTION Known problem
WAIVE
END
### Problem Record #41
# LSB 3.1
STANDARD LSB
TESTSUITE core < 4.0.6-1 | core >= 4.1.0-1 & < 4.1.3-1
TEST /tset/ANSI.os/genuts/free/T.free 1
SEVERITY failed
MARKER failed to reuse freed memory in next 1000 malloc() calls
COMMENT There is no guarantee of the behavior expected by this test and it has been modified to return UNTESTED (skipped)
LINK https://www.linuxfoundation.org/lsbprs/pr/0145
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1670 | bug 1670
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #42
# LSB 3.1
TESTSUITE libchk < 3.1.99
TEST libstdc++.so.6 4003
SEVERITY failed
MARKER 0x80ee24a078
TEST libstdc++.so.6 4010
SEVERITY failed
MARKER 0x80ee246af8
LINK https://www.linuxfoundation.org/lsbprs/pr/0146
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #43
# LSB 3.1
TESTSUITE core
TEST /tset/LSB.os/genuts/nftw/T.nftw 5
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
LINK https://www.linuxfoundation.org/lsbprs/pr/0147
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #44
# LSB 3.0
TESTSUITE libchk < 3.0.99
TEST libstdc++.so.6 3079
SEVERITY failed
MARKER _ZNKSt9exception4whatEv (expected) doesn't match _ZNKSt10bad_typeid4whatEv (found)
LINK https://www.linuxfoundation.org/lsbprs/pr/0148
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #45
# LSB 3.1
TESTSUITE core
TEST /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 2
SEVERITY failed
MARKER sysconf(_SC_XOPEN_VERSION)
MARKER got 600
LINK https://www.linuxfoundation.org/lsbprs/pr/0149
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #46
# LSB 3.1
TESTSUITE vsw4
TEST /tset/CH05/crtclrmp/crtclrmp 11
SEVERITY failed
MARKER Received error type BadMatch
MARKER Got BadMatch, Expecting BadValue
LINK https://www.linuxfoundation.org/lsbprs/pr/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.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1589 | Bug #1589
COMMENT See also TestPilot 3.1.1:
LINK http://www.linux-foundation.org/en/TestPilot311#lsb-test-vsw4
END
### Problem Record #47
# LSB 3.1
TESTSUITE vsw4
TEST /tset/CH10/crtimg/crtimg 1
SEVERITY unresolved
MARKER XCreateImage() returned NULL
LINK https://www.linuxfoundation.org/lsbprs/pr/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
### Problem Record #48
# Lynx automated test was removed in recent dist-checker.
# expected_severity failed
TESTSUITE lynx
TESTCASE Test comments Case-05
MARKER Case > still in comment --> | 05 |
COMMENT This is a contradiction with HTML standart, not LSB.
RESOLUTION Wrong behaviour of the application
WAIVE
END
### Problem Record #49
TESTSUITE apache
TESTCASE Checking the port 80
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
WAIVE
END
### Problem Record #50
TESTSUITE core
TEST /tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5
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
WAIVE
END
### Problem Record #51
TESTSUITE core
TEST /tset/LSB.os/genuts/ftw_L/T.ftw_L 4
SEVERITY warning
MARKER FTW_SL
COMMENT The linux ftw() function follows symlinks, it does not report them.
RESOLUTION Insignificant
WAIVE
END
### Problem Record #52
TESTSUITE core
TEST /tset/ANSI.os/maths/pow/T.pow 4
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
WAIVE
END
### Problem Record #53
TESTSUITE core
TEST /tset/ANSI.os/streamio/fopen/T.fopen 28
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
WAIVE
END
### Problem Record #54
TESTSUITE core
TEST /tset/POSIX.os/procprim/kill_X/T.kill_X 1
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, which is also logical.
RESOLUTION Insignificant
WAIVE
END
### Problem Record #55
TESTSUITE core
TEST /tset/ANSI.os/streamio/remove_X/T.remove_X 1
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
WAIVE
END
### Problem Record #56
TESTSUITE core
TEST /tset/ANSI.os/streamio/tmpfile/T.tmpfile 2
SEVERITY warning
MARKER mode 0666
MARKER found 0600
COMMENT Not a bug but feature. Linux tmpfile() creates files with access rights 0600 which is more secure than POSIX mandated 0666.
RESOLUTION Feature
WAIVE
END
### Problem Record #57
TESTSUITE core
TEST /tset/POSIX.os/dataform/tar/T.tar 12
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 are correct.
RESOLUTION Correct
WAIVE
END
### Problem Record #58
TESTSUITE core
TEST /tset/POSIX.os/devclass/c_iflag/T.c_iflag 19
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
WAIVE
END
### Problem Record #59
TESTSUITE core
TEST /tset/POSIX.os/devclass/c_lflag/T.c_lflag 6
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
WAIVE
END
### Problem Record #60
TESTSUITE core
TEST /tset/POSIX.os/devclass/tcdrain/T.tcdrain 2
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
WAIVE
END
### Problem Record #61
TESTSUITE core
TEST /tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 8
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
WAIVE
END
### Problem Record #62
TESTSUITE core
TEST /tset/POSIX.os/files/access_X/T.access_X 1
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
WAIVE
END
### Problem Record #63
TESTSUITE core
TEST /tset/POSIX.os/files/rename_X/T.rename_X 1
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
WAIVE
END
### Problem Record #64
TESTSUITE core
TEST /tset/POSIX.os/files/stat_X/T.stat_X 1
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
WAIVE
END
### Problem Record #65
TESTSUITE core
TEST /tset/POSIX.os/files/stat_X/T.stat_X 2
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
WAIVE
END
### Problem Record #66
TESTSUITE core
TEST /tset/POSIX.os/files/unlink_X/T.unlink_X 1
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
WAIVE
END
### Problem Record #67
TESTSUITE core
TEST /tset/POSIX.os/procenv/sysconf/T.sysconf 3
SEVERITY warning
MARKER CLK_TCK not defined
COMMENT Insignificant; CLK_TCK is obsolete anyway.
RESOLUTION Insignificant
WAIVE
END
### Problem Record #68
TESTSUITE core
TEST /tset/LSB.os/procenv/chroot/T.chroot 4
SEVERITY fip
MARKER execve() of ./chroot_t4
MARKER failed - errno 2 (ENOENT)
COMMENT This is correct behavior. The ./chroot_t4 executable cannot be run because the needed shared libraries are not present in the chrooted environment.
RESOLUTION Correct
WAIVE
END
### Problem Record #69
TESTSUITE core
TEST /tset/LSB.fhs/var/spool-lpd/spool-lpd-tc 2
SEVERITY fip
MARKER /var/spool/lpd/lpd.lock:
MARKER file not found
COMMENT Normal when lpd is not installed.
RESOLUTION Normal
WAIVE
END
### Problem Record #70
TESTSUITE core
TEST /tset/LSB.fhs/var/spool-rwho/spool-rwho-tc 1
SEVERITY fip
MARKER /var/spool/rwho:
MARKER directory not found
COMMENT Normal when rwho is not installed.
RESOLUTION Normal
WAIVE
END
### Problem Record #71
TESTSUITE core
TEST /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 17
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
WAIVE
END
### Problem Record #72
TESTSUITE core
TEST /tset/LI18NUX2K.L1/utils/localedef/T.localedef 3
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
WAIVE
END
### Problem Record #73
TESTSUITE core
TEST /tset/LSB.os/genuts/getopt/T.getopt 1
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
WAIVE
END
### Problem Record #74
TESTSUITE libstdcpp
TEST /23_containers/bitset/cons/16020.cc 1
| /23_containers/bitset/invalidation/1.cc 1
| /23_containers/bitset/operations/13838.cc 1
| /backward/11460.cc 1
| /ext/enc_filebuf/{char,wchar_t}/13189.cc 1
| /backward/strstream_members.cc 1
| /23_containers/{deque,vector,list}/invalidation/{1..4}.cc 1
| /23_containers/{multimap,multiset,map,set}/invalidation/{1,2}.cc 1
| /23_containers/map/insert/16813.cc 1
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
WAIVE
END
### Problem Record #75
TESTSUITE xts5
TEST /tset/Xlib3/vndrrls/{Test,MTest} 1
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
WAIVE
END
### Problem Record #76
TESTSUITE xts5
TEST /tset/Xlib3/srvrvndr/{Test,MTest} 1
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
WAIVE
END
### Problem Record #77
TESTSUITE xts5
TEST /tset/Xlib3/srvrvndr/Test 1
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
WAIVE
END
### Problem Record #78
TESTSUITE core
TEST /tset/POSIX.os/ioprim/write/T.write 13
| /tset/LSB.os/ioprim/writev_L/T.writev_L 13
SEVERITY failed
MARKER returned -1, expected > 0
MARKER errno was set to 11 (EAGAIN)
COMMENT This problem was faced earlier. See:
LINK http://osdir.com/ml/linux.debian.ports.ia64/2005-10/msg00004.html
END
### Problem Record #79
TESTSUITE core
TEST /tset/POSIX.os/procprim/exec/T.exec{l,le,lp,v,ve,vp} 30
| /tset/POSIX.os/procprim/fork/T.fork 18
SEVERITY failed
COMMENT See:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1827 | Bug #1827
COMMENT More details at
LINK 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.
RESOLUTION May be a known problem
END
### Problem Record #80
TESTSUITE xts5
TEST /tset/Xlib14/vcnlist/Test 2
SEVERITY failed
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
TEST /tset/Xlib14/vcnlist/Test 3
SEVERITY failed
MARKER REPORT: Returned value does not match expected value for foreground
MARKER REPORT: returned 0
MARKER REPORT: expected 1
MARKER TRACE: background
TEST /tset/Xlib14/vcnlist/Test 4
SEVERITY failed
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:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1365 | Bug #1365 in LSB bugzilla
RESOLUTION Test suite bug
END
### Problem Record #81
TESTSUITE xts5
TEST /tset/Xlib13/allwevnts/Test {20,24}
| /tset/Xt11/tcalbrcrl/Test 1
| /tset/Xt8/tmkgmreqt/Test 4
| /tset/Xt8/tmkrsizrt/Test 4
| /tset/Xlib17/gtdflt/Test {3,5}
SEVERITY failed
COMMENT Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see:
LINK http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
RESOLUTION Appears in multiple distros
END
### Problem Record #82
# LSB 3.1
TESTSUITE libchk < 3.1.99
TEST libX11.so.6 {478,479,480,481}
SEVERITY failed
LINK 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:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1330 | Bug #1330
RESOLUTION The LSB disposition of this failure is not yet determined
END
### Problem Record #83
TESTSUITE core
TEST /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh {5,6,7}
SEVERITY failed
LINK 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:
LINK http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348 | Bug #381348
RESOLUTION These failures occur with cpio 2.6. There is a patch to fix this problem.
END
### Problem Record #84
TESTSUITE core
TEST /tset/PTHR.os/procenv/ttyname_r/T.ttyname_r 2
SEVERITY failed
COMMENT relevant patches to glibc look to be be here:
LINK http://sourceware.org/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/ttyname_r.c.diff?r1=1.17&r2=1.18&cvsroot=glibc
LINK 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:
LINK http://www.linux-foundation.org/en/TestPilot31#lsb-runtime-test_on_Mandriva_2007.0.2C_Cooker
RESOLUTION There are patches to glibc for Mandriva 2007.0, that could help.
END
### Problem Record #85
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 46
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=D0004
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #86
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_hooks/glib_hooks 3
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=D0002
RESOLUTION Known problem
WAIVE
END
### Problem Record #87
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_unicode/glib_unicode 39
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=D0022
RESOLUTION Known problem
WAIVE
END
### Problem Record #88
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_automatic_string_completion/glib_automatic_string_completion 11
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=D0019
RESOLUTION Known problem
WAIVE
END
### Problem Record #89
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_relation/AtkObject_relation 2
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0788
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #90
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_relation/AtkObject_relation {6,7}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0568
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #91
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkHyperlink/AtkHyperlink 19
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0572
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #92
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {82,88}
SEVERITY failed
MARKER g_key_file_new.01
MARKER get comment failed: expected value = "Fourth Comment", returned value = "Fourth Comment
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {83,89}
SEVERITY failed
MARKER g_key_file_new.01
MARKER get comment from above group failed: expected value = "Third Comment", returned value = "Third Comment
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {84,90}
SEVERITY failed
MARKER g_key_file_new.01
MARKER get comment from above first group failed: expected value = "First Comment", returned value = "First Comment
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser 106
SEVERITY failed
MARKER g_key_file_new.01
MARKER set comment = "comment 1" get comment = "comment 1
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser 117
SEVERITY failed
MARKER g_key_file_new.01
MARKER Trying to set comment: set comment = "comment 1" get comment = "comment 1
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {108,119}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=D0025
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #93
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {107,118}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=D0026
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #94
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser 114
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=D0027
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #95
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_unicode/glib_unicode {206,207,208}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0690
RESOLUTION Known problem
WAIVE
END
### Problem Record #96
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkUtils/AtkUtils {5,8}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0579
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #97
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkStateSet/AtkStateSet 24
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0574
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #98
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_signals/AtkObject_signals 16
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0570
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #99
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_properties/AtkObject_properties 4
SEVERITY failed
MARKER Initial value of the role is
MARKER Value of the property should be 0 just after creation of an object.
OR
MARKER Default value of the property should be 0.
COMMENT This failure occurs due to the following problem:
COMMENT "accessible-role" - invalid default value.
COMMENT Detailed description of this problem:
LINK http://linuxtesting.org/results/report?num=S0569
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #100
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkRelationSet/AtkRelationSet 10
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0573
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #101
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_thread_pools/glib_thread_pools 13
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=D0024
RESOLUTION Known problem
WAIVE
END
### Problem Record #102
TESTSUITE desktop-t2c
TEST /gmodule-t2c/tests/gmodule/gmodule 15
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0575
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #103
TESTSUITE desktop-t2c
TEST /gmodule-t2c/tests/gmodule/gmodule 31
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0576
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #104
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_properties/AtkObject_properties 16
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0596
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #105
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_memchunks/glib_memchunks {1..10}
SEVERITY failed
COMMENT Memory chunks are deprecated since glib version 2.10.
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #106
# marker Abnormal child process termination
TESTSUITE desktop-t2c
TEST /fontconfig-t2c/tests/FcPattern/FcPattern 57
SEVERITY unresolved
COMMENT This failure occurs due to the following problem:
COMMENT Crash after FcPatternAdd is called several times.
COMMENT Detailed description of this problem:
LINK http://linuxtesting.org/results/report?num=S0601
RESOLUTION Known problem
WAIVE
END
### Problem Record #107
TESTSUITE desktop-t2c
TEST /fontconfig-t2c/tests/FcFontSet/FcFontSet 11
SEVERITY unresolved
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #108
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_random/glib_random {9..23}
SEVERITY failed
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #109
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_caches/glib_caches 7
SEVERITY failed
MARKER g_cache_value_foreach.01
COMMENT g_cache_value_foreach is deprecated since glib version 2.10.
RESOLUTION Known problem
END
### Problem Record #110
TESTSUITE desktop-t2c
TEST /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 6
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=S0607
RESOLUTION Known problem
WAIVE
END
### Problem Record #111
# comment Detailed description of this problem is available here.
TESTSUITE desktop-t2c
TEST /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 7
SEVERITY failed
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.
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #112
# marker unexpected signal 1 (SIGHUP) received
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging {5..9}
SEVERITY unresolved
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #113
# marker unexpected signal 1 (SIGHUP) received
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 9
SEVERITY failed
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #114
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion {4..7,27..29,32..34,37,43,49,52..55}
SEVERITY failed
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #115
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion {9..12,56}
SEVERITY unresolved
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #116
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion {58,59}
SEVERITY unresolved
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #117
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 58
SEVERITY failed
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #118
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion {32,33}
SEVERITY failed
MARKER The err must be NULL
OR
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.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #119
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 7
SEVERITY failed
MARKER g_main_loop_run.02
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop {17,18}
SEVERITY unresolved
MARKER Unable to initialize
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 57
SEVERITY failed
MARKER g_timeout_source_new
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 87
SEVERITY failed
MARKER g_child_watch_source_new.01
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 74
SEVERITY failed
MARKER g_idle_source_new
TEST /glib-t2c/tests/glib_threads/glib_threads 31
SEVERITY failed
MARKER g_static_rw_lock_reader_lock.01
TEST /glib-t2c/tests/glib_threads/glib_threads 26
SEVERITY failed
MARKER g_static_rec_mutex_lock_full.01
TEST /glib-t2c/tests/glib_thread_pools/glib_thread_pools 11
SEVERITY failed
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.
RESOLUTION FIP
WAIVE
END
### Problem Record #120
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_simple_xml_subset_parser/glib_simple_xml_subset_parser 29
SEVERITY failed
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.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #121
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {36,60,64,76,87,101}
SEVERITY failed
MARKER assertion `group_name != NULL' failed
COMMENT In LSB 3, the specification incorrectly described the behavior of several g_key_file_* interfaces when the group_name parameter is set to NULL. These tests rely on the behavior described in the specification.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1722 | Bug #1722
RESOLUTION Specification error
WAIVE
END
### Problem Record #122
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser {104,110,113,116}
SEVERITY failed
MARKER assertion `g_key_file_is_group_name (group_name)' failed
COMMENT In LSB 3, the specification incorrectly described the behavior of several g_key_file_* interfaces when the group_name parameter is set to NULL. These tests rely on the behavior described in the specification.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1722 | Bug #1722
RESOLUTION Specification error
WAIVE
END
### Problem Record #123
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_unicode/glib_unicode 18
SEVERITY failed
MARKER g_unichar_isdefined: error to determine
COMMENT This test was used to ensure that the function g_unichar_isdefined returns FALSE for an unassigned Unicode code point. The test used code point U+0372 as its unassigned code point, which received an assignment in Unicode 5.1. Newer glib versions correctly recognize this, which cause the test to fail.
RESOLUTION Change in an external standard
WAIVE
END
### Problem Record #124
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_messagelog/glib_messagelog {9,10}
SEVERITY failed
MARKER signal 5
COMMENT This test may fail on development versions of Glib library as well as any other versions compiled with '-DG_ENABLE_DEBUG' option.
COMMENT These versions of Glib behave differently from what is stated in the description of g_log* functions 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #125
STANDARD LSB < 4.1
TESTSUITE cmdchk
TEST xdg-desktop-icon 1
| xdg-desktop-menu 1
| xdg-email 1
| xdg-icon-resource 1
| xdg-mime 1
| xdg-open 1
| xdg-screensaver 1
SEVERITY failed
COMMENT This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
RESOLUTION Trial Use Module
WAIVE
END
### Problem Record #126
TESTSUITE cmdchk
TEST java 1
SEVERITY failed
COMMENT This failure does not affect distribution compliance because Java is a Trial Use Module.
RESOLUTION Trial Use Module
WAIVE
END
### Problem Record #127
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/InlineData/InlineData 17
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0615
RESOLUTION Known problem
END
### Problem Record #128
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/InlineData/InlineData {16..19}
SEVERITY failed
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.
LINK http://www.linuxfoundation.org/en/Downloads | You can download it from this site
RESOLUTION Known problem
WAIVE
END
### Problem Record #129
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/SubPixbuf/SubPixbuf 2
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0640
RESOLUTION Known problem
WAIVE
END
### Problem Record #130
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/Scaling/Scaling {24,49}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0641
RESOLUTION Known problem
WAIVE
END
### Problem Record #131
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/Scaling/Scaling {69,70}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0654
RESOLUTION Known problem
WAIVE
END
### Problem Record #132
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface {8,9,10}
| /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 3
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0642
RESOLUTION Known problem
WAIVE
END
### Problem Record #133
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/Animation/Animation 8
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0626
RESOLUTION Known problem
WAIVE
END
### Problem Record #134
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader {35,42,43}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0659
RESOLUTION Known problem
WAIVE
END
### Problem Record #135
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader {48..53}
| /gdk-pixbuf-t2c/tests/FileLoading/FileLoading {33,35,36,37,43,44,51,52}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0660
RESOLUTION Known problem
END
### Problem Record #136
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 34
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0657
RESOLUTION Known problem
WAIVE
END
### Problem Record #137
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/Utils/Utils {13,14}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0656
RESOLUTION Known problem
WAIVE
END
### Problem Record #138
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 44
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0643
RESOLUTION Known problem
WAIVE
END
### Problem Record #139
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 8
| /gdk-pixbuf-t2c/tests/Structure/Structure 7
SEVERITY failed
COMMENT This failure occurs due to the following problem:
COMMENT Incorrect handling of "tEXt::key" parameters.
COMMENT Detailed description of this problem:
LINK http://linuxtesting.org/results/report?num=S0661
RESOLUTION Known problem
END
### Problem Record #140
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader {20..25}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0663
RESOLUTION Known problem
WAIVE
END
### Problem Record #141
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/FileSaving/FileSaving {29..34}
SEVERITY unresolved
MARKER Couldn't recognize the image file format
COMMENT {noreplace}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 - 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.
COMMENT - 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.
COMMENT - 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.
COMMENT - Execute install_loader.sh (as root). This should install the custom
COMMENT image loader.
COMMENT - Re-run the tests.
COMMENT - Note: On more modern systems, the loader file is /usr/lib{64}/gdk-pixbuf-2.0/2.10.0/loaders.cache. The install_loader.sh script has been adapted to use this when present.
COMMENT - Note: Some systems are going to various multi-arch setups using either gnu triplets or tuples under /usr/lib, such as /usr/lib/i386-linux-gnu. The install_loader.sh script has been adapted to look in these directories when present. See bug 3257 for details.
COMMENT - Note2: Newer versions of gtk/gdk check the mime type of the .chb file before looking up the correct loader. New builds of the test populate the mime database with the correct information for the test file. See the description of bug 2455 for details.
COMMENT
COMMENT
{/noreplace}
RESOLUTION Known problem
END
### Problem Record #142
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader_external/GdkPixbufLoader_external {1,2,3}
SEVERITY uninitiated
MARKER Loader with name "checkboard" is not installed although it is required for this test
COMMENT {noreplace}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 - 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.
COMMENT - 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.
COMMENT - 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.
COMMENT - Execute install_loader.sh (as root). This should install the custom
COMMENT image loader.
COMMENT - Re-run the tests.
COMMENT - Note: On more modern systems, the loader file is /usr/lib{64}/gdk-pixbuf-2.0/2.10.0/loaders.cache. The install_loader.sh script has been adapted to use this when present.
COMMENT - Note: Some systems are going to various multi-arch setups using either gnu triplets or tuples under /usr/lib, such as /usr/lib/i386-linux-gnu. The install_loader.sh script has been adapted to look in these directories when present. See bug 3257 for details.
COMMENT
{/noreplace}
RESOLUTION Known problem
END
### Problem Record #143
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external {1..9}
SEVERITY uninitiated
MARKER Failed to load a custom pixbuf loader required by the tests
COMMENT {noreplace}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 - 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.
COMMENT - 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.
COMMENT - 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.
COMMENT - Execute install_loader.sh (as root). This should install the custom
COMMENT image loader.
COMMENT - Re-run the tests.
COMMENT - Note: On more modern systems, the loader file is /usr/lib{64}/gdk-pixbuf-2.0/2.10.0/loaders.cache. The install_loader.sh script has been adapted to use this when present.
COMMENT - Note: Some systems are going to various multi-arch setups using either gnu triplets or tuples under /usr/lib, such as /usr/lib/i386-linux-gnu. The install_loader.sh script has been adapted to look in these directories when present. See bug 3257 for details.
COMMENT
{/noreplace}
RESOLUTION Known problem
END
### Problem Record #144
# ---- FreeType ----
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/type_1_tables/type_1_tables {12,13}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=V0016
RESOLUTION Known problem
WAIVE
END
### Problem Record #145
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/opentype_validation/opentype_validation {1..27}
SEVERITY uninitiated
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #146
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/base_interface_basic_glyph/base_interface_basic_glyph {19..22}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=V0017
RESOLUTION Known problem
WAIVE
END
### Problem Record #147
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/multiple_masters/multiple_masters {4,5,6}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=V0028
RESOLUTION Known problem
WAIVE
END
### Problem Record #148
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/bitmap_handling/bitmap_handling {20,21}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=V0020
RESOLUTION Known problem
END
### Problem Record #149
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/pfr_fonts/pfr_fonts {5,8,11,14}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=V0031
RESOLUTION Known problem
END
### Problem Record #150
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/pfr_fonts/pfr_fonts {6,7,9,10,12,13}
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=V0030
RESOLUTION Known problem
END
### Problem Record #151
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/x11_font_format/x11_font_format 10
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=S0797
RESOLUTION Known problem
END
### Problem Record #152
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport {103,105,106,108}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0672
RESOLUTION Known problem
WAIVE
END
### Problem Record #153
# Needs interpretation by JTC1. - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/codecvt/codecvt {24,27,29}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0675
RESOLUTION Known problem
WAIVE
END
### Problem Record #154
# Bug accepted, no progress on a fix. - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/time_get/time_get {37..40}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0694
RESOLUTION Known problem
WAIVE
END
### Problem Record #155
# Fixed for gcc 4.4.0 - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_put_do_put5/num_put_do_put5 {9,18}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0677
RESOLUTION Known problem
WAIVE
END
### Problem Record #156
# Fixed for gcc 4.4.0 - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_put_do_put7/num_put_do_put7 {55,58,61,64}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0711
RESOLUTION Known problem
WAIVE
END
### Problem Record #157
# Possibly fixed for gcc 4.4.0. - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 {15,16,21,22,33,34,36,38}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0735
RESOLUTION Known problem
WAIVE
END
### Problem Record #158
# Claimed fixed with other bugfix, for gcc 4.4.0 - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 {28,29,31,32,35,37}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0736
RESOLUTION Known problem
WAIVE
END
### Problem Record #159
# Missing linuxtesting.org report. - JAL -
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 {3..5,8..10,13..15,18..20,23..25,28..30}
| /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 {33..35,38..40,43,44,47,48,52,53,57,58}
| /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 {62,63,67,68,72,73,77,78,81,84}
| /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 {4,7,12,15,20,23,28,31,36,39,44,47}
| /libstdcxx-t2c/tests/num_get_do_get5/num_get_do_get5 {52,55,60,63,68,73}
SEVERITY failed
MARKER String is
MARKER but should be
MARKER val is unchanged
OR
MARKER String is
MARKER but should be
MARKER but it is 0
TEST /libstdcxx-t2c/tests/num_get_do_get4/num_get_do_get4 {81,84}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0691
RESOLUTION Known problem
WAIVE
END
### Problem Record #160
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 {37,40,41,44,45,48,53,56,57,60}
| /libstdcxx-t2c/tests/num_get_do_get1/num_get_do_get1 {61,64,67,72,77,82,87,92,98,102}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {136,138,139,141,142,144,148,150}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {151,153,154,156,162,164,166,167}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {169,171,172,174,176,177,179,181}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {187,189,191,192,194,196,197,199}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {201,202,204,206,211,214,215,218}
| /libstdcxx-t2c/tests/num_get_do_get2/num_get_do_get2 {219,222,227,230,231,234,235,238}
| /libstdcxx-t2c/tests/num_get_do_get6/num_get_do_get6 {18,19,20,24,25,26}
SEVERITY failed
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:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2665 | Bug #2665
RESOLUTION Known problem
WAIVE
END
### Problem Record #161
ARCHITECTURE PPC32,S390
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport {16,17,18,34,35,36,47,48,58,59}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0740
RESOLUTION Known problem (waived)
WAIVE
END
### Problem Record #162
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/LanguageSupport/LanguageSupport {46..50,57..61,71..74,81..84}
SEVERITY unresolved
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, because currently memory usage of memory-subsystem of libstdcxx exceeds this value.
RESOLUTION No problem
WAIVE
END
### Problem Record #163
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/money_put/money_put {41,42}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0738
RESOLUTION Known problem
END
### Problem Record #164
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/money_get/money_get {106,108,110,112}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0738
RESOLUTION Known problem
END
### Problem Record #165
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/money_get/money_get {189..192}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0741
RESOLUTION Known problem
END
### Problem Record #166
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/money_get/money_get {119,128,137,146,205,207}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0780
RESOLUTION Known problem
END
### Problem Record #167
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/locale/locale {53..56}
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0744
RESOLUTION Known problem
END
### Problem Record #168
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/locale/locale 80
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0744
RESOLUTION Known problem
END
### Problem Record #169
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/locale/locale 82
SEVERITY failed
MARKER LC_TIME=ru_RU_test
TEST /libstdcxx-t2c/tests/locale/locale 86
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0744
RESOLUTION Known problem
END
### Problem Record #170
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/locale/locale {83,85,87}
SEVERITY failed
MARKER thousands_sep
MARKER moneypunct
TEST /libstdcxx-t2c/tests/locale/locale 88
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0743
RESOLUTION Known problem
END
### Problem Record #171
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/locale/locale {35,36,71,84}
SEVERITY failed
MARKER monetary
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=S0742
RESOLUTION Known problem
END
### Problem Record #172
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/facets_common/facets_common {396..399}
SEVERITY unresolved
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:
LINK http://linuxtesting.org/results/report?num=S0742
RESOLUTION Known problem
END
### Problem Record #173
TESTSUITE cpp-t2c
TEST /libstdcxx-t2c/tests/basic_istream/basic_istream {314,316,322,324,329,330,361,362}
| /libstdcxx-t2c/tests/operator_shift_left/operator_shift_left {5,6}
SEVERITY failed
COMMENT This failure occurs due to the following problem:
COMMENT This version of libstdcxx implements the resolution of the defect report
LINK http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#136 | 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:
LINK http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39596 | The comments from gcc team
RESOLUTION Known problem
WAIVE
END
### Problem Record #174
TEST /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 {253,256,258,260,263,265,268}
| /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 {270,274,276,279,283}
| /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 {335,338,340,342,345,347,350}
| /libstdcxx-t2c/tests/basic_filebuf_part1/basic_filebuf_part1 {352,356,358,361,365}
SEVERITY failed
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
LINK http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#596 | 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #175
TESTSUITE qt3-azov
TEST /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 6
SEVERITY unresolved
MARKER QGLWidget::grabFrameBuffer(bool)
MARKER unexpected signal 11
TEST /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 21
SEVERITY unresolved
MARKER QGLWidget::renderText(double, double, double, QString const&, QFont const&, int)
MARKER unexpected signal
TEST /Qt3_OpenGL-t2c/tests/QGLWidget/QGLWidget 41
SEVERITY unresolved
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 the LSB Bugzilla for details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2406 | Bug #2406
RESOLUTION Known problem
WAIVE
END
### Problem Record #176
TESTSUITE qt3-azov
TEST /Qt3_OpenGL-t2c/tests/QGLContext/QGLContext *
SEVERITY unresolved
MARKER unexpected signal 11
COMMENT This error appears if the test fails to create an OpenGL context, which can happen when running under Xvfb.
COMMENT See the LSB Bugzilla for details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2406 | Bug #2406
RESOLUTION Known problem
WAIVE
END
### Problem Record #177
TESTSUITE olver
TEST /olver/util/search/tests/insque_spec 028
SEVERITY failed
MARKER Registered bug: bug028(insque)
COMMENT The insque(element, pred) function shall insert the element pointed to by element into a queue immediately after the element pointed to by pred. According to LSB, if the queue is to be used as a linear list, invoking insque(element, NULL), where element is the initial element of the queue, shall initialize the forward and backward pointers of element to null pointers. But this function causes the segmentation fault if the second parameter is NULL.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0028
RESOLUTION Known problem
END
### Problem Record #178
TESTSUITE olver
TEST /olver/process/meta/tests/seteuid_spec 82
SEVERITY failed
MARKER Registered bug: bug82(seteuid)
TEST /olver/process/meta/tests/setuid_spec 102
SEVERITY failed
MARKER Registered bug: bug102(setuid)
TEST /olver/process/meta/tests/setreuid_spec 103
SEVERITY failed
MARKER Registered bug: bug103(setreuid)
COMMENT The LSB specification says nothing that setreuid() function may change the saved set-user-ID value. But actually, if the real user ID is set to or the effective user ID is set to a value not equal to 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
LINK http://linuxtesting.org/results/report?num=S0102
RESOLUTION Known problem
WAIVE
END
### Problem Record #179
TESTSUITE olver
TEST /olver/process/meta/tests/setegid_spec 83
SEVERITY failed
MARKER Registered bug: bug83(setegid)
TEST /olver/process/meta/tests/setgid_spec 104
SEVERITY failed
MARKER Registered bug: bug104(setgid)
TEST /olver/process/meta/tests/setregid_spec 106
SEVERITY failed
MARKER Registered bug: bug106(setregid)
COMMENT The LSB specification says nothing that setregid() function may change the saved set-group-ID value. But actually, if the real group ID is set to or the effective group ID is set to a value not equal to 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
LINK http://linuxtesting.org/results/report?num=S0102
RESOLUTION Known problem
WAIVE
END
### Problem Record #180
TESTSUITE olver
TEST /olver/process/resources/tests/ulimit_spec 167
SEVERITY failed
MARKER Registered bug: bug167(ulimit)
COMMENT The ulimit() function shall control process limits. The process limits that can be controlled 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 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
LINK http://linuxtesting.org/results/report?num=S0167
RESOLUTION Known problem
END
### Problem Record #181
TESTSUITE olver
TEST /olver/system/user/tests/getgrouplist_spec 177
SEVERITY failed
MARKER Registered bug: bug177(getgrouplist)
COMMENT The getgrouplist() function shall fill in the supplied array with the supplementary groups for the specified user. According to LSB, if such user doesn't exist function shall return 0. But it returns 1 on the system under test.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0177
RESOLUTION Known problem
WAIVE
END
### Problem Record #182
TESTSUITE olver
TEST /olver/fs/name/tests/basename_spec 207
SEVERITY failed
MARKER Registered bug: bug207(basename)
COMMENT The basename() function shall take the pathname pointed to by path and return a pointer to the final component of the pathname, deleting any trailing '/' characters. But the input "err////" causes segmentation fault.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0207
RESOLUTION Known problem
END
### Problem Record #183
TESTSUITE olver
TEST /olver/ncurses/move/tests/mvcur_spec 313
SEVERITY failed
MARKER Registered bug: bug313(mvcur)
COMMENT According to LSB, if screen position (newrow, newcol) is not a valid address for the terminal in use, mvcur(int xpos, int ypos) function call to this cursor position should fail (mvcur() is the function from Ncurses library that moves the cursor), but error doesn't occur on inputs (-1000000, -1000000), (10000000, 10000000).
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0313
RESOLUTION Known problem
WAIVE
END
### Problem Record #184
TESTSUITE olver
TEST /olver/ncurses/line/tests/ripoffline_spec 319
SEVERITY failed
MARKER Registered bug: bug319(ripoffline)
COMMENT Function ripoffline() is one from Ncurses library and reserves one screen line for use by the application (for example, for menu). According to LSB, up to five lines can be ripped off for use by the application and calls to ripoffline() above this limit have no effect but report success. But this function on sixth call returns error value -1. This contradicts the standard.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0319
RESOLUTION Known problem
WAIVE
END
### Problem Record #185
TESTSUITE olver
TEST /olver/ncurses/window/tests/refresh_spec 329
SEVERITY failed
MARKER Registered bug: bug329(chgat)
COMMENT Function chgat() is one from Ncurses library and it changes renditions (for example, color, bold, 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 window was refreshed. It still works if it is applied after the text was output to the window but before refresh() call. This behavior is unclear from standard. This bug has been fixed since patch 20060715 for ncurses 5.5.
COMMENT Additional information about this bug may be found at bug-ncurses@gnu.org, archive is
LINK http://www.nabble.com/chgat%28%29-function-does-not-work-correctly-after-refresh%28%29-tf3777004.html
RESOLUTION Known problem
WAIVE
END
### Problem Record #186
TESTSUITE olver
TEST /olver/ncurses/slk/tests/slk_label_spec 342
SEVERITY failed
MARKER Registered bug: bug342(slk_label)
COMMENT Upon successful completion, slk_label(labnum) function from ncurses library returns the requested label with number labnum with leading and trailing blanks stripped.
COMMENT But on the target machine there are outputs with unstripped blanks.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0342
RESOLUTION Known problem
WAIVE
END
### Problem Record #187
TESTSUITE olver
TEST /olver/ncurses/misc/tests/keyname_spec 357
SEVERITY failed
MARKER Registered bug: bug357(keyname)
COMMENT The keyname() function generates a character string whose value describes the key specified as the argument of the functions. The meta-character notation in function keyname() from ncurses library, when running it with meta-character parameter, shall be used only if meta-characters are enabled (according to the LSB standard). But it is used irrespectively of enabling of meta-characters.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0357
RESOLUTION Known problem
WAIVE
END
### Problem Record #188
TESTSUITE olver
TEST /olver/time/time/tests/stime_spec 377
SEVERITY failed
MARKER Registered bug: bug377(stime)
COMMENT The stime() function shall set the system's idea of the time and date to the time referenced by function argument. According to LSB, if this argument is NULL then stime() shall set error code to EINVAL. 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
LINK http://linuxtesting.org/results/report?num=S0377
RESOLUTION Known problem
WAIVE
END
### Problem Record #189
TESTSUITE olver
TEST /olver/time/conversion/tests/asctime_r_spec 379
SEVERITY failed
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, but on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909".
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0379
RESOLUTION Known problem
WAIVE
END
### Problem Record #190
TESTSUITE olver
TEST /olver/time/conversion/tests/asctime_spec 380
SEVERITY failed
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, but on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909".
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0379
RESOLUTION Known problem
WAIVE
END
### Problem Record #191
TESTSUITE olver
TEST /olver/util/float/tests/nexttoward_spec 424
SEVERITY failed
MARKER Registered bug: bug424(nexttoward)
COMMENT The nexttoward(x, y) function shall compute the next representable floating-point value following x in the direction of y.
COMMENT The function gives incorrect result on the input (3fffffff ffffffff, 3fffffffffff ffffffff).
RESOLUTION Known problem
END
### Problem Record #192
STANDARD LSB <= 3.2
TESTSUITE olver
TEST /olver/locale/messages/tests/strerror_spec 443
SEVERITY failed
MARKER Registered bug: bug443(strerror_r)
COMMENT According to LSB, the strerror_r() function shall return a pointer to the string corresponding to errno and shall place the string with description of the error in the buffer, specified as argument of 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 It was fixed in LSB 3.2.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1256 | Bug #1256
RESOLUTION Known problem
WAIVE
END
### Problem Record #193
TESTSUITE olver
TEST /olver/util/assert/tests/warnx_spec 486
SEVERITY failed
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 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 message.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0488
RESOLUTION Known problem
WAIVE
END
### Problem Record #194
TESTSUITE olver
TEST /olver/util/assert/tests/errx_spec 488
SEVERITY failed
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 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 message.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0488
RESOLUTION Known problem
WAIVE
END
### Problem Record #195
TESTSUITE olver
TEST /olver/util/assert/tests/verrx_spec 489
SEVERITY failed
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 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 message.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0488
RESOLUTION Known problem
WAIVE
END
### Problem Record #196
TESTSUITE olver
TEST /olver/math/chyper/tests/cacosh_spec 496
SEVERITY failed
MARKER Registered bug: bug496(cacosh)
COMMENT The cacosh() family of functions shall compute the complex arc hyperbolic cosine of their argument.
COMMENT From mathematical definition of the complex arc hyperbolic cosine there is the 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #197
TESTSUITE olver
TEST /olver/signal/sigset/tests/sigandset_spec 4981
SEVERITY failed
MARKER Registered bug: bug498_1(sigandset)
COMMENT The sigandset() shall combine the two signal sets (specified as arguments) using a logical AND 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 EINVAL error.
COMMENT But it causes crash on the target machine.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0498
RESOLUTION Known problem
WAIVE
END
### Problem Record #198
TESTSUITE olver
TEST /olver/signal/sigset/tests/sigorset_spec 4982
SEVERITY failed
MARKER Registered bug: bug498_2(sigorset)
COMMENT The sigorset() shall combine the two signal sets (specified as arguments) using a logical OR 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 EINVAL error.
COMMENT But it causes crash on the target machine.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0498
RESOLUTION Known problem
WAIVE
END
### Problem Record #199
TESTSUITE olver
TEST /olver/signal/sigset/tests/sigisemptyset_spec 4983
SEVERITY failed
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
LINK http://linuxtesting.org/results/report?num=S0498
RESOLUTION Known problem
WAIVE
END
### Problem Record #200
TESTSUITE olver
TEST /olver/pthread/mutex/tests/pthread_mutex_trylock_spec 5011
SEVERITY failed
MARKER Registered bug: bug501_1(pthread_mutexattr)
COMMENT Function pthread_mutex_trylock() tries to lock a mutex. It shall return EBUSY error code 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
LINK http://linuxtesting.org/results/report?num=S0501
RESOLUTION Known problem
END
### Problem Record #201
TESTSUITE olver
TEST /olver/pthread/mutex/tests/pthread_mutex_trylock_spec 5012
SEVERITY failed
MARKER Registered bug: bug501_2(pthread_mutex_trylock)
COMMENT Function pthread_mutex_trylock() tries to lock a mutex. It shall return EBUSY error code 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
LINK http://linuxtesting.org/results/report?num=S0501
RESOLUTION Known problem
END
### Problem Record #202
TESTSUITE olver
TEST /olver/math/cexp/tests/csqrt_spec 503
SEVERITY failed
MARKER Registered bug: bug503(csqrt)
COMMENT The csqrt() family of functions shall compute the complex square root of z, with a branch cut along the negative real axis. Thus the functions shall return result from right 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 complex conjugate of z" to be failed.
RESOLUTION Known problem
WAIVE
END
### Problem Record #203
TESTSUITE olver
TEST /olver/process/scheduler/tests/sched_setscheduler_spec 504
SEVERITY failed
MARKER Registered bug: bug504(sched_setscheduler)
COMMENT The sched_setscheduler() function shall set the scheduling policy and scheduling parameters of the specified process. According to LSB, upon successful completion, the function shall return the former 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
LINK http://linuxtesting.org/results/report?num=S0504
RESOLUTION Known problem
WAIVE
END
### Problem Record #204
TESTSUITE olver
TEST /olver/util/format/tests/swprintf_spec 505
SEVERITY failed
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 global variable. This contradicts LSB standard for this function.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0505
RESOLUTION Known problem
WAIVE
END
### Problem Record #205
TESTSUITE olver
TEST /olver/util/format/tests/vswprintf_spec 506
SEVERITY failed
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 global variable. This contradicts LSB standard for this function.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0505
RESOLUTION Known problem
WAIVE
END
### Problem Record #206
TESTSUITE olver
TEST /olver/math/rand/tests/initstate_spec 5111
SEVERITY failed
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 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 than 8.
RESOLUTION Known problem
WAIVE
END
### Problem Record #207
TESTSUITE olver
TEST /olver/math/rand/tests/initstate_spec 5112
SEVERITY failed
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 array; otherwise, a null pointer shall be returned.
COMMENT But on the target machine the function returns neither a pointer to the previous state, nor NULL pointer.
RESOLUTION Known problem
WAIVE
END
### Problem Record #208
TESTSUITE olver
TEST /olver/math/hyper/tests/atanh_spec 512
SEVERITY failed
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 set error code to ERANGE.
COMMENT But on the target machine, these functions set error code EDOM instead of ERANGE in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #209
TESTSUITE olver
TEST /olver/math/trig/tests/cos_spec 512
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #210
TESTSUITE olver
TEST /olver/math/real/tests/drem_spec 512
SEVERITY failed
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 be set to EDOM.
COMMENT But on the target machine, the functions set error code EOK instead of EDOM in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #211
TESTSUITE olver
TEST /olver/math/exp/tests/expm1_spec 512
SEVERITY failed
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 and error code shall be set to ERANGE.
COMMENT But on the target machine the functions set error code EOK instead of ERANGE when overflow occurs.
RESOLUTION Known problem
WAIVE
END
### Problem Record #212
TESTSUITE olver
TEST /olver/math/real/tests/fdim_spec 512
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #213
TESTSUITE olver
TEST /olver/math/real/tests/fmod_spec 512
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #214
TESTSUITE olver
TEST /olver/math/gamma/tests/lgamma_spec 512
SEVERITY failed
MARKER Registered bug: bug512(lgamma)
COMMENT According to LSB, lgamma(x) family of functions shall set error code to ERANGE if x argument is negative integer or zero.
COMMENT But on the target machine the functions sets error code EDOM instead of ERANGE on zero argument.
RESOLUTION Known problem
WAIVE
END
### Problem Record #215
TESTSUITE olver
TEST /olver/math/gamma/tests/lgamma_r_spec 512
SEVERITY failed
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 negative integer or zero.
COMMENT But on the target machine the functions sets error code EDOM instead of ERANGE on zero argument.
RESOLUTION Known problem
WAIVE
END
### Problem Record #216
TESTSUITE olver
TEST /olver/math/real/tests/llrint_spec 512
SEVERITY failed
MARKER Registered bug: bug512(llrint)
COMMENT The llrint() family of functions shall round their argument to the nearest integer value, 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 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #217
TESTSUITE olver
TEST /olver/math/real/tests/llround_spec 512
SEVERITY failed
MARKER Registered bug: bug512(llround)
COMMENT The llround() family of functions shall round their argument to the nearest integer value, 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 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #218
TESTSUITE olver
TEST /olver/math/real/tests/lrint_spec 512
SEVERITY failed
MARKER Registered bug: bug512(lrint)
COMMENT The lrint() family of functions shall round their argument to the nearest integer value, 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 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #219
TESTSUITE olver
TEST /olver/math/real/tests/lround_spec 512
SEVERITY failed
MARKER Registered bug: bug512(lround)
COMMENT The lround() family of functions shall round their argument to the nearest integer value, 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 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #220
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 512
SEVERITY failed
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 to ERANGE.
COMMENT But on the target machine, the functions set error code EDOM instead of ERANGE in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #221
TESTSUITE olver
TEST /olver/math/real/tests/remainder_spec 512
SEVERITY failed
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 be set to EDOM.
COMMENT But on the target machine, the functions set error code EOK instead of EDOM in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #222
TESTSUITE olver
TEST /olver/math/real/tests/remquo_spec 512
SEVERITY failed
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 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #223
TESTSUITE olver
TEST /olver/math/trig/tests/sin_spec 512
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #224
TESTSUITE olver
TEST /olver/math/trig/tests/tan_spec 512
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #225
TESTSUITE olver
TEST /olver/math/gamma/tests/tgamma_spec 512
SEVERITY failed
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 code shall be set to EDOM.
COMMENT But on the target machine, the functions set error code EOK instead of EDOM.
RESOLUTION Known problem
WAIVE
END
### Problem Record #226
TESTSUITE olver
TEST /olver/math/bessel/tests/y0_spec 512
SEVERITY failed
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 error shall occur.
COMMENT But on the target machine the function sets error code EDOM instead of ERANGE on an input 0.
RESOLUTION Known problem
WAIVE
END
### Problem Record #227
TESTSUITE olver
TEST /olver/math/exp/tests/log1p_spec 5121
SEVERITY failed
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 and set error code to EDOM.
COMMENT But on the target machine the functions set error code EOK instead of EDOM if the argument is less than -1.
RESOLUTION Known problem
WAIVE
END
### Problem Record #228
TESTSUITE olver
TEST /olver/math/bessel/tests/y1_spec 5121
SEVERITY failed
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 error shall occur.
COMMENT But on the target machine the function sets error code EDOM instead of ERANGE on an input 0.
RESOLUTION Known problem
WAIVE
END
### Problem Record #229
TESTSUITE olver
TEST /olver/math/bessel/tests/yn_spec 5121
SEVERITY failed
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 error shall occur.
COMMENT But on the target machine the function sets error code EDOM instead of ERANGE on an input 0.
RESOLUTION Known problem
WAIVE
END
### Problem Record #230
TESTSUITE olver
TEST /olver/math/exp/tests/log1p_spec 5122
SEVERITY failed
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 and set error code to ERANGE.
COMMENT But on the target machine the functions set error code EOK instead of ERANGE in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #231
TESTSUITE olver
TEST /olver/math/trig/tests/atan_spec 513
SEVERITY failed
MARKER Registered bug: bug513(atan)
COMMENT At the specified point the inaccuracy of the result of atan() family of functions is more then 20 bits from the end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #232
TESTSUITE olver
TEST /olver/math/trig/tests/cos_spec 513
SEVERITY failed
MARKER Registered bug: bug513(cos)
COMMENT At the specified point the inaccuracy of the result of cos() family of functions is more then 20 bits from the end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #233
TESTSUITE olver
TEST /olver/math/bessel/tests/j0_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #234
TESTSUITE olver
TEST /olver/math/bessel/tests/j1_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #235
TESTSUITE olver
TEST /olver/math/bessel/tests/jn_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #236
TESTSUITE olver
TEST /olver/math/trig/tests/sin_spec 513
SEVERITY failed
MARKER Registered bug: bug513(sin)
COMMENT At the specified point the inaccuracy of the result of sin() family of functions is more then 20 bits from the end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #237
TESTSUITE olver
TEST /olver/math/trig/tests/sincos_spec 513
SEVERITY failed
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 20 bits from the end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #238
TESTSUITE olver
TEST /olver/math/trig/tests/tan_spec 513
SEVERITY failed
MARKER Registered bug: bug513(tan)
COMMENT At the specified point the inaccuracy of the result of tan() family of functions is more then 20 bits from the end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #239
TESTSUITE olver
TEST /olver/math/bessel/tests/y0_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #240
TESTSUITE olver
TEST /olver/math/bessel/tests/y1_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #241
TESTSUITE olver
TEST /olver/math/bessel/tests/yn_spec 513
SEVERITY failed
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 end of the floating point number.
RESOLUTION Known problem
WAIVE
END
### Problem Record #242
TESTSUITE olver
TEST /olver/math/chyper/tests/cacosh_spec 516
SEVERITY failed
MARKER Registered bug: bug516(cacosh)
COMMENT The cacosh() family of functions shall compute the complex arc hyperbolic cosine of their argument.
COMMENT According to LSB, the functions shall return result in the range of a half-strip of non-negative 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 plane.
RESOLUTION Known problem
WAIVE
END
### Problem Record #243
TESTSUITE olver
TEST /olver/math/chyper/tests/catanh_spec 516
SEVERITY failed
MARKER Registered bug: bug516(catanh)
COMMENT The catanh() family of functions shall compute the complex arc hyperbolic tangent of their argument.
COMMENT But at the specified point the result is very imprecise (inaccuracy is more then 20 bits from the end of the floating point number).
RESOLUTION Known problem
WAIVE
END
### Problem Record #244
TESTSUITE olver
TEST /olver/math/cexp/tests/cpow_spec 516
SEVERITY failed
MARKER Registered bug: bug516(cpow)
COMMENT The cpow(x, y) family of functions shall compute the complex power function x^y, 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 instead of 0+i*0. This result is logical from definition of mathematical complex power function.
RESOLUTION Known problem
WAIVE
END
### Problem Record #245
TESTSUITE olver
TEST /olver/math/ctrig/tests/ctan_spec 516
SEVERITY failed
MARKER Registered bug: bug516(ctan)
COMMENT The ctan() family of functions shall compute the complex tangent of their argument.
COMMENT At the specified point the functions don't satisfy to the property ctan(z) == -i * ctanh(iz).
RESOLUTION Known problem
WAIVE
END
### Problem Record #246
TESTSUITE olver
TEST /olver/math/chyper/tests/ctanh_spec 516
SEVERITY failed
MARKER Registered bug: bug516(ctanh)
COMMENT The ctanh() family of functions shall compute the complex hyperbolic tangent of their argument.
COMMENT But at the specified point the result is very imprecise (inaccuracy is more then 20 bits from the end of the floating point number).
RESOLUTION Known problem
WAIVE
END
### Problem Record #247
TESTSUITE olver
TEST /olver/math/gamma/tests/gamma_spec 516
SEVERITY failed
MARKER Registered bug: bug516(gamma)
COMMENT According to LSB, gamma(x) family of functions shall return either HUGE_VAL or NaN if x is a non-positive integer.
COMMENT But on the target machine the functions don't return HUGE_VAL or NaN if the argument is not positive.
RESOLUTION Known problem
WAIVE
END
### Problem Record #248
TESTSUITE olver
TEST /olver/math/gamma/tests/lgamma_spec 516
SEVERITY failed
MARKER Registered bug: bug516(lgamma)
COMMENT According to LSB, lgamma(x) family of functions shall return +HUGE_VAL if x is a non-positive integer.
COMMENT But on the target machine the functions don't return +HUGE_VAL if the argument is not positive.
RESOLUTION Known problem
WAIVE
END
### Problem Record #249
TESTSUITE olver
TEST /olver/math/gamma/tests/lgamma_r_spec 516
SEVERITY failed
MARKER Registered bug: bug516(lgamma_r)
COMMENT According to LSB, lgamma_r(x) family of functions shall return +HUGE_VAL if x is a non-positive integer.
COMMENT But on the target machine the functions don't return +HUGE_VAL if the argument is not positive.
RESOLUTION Known problem
WAIVE
END
### Problem Record #250
TESTSUITE olver
TEST /olver/math/gamma/tests/tgamma_spec 516
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #251
TESTSUITE olver
TEST /olver/math/bessel/tests/yn_spec 516
SEVERITY failed
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 according to LSB.
RESOLUTION Known problem
WAIVE
END
### Problem Record #252
TESTSUITE olver
TEST /olver/math/cexp/tests/cexp_spec 5161
SEVERITY failed
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 is NaN+i*Inf. This result is logical from definition of mathematical exponent function.
RESOLUTION Known problem
WAIVE
END
### Problem Record #253
TESTSUITE olver
TEST /olver/math/bessel/tests/jn_spec 5161
SEVERITY failed
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 according to LSB.
RESOLUTION Known problem
WAIVE
END
### Problem Record #254
TESTSUITE olver
TEST /olver/math/cexp/tests/cexp_spec 5162
SEVERITY failed
MARKER Registered bug: bug516_2(cexp)
COMMENT The cexp() family of functions function shall compute the complex exponent of their argument.
COMMENT At the specified point the result of computing the exponent is very imprecise (inaccuracy is more then 20 bits from the end of the floating point number).
RESOLUTION Known problem
WAIVE
END
### Problem Record #255
TESTSUITE olver
TEST /olver/math/bessel/tests/jn_spec 5162
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #256
TESTSUITE olver
TEST /olver/util/float/tests/ilogb_spec 5181
SEVERITY failed
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.
RESOLUTION Known problem
END
### Problem Record #257
TESTSUITE olver
TEST /olver/util/float/tests/logb_spec 5182
SEVERITY failed
MARKER Registered bug: bug518_2(logb)
COMMENT The logb() function shall compute the exponent of the integral part of logarithm 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.
RESOLUTION Known problem
END
### Problem Record #258
TESTSUITE olver
TEST /olver/util/float/tests/nextafter_spec 5183
SEVERITY failed
MARKER Registered bug: bug518_3(nextafter)
COMMENT The nextafter(x, y) family of functions functions shall compute the next representable 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 shall be set.
COMMENT But on the target machine the function sets error code EOK instead of ERANGE.
RESOLUTION Known problem
END
### Problem Record #259
TESTSUITE olver
TEST /olver/util/float/tests/nexttoward_spec 5184
SEVERITY failed
MARKER Registered bug: bug518_4(nexttoward)
COMMENT The nexttoward(x, y) family of functions functions shall compute the next representable 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 shall be set.
COMMENT But on the target machine the function sets error code EOK instead of ERANGE.
RESOLUTION Known problem
END
### Problem Record #260
TESTSUITE olver
TEST /olver/util/float/tests/scalb_spec 5185
SEVERITY failed
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 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 is -Inf and ERANGE when overflow occurs.
COMMENT But the functions sets error code EOK in these cases.
RESOLUTION Known problem
END
### Problem Record #261
TESTSUITE olver
TEST /olver/util/float/tests/scalbln_spec 5186
SEVERITY failed
MARKER Registered bug: bug518_6(scalbln)
COMMENT The scalbln() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing 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 this case.
RESOLUTION Known problem
END
### Problem Record #262
TESTSUITE olver
TEST /olver/util/float/tests/scalbn_spec 5187
SEVERITY failed
MARKER Registered bug: bug518_7(scalbn)
COMMENT The scalbn() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing 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 this case.
RESOLUTION Known problem
END
### Problem Record #263
TESTSUITE olver
TEST /olver/util/format/tests/getdate_spec 5201
SEVERITY failed
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 according to conversion specification.
COMMENT But on the target machine it is detected incorrect processing of conversion patterns %S, %M, %p, %y, %Y, %d, %C.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0520_1
RESOLUTION Known problem
END
### Problem Record #264
TESTSUITE olver
TEST /olver/memory/mman/tests/mmap_spec 522
SEVERITY failed
MARKER Registered bug: bug522(mmap)
COMMENT The mmap() function shall establish a mapping between a process' address space and a file, shared memory object, or typed memory object. The length of the mapping is set up by 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
LINK http://linuxtesting.org/results/report?num=S0522
RESOLUTION Known problem
END
### Problem Record #265
TESTSUITE olver
TEST /olver/time/clock/tests/clock_getres_spec 523
SEVERITY failed
MARKER Registered bug: bug523(clock_getres)
COMMENT The clock_getres() function shall return the resolution of any clock and write this 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
LINK http://linuxtesting.org/results/report?num=S0523
RESOLUTION Known problem
END
### Problem Record #266
TESTSUITE olver
TEST /olver/ncurses/string/tests/scanw_spec 5241
SEVERITY failed
MARKER Registered bug: bug524_1(scanw)
COMMENT According to the standard, upon successful completion, scanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #267
TESTSUITE olver
TEST /olver/ncurses/string/tests/vw_scanw_spec 5242
SEVERITY failed
MARKER Registered bug: bug524_2(vw_scanw)
COMMENT According to the standard, upon successful completion, vw_scanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #268
TESTSUITE olver
TEST /olver/ncurses/string/tests/vwscanw_spec 5243
SEVERITY failed
MARKER Registered bug: bug524_3(vwscanw)
COMMENT According to the standard, upon successful completion, vwscanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #269
TESTSUITE olver
TEST /olver/ncurses/string/tests/scanw_spec 5244
SEVERITY failed
MARKER Registered bug: bug524_4(mvwscanw)
COMMENT According to the standard, upon successful completion, mvwscanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #270
TESTSUITE olver
TEST /olver/ncurses/string/tests/scanw_spec 5245
SEVERITY failed
MARKER Registered bug: bug524_5(mvscanw)
COMMENT According to the standard, upon successful completion, mvscanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #271
TESTSUITE olver
TEST /olver/ncurses/string/tests/scanw_spec 5246
SEVERITY failed
MARKER Registered bug: bug524_6(wscanw)
COMMENT According to the standard, upon successful completion, wscanw() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0524
RESOLUTION Known problem
WAIVE
END
### Problem Record #272
TESTSUITE olver
TEST /olver/system/user/tests/getgrouplist_spec 525
SEVERITY failed
MARKER Registered bug: bug525(getgrouplist)
COMMENT The getgrouplist() function shall fill in the supplied array with the supplementary groups 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 identifiers, getgrouplist() shall return -1, and update the value referenced by this parameter 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
LINK http://linuxtesting.org/results/report?num=S0525
RESOLUTION Known problem
WAIVE
END
### Problem Record #273
TESTSUITE olver
TEST /olver/pthread/attr/tests/pthread_attr_setstack_spec 5261
SEVERITY failed
MARKER Registered bug: bug526_1(pthread_attr_setstack)
COMMENT The function pthread_attr_setstack() is not implemented in libraries on the system of the target machine.
RESOLUTION Known problem
END
### Problem Record #274
TESTSUITE olver
TEST /olver/pthread/pthread/tests/pthread_create_spec 5262
SEVERITY failed
MARKER Registered bug: bug526_2(pthread_attr_setstack)
COMMENT The function pthread_attr_setstack() is not implemented in libraries on the system of the target machine, thus pthread_create() was not successful.
RESOLUTION Known problem
END
### Problem Record #275
TESTSUITE olver
TEST /olver/util/format/tests/getdate_spec 527
SEVERITY failed
MARKER Registered bug: bug527(getdate)
COMMENT The getdate() function shall convert a string representation of a date or time into a broken-down time 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
LINK http://linuxtesting.org/results/report?num=S0520_1
RESOLUTION Known problem
END
### Problem Record #276
TESTSUITE olver
TEST /olver/math/exp/tests/log1p_spec 530
SEVERITY failed
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, 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #277
TESTSUITE olver
TEST /olver/math/chyper/tests/cacosh_spec 532
SEVERITY failed
MARKER Registered bug: bug532(cacosh)
COMMENT The cacosh() family of functions shall compute the complex arc hyperbolic cosine of 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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #278
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 533
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #279
TESTSUITE olver
TEST /olver/util/float/tests/logb_spec 535
SEVERITY failed
MARKER Registered bug: bug535(logb)
COMMENT The logb() family of functions shall compute the exponent of x, which is the integral part 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 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 on denormalized arguments, because it simply returns exponential part of the number which is not correct for this type of arguments.
COMMENT The bug was fixed in libc 2.6.
RESOLUTION Known problem
END
### Problem Record #280
TESTSUITE olver
TEST /olver/util/float/tests/scalbln_spec 536
SEVERITY failed
MARKER Registered bug: bug536(scalbln)
COMMENT The scalbln() family of functions shall compute x * FLT_RADIX at the power of n efficiently, not 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 very big number.
COMMENT Bug was added to linuxtesting.ru as bug number S0536.
RESOLUTION Known problem
END
### Problem Record #281
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 537
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #282
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 538
SEVERITY failed
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 calls of powl() on positive x and negative y.
RESOLUTION Known problem
WAIVE
END
### Problem Record #283
TESTSUITE olver
TEST /olver/math/exp/tests/hypot_spec 543
SEVERITY failed
MARKER Registered bug: bug543(hypotl)
COMMENT The hypotl() function shall compute the value of the square root of x^2+ y^2 without undue overflow or underflow.
COMMENT According to LSB, if both arguments are subnormal and the correct result is subnormal, 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 both subnormal arguments.
RESOLUTION Known problem
WAIVE
END
### Problem Record #284
TESTSUITE olver
TEST /olver/time/timer/tests/timer_getoverrun_spec 5441
SEVERITY failed
MARKER Registered bug: bug544_1(timer_getoverrun)
COMMENT When a timer expiration signal is delivered to or accepted by a process, if the implementation supports the Realtime Signals Extension, the timer_getoverrun() function shall return the timer 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
LINK http://linuxtesting.org/results/report?num=S0544
RESOLUTION Known problem
WAIVE
END
### Problem Record #285
TESTSUITE olver
TEST /olver/time/timer/tests/timer_delete_spec 5442
SEVERITY failed
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
LINK http://linuxtesting.org/results/report?num=S0544
RESOLUTION Known problem
WAIVE
END
### Problem Record #286
TESTSUITE olver
TEST /olver/time/timer/tests/timer_gettime_spec 5443
SEVERITY failed
MARKER Registered bug: bug544_3(timer_gettime)
COMMENT The timer_gettime() function shall store the amount of time until the specified timer, 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
LINK http://linuxtesting.org/results/report?num=S0544
RESOLUTION Known problem
WAIVE
END
### Problem Record #287
TESTSUITE olver
TEST /olver/process/fenv/tests/fesetround_spec 545
SEVERITY failed
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 requested rounding direction was established. If the argument is not equal to the value of a 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
LINK http://linuxtesting.org/results/report?num=S0545
RESOLUTION Known problem
END
### Problem Record #288
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 548
SEVERITY failed
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 an no error shall occur.
COMMENT But on the target machine pow() returns EDOM error in this case.
RESOLUTION Known problem
WAIVE
END
### Problem Record #289
TESTSUITE olver
TEST /olver/math/exp/tests/pow_spec 549
SEVERITY failed
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, 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 is still representable.
COMMENT Bug was added to linuxtesting.ru as bug number S0549.
RESOLUTION Known problem
WAIVE
END
### Problem Record #290
TESTSUITE olver
TEST /olver/util/float/tests/ilogb_spec 550
SEVERITY failed
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 exponent of +0 or -0.
COMMENT But on the target machine ilogb() sets error code ERANGE in this case.
RESOLUTION Known problem
END
### Problem Record #291
TESTSUITE olver
TEST /olver/util/float/tests/logb_spec 551
SEVERITY failed
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 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.
RESOLUTION Known problem
END
### Problem Record #292
TESTSUITE olver
TEST /olver/util/float/tests/__signbit_spec 552
SEVERITY failed
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 sign of its argument value is negative.
COMMENT But on the target machine, the function __signbit() returns 0 on -NaN while the correct result shall be non-zero.
RESOLUTION Known problem
END
### Problem Record #293
TESTSUITE olver
TEST /olver/util/float/tests/__signbit_spec 552
SEVERITY failed
MARKER Registered bug: bug552(__signbitf)
COMMENT The __signbit() function shall determine whether the sign of its argument value is negative. NaNs, zeros, 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 argument value is negative.
COMMENT But on the target machine it returns 0 on -NaN while the correct result shall be non-zero.
RESOLUTION Known problem
END
### Problem Record #294
TESTSUITE olver
TEST /olver/math/gamma/tests/tgamma_spec 553
SEVERITY failed
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 be set to ERANGE.
COMMENT But on the target machine, the functions set error code EDOM instead of ERANGE.
RESOLUTION Known problem
WAIVE
END
### Problem Record #295
TESTSUITE olver
TEST /olver/time/timer/tests/timer_create_spec 558
SEVERITY failed
MARKER Registered bug: bug558(timer_create)
COMMENT The timer_create() function shall create a per-process timer using the specified clock, clock_id, as the timing base.
COMMENT But call to timer_create with clock_id received from clock_getcpuclockid() cause 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
LINK http://linuxtesting.org/results/report?num=S0558
RESOLUTION Known problem
END
### Problem Record #296
TESTSUITE olver
TEST /olver/util/format/tests/wcsftime_spec 561
| /olver/other/other/tests/others 561
SEVERITY failed
MARKER Registered bug: bug561(wcsftime)
COMMENT %z Replaced by the offset from UTC in the ISO 8601:2000 standard format, 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 when tm_isdst is set to a positive number - no daylight savings time offset is used.
COMMENT Upstream has said that they interpret the spec to mean that the incoming values already have the DST value applied, which would make the test incorrect. See the LSB bug for more information.
COMMENT Additional information about this bug may be found at:
LINK http://linuxtesting.org/results/report?num=S0561 | LinuxTesting,
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3774 | the LSB bug
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #297
TESTSUITE olver
TEST /olver/time/clock/tests/clock_getres_spec 6021
SEVERITY failed
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 executed with correct clock (recieved as the result of clock_getcpuclockid() function) as the argument.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0601 | LinuxTesting (problem with link)
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3563 | LSB bug 3563
RESOLUTION Known problem
END
### Problem Record #298
TESTSUITE olver
TEST /olver/time/clock/tests/clock_gettime_spec 6022
SEVERITY failed
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 executed with correct clock (recieved as the result of clock_getcpuclockid() function) as the argument.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0601
RESOLUTION Known problem
END
### Problem Record #299
TESTSUITE olver
TEST /olver/socket/socket/tests/sockatmark_spec 610
SEVERITY failed
MARKER Registered bug: bug610(sockatmark)
COMMENT The sockatmark() function shall determine whether the socket specified by the descriptor is at the out-of-band data mark.
COMMENT But on the target machine this function returns error EFAULT when it is executed with correct socket as the argument.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0610
RESOLUTION Known problem
END
### Problem Record #300
TESTSUITE olver
TEST /olver/process/meta/tests/setgid_spec 6111
SEVERITY failed
MARKER Registered bug: bug611_1(setgid)
COMMENT If the process has appropriate privileges, setgid() shall set the real group ID, effective group ID, and 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 executed with parameter less than zero.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0611
RESOLUTION Known problem
END
### Problem Record #301
TESTSUITE olver
TEST /olver/process/meta/tests/setuid_spec 6112
SEVERITY failed
MARKER Registered bug: bug611_2(setuid)
COMMENT If the process has appropriate privileges, setuid() shall set the real user ID, effective user ID, and 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 executed with parameter less than zero.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0611
RESOLUTION Known problem
END
### Problem Record #302
TESTSUITE olver
TEST /olver/math/exp/tests/exp2_spec 616
SEVERITY failed
MARKER Registered bug: bug616(exp2l)
COMMENT The function exp2l() is not implemented in libraries on the system of the target machine.
RESOLUTION Known problem
WAIVE
END
### Problem Record #303
TESTSUITE olver
TEST /olver/fs/dir/tests/readdir_spec 617
SEVERITY failed
MARKER Registered bug: bug617(readdir_spec)
COMMENT The readdir() function shall return a pointer to a structure representing the directory entry at the current position in the directory.
COMMENT Each file in the filesystem should have unique file serial number. But on the target machine readdir() returns the same serial number for different file.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0617
RESOLUTION Known problem
END
### Problem Record #304
TESTSUITE olver
TEST /olver/math/exp/tests/hypot_spec 618
SEVERITY failed
MARKER Registered bug: bug618(hypotf)
COMMENT The hypotf() function shall compute the value of the square root of x^2+ y^2 without undue overflow or underflow.
COMMENT According to LSB, if both arguments are subnormal and the correct result is subnormal, 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 both subnormal arguments.
RESOLUTION Known problem
WAIVE
END
### Problem Record #305
TESTSUITE olver
TEST /olver/math/real/tests/llround_spec 619
SEVERITY failed
MARKER Registered bug: bug619(llroundf)
COMMENT The llroundf() function shall round their argument to the nearest integer value, 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 +-1.9999998807907104e+00 (i.e. nearest to +-2 float numbers).
RESOLUTION Known problem
WAIVE
END
### Problem Record #306
TESTSUITE olver
TEST /olver/io/multiplex/tests/poll_spec 649
SEVERITY failed
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
LINK http://linuxtesting.org/results/report?num=S0649
RESOLUTION Known problem
END
### Problem Record #307
TESTSUITE olver
TEST /olver/io/multiplex/tests/select_spec 649
SEVERITY failed
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
LINK http://linuxtesting.org/results/report?num=S0649
RESOLUTION Known problem
END
### Problem Record #308
TESTSUITE olver
TEST /olver/math/real/tests/fdim_spec 664
SEVERITY failed
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.
RESOLUTION Known problem
WAIVE
END
### Problem Record #309
TESTSUITE olver
TEST /olver/signal/sigstr/tests/psignal_spec 684
SEVERITY failed
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"), the message shall consist of the string s, a colon, a space, and a string describing the signal number sig; otherwise psignal() shall display only a message 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
LINK http://linuxtesting.org/results/report?num=S0684
RESOLUTION Known problem
WAIVE
END
### Problem Record #310
TESTSUITE olver
TEST /olver/signal/sigstr/tests/strsignal_spec 685
SEVERITY failed
MARKER Registered bug: bug685(strsignal)
COMMENT If sig is not a valid signal number, strsignal shall return either a pointer 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 to the appropriate description string. Otherwise, strsignal() shall return 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
LINK http://linuxtesting.org/results/report?num=S0685
RESOLUTION Known problem
WAIVE
END
### Problem Record #311
TESTSUITE olver
TEST /olver/ncurses/terminal/tests/tgetnum_spec 686
SEVERITY failed
MARKER Registered bug: bug686(tgetnum)
COMMENT According to the standard, upon successful completion, tgetnum() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0686
RESOLUTION Known problem
WAIVE
END
### Problem Record #312
TESTSUITE olver
TEST /olver/ncurses/terminal/tests/tgetflag_spec 687
SEVERITY failed
MARKER Registered bug: bug687(tgetflag)
COMMENT According to the standard, upon successful completion, tgetflag() function from Ncurses 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
LINK http://linuxtesting.org/results/report?num=S0687
RESOLUTION Known problem
WAIVE
END
### Problem Record #313
TESTSUITE olver
TEST /olver/util/conversion/tests/__strtod_internal_spec 7091
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #314
TESTSUITE olver
TEST /olver/util/conversion/tests/__wcstod_internal_spec 7101
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #315
TESTSUITE olver
TEST /olver/util/conversion/tests/__strtod_internal_spec 7092
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #316
TESTSUITE olver
TEST /olver/util/conversion/tests/__wcstod_internal_spec 7102
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #317
TESTSUITE olver
TEST /olver/util/conversion/tests/__strtod_internal_spec 7093
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #318
TESTSUITE olver
TEST /olver/util/conversion/tests/__wcstod_internal_spec 7103
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #319
TESTSUITE olver
TEST /olver/util/conversion/tests/strtod_spec 7094
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #320
TESTSUITE olver
TEST /olver/util/conversion/tests/wcstod_spec 7104
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #321
TESTSUITE olver
TEST /olver/util/conversion/tests/strtod_spec 7095
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #322
TESTSUITE olver
TEST /olver/util/conversion/tests/wcstod_spec 7105
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #323
TESTSUITE olver
TEST /olver/util/conversion/tests/strtod_spec 7096
SEVERITY failed
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 these 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, including the terminating null byte of the input string. If input string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0709
RESOLUTION Known problem
END
### Problem Record #324
TESTSUITE olver
TEST /olver/util/conversion/tests/wcstod_spec 7106
SEVERITY failed
MARKER Registered bug: bug710_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 these 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 the terminating null byte of the input wide string. If input wide string looks like NAN(n-char-sequenceopt) * endptr must point to symbol after closing bracket. But * endptr point to closing bracket.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0710
RESOLUTION Known problem
END
### Problem Record #325
TESTSUITE olver
TEST /olver/util/search/tests/hsearch_spec 790
SEVERITY failed
MARKER Registered bug: bug790(hsearch)
COMMENT The hsearch(item, action) function shall return a pointer into a hash table created by hcreate(nel) function 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 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
LINK http://linuxtesting.org/results/report?num=S0791
LINK http://linuxtesting.org/results/report?num=S0790
RESOLUTION Upstream bug
END
### Problem Record #326
TESTSUITE olver
TEST /olver/util/search/tests/hsearch_spec 792
SEVERITY failed
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 and hence returns NULL pointer while trying to obtain the value desired.
COMMENT Additional information about these bugs may be found at
LINK http://linuxtesting.org/results/report?num=S0791
LINK http://linuxtesting.org/results/report?num=S0790
RESOLUTION Upstream bug
END
### Problem Record #327
TESTSUITE olver
TEST /olver/util/search/tests/hsearch_spec 793
SEVERITY failed
MARKER Registered bug: bug793(hsearch)
COMMENT The hsearch(item, action) function shall return a pointer into a hash table created by hcreate(nel) function 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
LINK http://linuxtesting.org/results/report?num=S0791
LINK http://linuxtesting.org/results/report?num=S0790
RESOLUTION Upstream bug
END
### Problem Record #328
TESTSUITE olver
TEST /olver/process/resources/tests/ulimit_spec 794
SEVERITY failed
MARKER Registered bug: bug794(ulimit)
COMMENT It is a test suite deficiency that will be fixed soon.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #329
TESTSUITE olver < 4.1.3
TEST /olver/system/sysconf/tests/sysconf_spec 807
| /olver/other/other/tests/others 807
SEVERITY failed
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, _POSIX2_VERSION, _POSIX_ADVISORY_INFO, _POSIX_ASYNCHRONOUS_IO, _POSIX_BARRIERS, _POSIX_CLOCK_SELECTION, _POSIX_FSYNC, _POSIX_IPV6, _POSIX_MAPPED_FILES, _POSIX_MEMLOCK, _POSIX_MEMLOCK_RANGE, _POSIX_MEMORY_PROTECTION, _POSIX_MESSAGE_PASSING, _POSIX_PRIORITIZED_IO, _POSIX_PRIORITY_SCHEDULING, _POSIX_RAW_SOCKETS, _POSIX_READER_WRITER_LOCKS, _POSIX_REALTIME_SIGNALS, _POSIX_SEMAPHORES, _POSIX_SHARED_MEMORY_OBJECTS, _POSIX_SPAWN, _POSIX_SPIN_LOCKS, _POSIX_SYNCHRONIZED_IO, _POSIX_THREAD_ATTR_STACKADDR, _POSIX_THREAD_ATTR_STACKSIZE, _POSIX_THREAD_PRIO_INHERIT, _POSIX_THREAD_PRIO_PROTECT, _POSIX_THREAD_PRIORITY_SCHEDULING, _POSIX_THREAD_PROCESS_SHARED, _POSIX_THREADS, _POSIX_THREAD_SAFE_FUNCTIONS, _POSIX_TIMEOUTS, _POSIX_TIMERS, _POSIX_VERSION is defined in , it shall be defined to be -1, 0, or 200112L. The value of this symbol reported by sysconf() shall either be -1 or 200112L. But glibc since 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
LINK http://linuxtesting.org/results/report?num=S0807
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2699 | bug 2699
RESOLUTION Specification deficiency
WAIVE
END
### Problem Record #330
TESTSUITE core
TEST /tset/LSB.fhs/var/lib-hwclock/lib-hwclock-tc 1
SEVERITY failed
MARKER Found /etc/adjtime, should be in /var/lib/hwclock
COMMENT The FHS mandated that this file move out of /etc, but not everyone has caught up to this requirement, so it is temporary waived for now.
RESOLUTION Still in transition
WAIVE
END
### Problem Record #331
TESTSUITE printing
TEST /fhs/share-ppd/share-ppd 1
SEVERITY failed
MARKER /usr/share/ppd: directory not found
COMMENT Not all distributions have moved to supporting the standard PPD directory yet.
RESOLUTION Still in transition
WAIVE
END
### Problem Record #332
TESTSUITE core
TEST /tset/LI18NUX2K.L1/utils/diff/T.diff {2,3}
| /tset/LI18NUX2K.L1/utils/fold/T.fold {1,2,3}
| /tset/LI18NUX2K.L1/utils/join/T.join {3,4}
| /tset/LI18NUX2K.L1/utils/pr/T.pr {1,3..6}
| /tset/LI18NUX2K.L1/utils/sort/T.sort {8..16,24..32,40..48}
| /tset/LI18NUX2K.L1/utils/unexpand/T.unexpand 1
| /tset/LI18NUX2K.L1/utils/uniq/T.uniq {2,3}
| /tset/LI18NUX2K.L1/utils/find/T.find 2
SEVERITY failed
COMMENT Some utilities are not yet able to handle multibyte characters.
COMMENT The patches to fix this are not yet acceptable to some upstream maintainers. While this situation is being resolved, the failure of those utilities is not considered a violation of the spec.
RESOLUTION Waived
WAIVE
END
### Problem Record #333
TESTSUITE core
TEST /tset/LI18NUX2K.L1/base/strptime/T.strptime 32
SEVERITY failed
COMMENT This test fails on newer distributions with certain versions of glibc.
COMMENT See the LSB Bugzilla for more details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2040 | Bug #2040
RESOLUTION Unknown
WAIVE
END
### Problem Record #334
TESTSUITE core
TEST /tset/LI18NUX2K.L1/base/__wcstold_internal/T.__wcstold_internal 8
| /tset/LI18NUX2K.L1/base/wcstold/T.wcstold 8
SEVERITY failed
MARKER The return value is not correct.
MARKER The errno is not correct.
COMMENT This error is seen on the ppc32/64, s390(x) architectures.
COMMENT For more information, see the LSB Bugzilla:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1771 | Bug #1771
RESOLUTION Unknown
WAIVE
END
### Problem Record #335
TESTSUITE printing
TEST /testfoomaticrip/testfoomaticrip 13
SEVERITY failed
COMMENT This test is too sensitive to specific conditions in the various distributions.
RESOLUTION Unknown
WAIVE
END
### Problem Record #336
TESTSUITE core
TEST /tset/POSIX.os/procprim/exec/T.exec{l,le,lp,v,ve,vp} 15
SEVERITY failed
COMMENT In newer kernel/glibc combinations, sysconf(_SC_ARG_MAX) is dynamic, and has a per-argument limit as well as a total buffer limit. The test does not take this into account.
COMMENT For more information see
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2288 | Bug #2288
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #337
TESTSUITE core
TEST /tset/POSIX.os/procprim/exec/T.exec{l,le,lp,v,ve,vp} 16
SEVERITY unresolved
COMMENT This is a side effect of the failure of a previous test.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #338
TESTSUITE core
TEST /tset/LSB.fhs/usr/x11r6/x11r6-tc 1
SEVERITY failed
MARKER /usr/X11R6: directory not found
COMMENT Contrary to the sense of this test, the /usr/X11R6 directory is not required to be present by the FHS.
RESOLUTION Test mistake
WAIVE
END
### Problem Record #339
TESTSUITE core
TEST /tset/LI18NUX2K.L1/base/__cxa_atexit/T.__cxa_atexit 2
SEVERITY unreported
MARKER libm.so: cannot open shared object file: No such file or directory
COMMENT The libm.so file is not required by the LSB.
COMMENT See the LSB bug tracker for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2545 | Bug #2545
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #340
TESTSUITE core
TEST /tset/ANSI.os/time/strftime/T.strftime 9
SEVERITY failed
MARKER expected "ABC"
COMMENT Recent glibc versions have been optimizing how time conversion functions call tzset(). This may be a missed corner case.
COMMENT See the LSB bug tracker for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2577 | Bug #2577
RESOLUTION Upstream issue
WAIVE
END
### Problem Record #341
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkTreeSelection/GtkTreeSelection {45..69,170..175}
SEVERITY failed
COMMENT This is caused by a vendor patch commonly seen on newer Debian-based systems.
COMMENT For more information see:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2170 | Bug #2170
RESOLUTION Unknown
WAIVE
END
### Problem Record #342
TEST /libstdcxx-t2c/tests/codecvt/codecvt {28,29,30,31,34,35}
| /libstdcxx-t2c/tests/ctype/ctype {10,12,14,16,18,19,20,29,30,31,33,37,38,39,42,43}
| /libstdcxx-t2c/tests/ctype/ctype {50..55,58,59,61,62,64,65,73..79,82,83,84,87,88}
| /libstdcxx-t2c/tests/ctype/ctype {91,92,95,96,99,100,109..120,123..125,134..145,148..150}
| /libstdcxx-t2c/tests/time_get/time_get {4,6,8,10,11,12,25..28,35..40}
| /libstdcxx-t2c/tests/collate/collate {13..18,27..43,50..58,65..73}
| /libstdcxx-t2c/tests/time_put/time_put {38..74,112..148,156..162,170..176,190..202}
| /libstdcxx-t2c/tests/time_put/time_put {216..228,233..236,241..244,247,248,251,252}
SEVERITY unresolved
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 again.
COMMENT This can be done by running the "/opt/lsb/test/cpp-t2c/locales/install_locale.sh" script as root.
COMMENT For more information see:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2506 | Bug #2506
RESOLUTION Test setup problem
END
### Problem Record #343
STANDARD LSB
TESTSUITE core
TEST /tset/lsb_release/testcases/lsb_release/lsb_release-tc 2
SEVERITY failed
COMMENT The lsb_release command is not reporting that the distribution attempts to be compliant with the version of the LSB being tested. Update the lsb_release command (and/or the supporting files) to report this LSB version.
RESOLUTION Distribution problem
END
### Problem Record #344
TEST /tset/initd/misc/install/general-tc 1
SEVERITY failed
COMMENT There is disagreement about the interpretation of the LSB init script specification; specifically, whether certain fields may be optional. See:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2479 | Bug #2479
RESOLUTION Specification ambiguity
WAIVE
END
### Problem Record #345
#TESTSUITE core
#TEST /tset/POSIX.os/ioprim/select/T.select 6
# SEVERITY failed
# MARKER errno is expected to be 22[EINVAL]
#COMMENT This is caused by a bug in the test.
#COMMENT Please see the LSB bug tracker for more information:
#LINK http://bugs.linuxbase.org/show_bug.cgi?id=2528 | Bug #2528
#RESOLUTION Test suite deficiency
#WAIVE
#END
### Problem Record #346
#TESTSUITE core
#TEST /tset/LSB.os/network/accept/T.accept 7
# SEVERITY failed
# MARKER errno is set to 14
#COMMENT This is caused by a bug in the test.
#COMMENT Please see the LSB bug tracker for more information:
#LINK http://bugs.linuxbase.org/show_bug.cgi?id=2529 | Bug #2529
#RESOLUTION Test suite deficiency
#WAIVE
#END
### Problem Record #347
TESTSUITE core
TEST /tset/LSB.os/network/setsockopt/T.setsockopt 3
SEVERITY failed
MARKER setsockopt() returned 0, expected to return -1
COMMENT This is caused by a bug in the test.
COMMENT Please see the LSB bug tracker for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2530 | Bug #2530
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #348
TESTSUITE core
TEST /tset/LSB.os/network/connect/T.connect 2
SEVERITY failed
COMMENT This test will often report failures depending on what network a host may be on, or whether Internet access is available.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2332 | Bug #2332
RESOLUTION Inappropriate reliance on network
WAIVE
END
### Problem Record #349
TESTSUITE core
TEST /tset/LSB.fhs/usr/share-misc/share-misc-tc 3
SEVERITY failed
MARKER /usr/share/misc/magic: file not found
COMMENT Since this is an optional component, it should not fail.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #350
TEST /tset/profile.d/testcases/profile.d/profile.d-tc 2
SEVERITY failed
MARKER Expected $LSB_CORE_TEST_VAL to be set to 'ABC123', got ''
COMMENT This problem occurs when scripts in /etc/profile.d are not read by the shell at startup.
RESOLUTION Known problem
WAIVE
END
### Problem Record #351
TESTSUITE core
TEST /tset/POSIX.os/ioprim/pipe/T.pipe 4
SEVERITY failed
MARKER deletion reason: unable to find an unused file descriptor
COMMENT The method used to determine the lowest-number unused file descriptor does not seem to work on newer distributions.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2627 | Bug #2627
RESOLUTION Upstream kernel issue
WAIVE
END
### Problem Record #352
TESTSUITE printing
TEST /testfoomaticrip/testfoomaticrip {3,11}
SEVERITY failed
COMMENT Some snapshots of foomatic 3.x contained a regression that has produced incorrect behavior. Upstream has fixed the bug, and recommends that all distributions failing this test upgrade to a version of foomatic 3.x newer than 2008-11-19.
COMMENT More information is available on the LSB bug tracker:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2418 | Bug #2418
RESOLUTION Upstream bug
END
### Problem Record #353
STANDARD LSB < 4.0
TESTSUITE printing
TEST /testgs/testgs 5
SEVERITY failed
MARKER /usr/bin/gs returned 1 using the ijs driver, expected 0
COMMENT The test requires that hpijs be installed, which is not specified. See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2553 | Bug #2553
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #354
TESTSUITE desktop-t2c
TEST /pango-t2c/tests/pango_matrix/pango_matrix 1
SEVERITY failed
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:
LINK http://linuxtesting.org/results/report?num=S0771
RESOLUTION Known problem
END
### Problem Record #355
TESTSUITE desktop-t2c
TEST /pango-t2c/tests/pango_language/pango_language {4,9,10}
SEVERITY failed
MARKER This stripping was no good
COMMENT This failure occurs due to the following problem:
COMMENT Probably pango version is too old.
RESOLUTION Known problem
END
### Problem Record #356
TESTSUITE libstdcpp
TEST -r /22_locale/.*/(char|wchar_t)/wrapped_locale\.cc 1
| /27_io/basic_filebuf/imbue/wchar_t/12868.cc 1
| /27_io/basic_streambuf/imbue/{char,wchar_t}/13007-1.cc 1
SEVERITY failed
MARKER locale name not valid
COMMENT Some of the locales used for this test are missing.
COMMENT Please see the gcc manual for the list of locales used by the test suites, and install them on the test machine:
LINK http://gcc.gnu.org/onlinedocs/libstdc++/manual/build.html#build.prereq | gcc manual
RESOLUTION Missing locales
END
### Problem Record #357
TESTSUITE libstdcpp
TEST /22_locale/money_put/put/char/9780-3.cc 1
SEVERITY failed
COMMENT This is caused by a test that is overly sensitive to the output text. See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2596 | Bug #2596
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #358
TESTSUITE libstdcpp
TEST /22_locale/time_get/get_date/wchar_t/4.cc 1
SEVERITY failed
COMMENT This is thought to be related to an upstream bug in the C++ library.
COMMENT See the linuxtesting.org report for details:
LINK http://linuxtesting.org/results/report?num=S0735
RESOLUTION Known problem
WAIVE
END
### Problem Record #359
TESTSUITE libstdcpp
TEST /22_locale/money_get/get/{char,wchar_t}/{1,wrapped_env,wrapped_locale}.cc 1
| /22_locale/money_put/put/{char,wchar_t}/{1,3,wrapped_env,wrapped_locale}.cc 1
SEVERITY failed
COMMENT Some versions of Ubuntu have a bug in their locale databases where the local money symbol (the Euro symbol) is not displayed for at least the German locale using the ISO 8859-15 character set (the text letters "EUR" appear instead). The C++ locale support code in question is actually working properly, in that it reports the value that is stored in the database. As the LSB does not specify the contents of the locale database, this bug is not an issue with the LSB. It should not affect Ubuntu-based distributions, as they have moved exclusively to UTF-8 (where the problem does not appear).
RESOLUTION Locale database issue
WAIVE
END
### Problem Record #360
TESTSUITE libstdcpp
TEST /27_io/basic_istream/extractors_other/{char,wchar_t}/1.cc 1
SEVERITY failed
COMMENT This failure is currrently being evaluated.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2533 | Bug #2533
RESOLUTION Unknown
WAIVE
END
### Problem Record #361
STANDARD LSB
TESTSUITE libstdcpp
TEST /26_numerics/complex/13450.cc 1
SEVERITY failed
MARKER void test01_do(T, T) [with T = long double]: Assertion `abs(ref - res1) < eps' failed.
OR
MARKER void test01_do(T, T) [with T = long double]: Assertion `abs(ref - res2) < eps' failed.
COMMENT This is caused by improper precision in measuring the long double result.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2447 | Bug #2447
RESOLUTION Known Problem
WAIVE
END
### Problem Record #362
STANDARD LSB <= 4.0
TESTSUITE libstdcpp < 4.1.0-8
TEST /27_io/basic_istream/extractors_arithmetic/{char,wchar_t}/exceptions_badbit_throw.cc 1
| /27_io/basic_ostream/inserters_arithmetic/{char,wchar_t}/exceptions_badbit_throw.cc 1
SEVERITY failed
MARKER void test_badbit() [with T = bool]: Assertion `false' failed.
COMMENT These tests have since been corrected by rebuilding with a fixed LSB SDK.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2450 | Bug #2450
RESOLUTION SDK Issue
WAIVE
END
### Problem Record #363
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-qt4 < 4.0.5-1
TEST tst_QTextDocumentFragment_html_anchorColor 112
SEVERITY failed
COMMENT This problem appears to be caused by an interaction with Qt 4.4 and Xvfb. As the issue (color cariance of a link) is not an ABI issue, the test has been disabled in current test builds.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2517 | Bug #2517
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #364
TESTSUITE desktop | desktop-qt4
TEST tst_QColor_setNamedColor 4
| tst_QItemSelectionModel_selectedRows 10
| tst_QLineEdit_selectedText 30
| tst_QPixmapCache_cacheLimit 1
| tst_QTreeView_construction 2
| tst_QTreeView_itemDelegate 14
| tst_QUuid_less 6
| tst_QItemSelectionModel_selectedColumns 11
SEVERITY failed
COMMENT These failures are seen with Qt 4.4.
COMMENT See the LSB Bugzilla for more details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2519 | Bug #2519
RESOLUTION Unknown
WAIVE
END
### Problem Record #365
TESTSUITE desktop | desktop-qt4
TEST tst_QDataWidgetMapper_mappedWidgetAt 7
| tst_QHeaderView_moveSectionAndReset 38
| tst_QLabel_focusPolicy 13
| tst_QListView_batchedMode 16
| tst_QStyleOption_qstyleoptioncast 1
| tst_QTableWidget_itemData 18
| tst_QTextDocumentFragment_html_rowSpans2 109
| tst_QTextDocumentFragment_css_nodeNameCaseInsensitivity 123
| tst_QTextTable_splitCells 14
SEVERITY failed
COMMENT The Qt 4 tests assume that some changes made in Qt 4.2.3 were made, when they should not have.
COMMENT See the LSB Bugzilla for more details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2515 | Bug #2515
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #366
TESTSUITE desktop | desktop-qt4
TEST tst_QListView_singleSelectionRemoveRow 12
SEVERITY failed
MARKER Compared values are not the same
COMMENT When the current item in a QListView is deleted, the Qt spec does not appear to define which item becomes current, but the test assumes that the preceding item becomes current.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2601 | Bug #2601
RESOLUTION Possible test suite issue
WAIVE
END
### Problem Record #367
TESTSUITE desktop | desktop-qt4
TEST tst_QMetaObject_invokeQueuedMetaMember 3
SEVERITY failed
MARKER QMetaMethod::invoke
COMMENT The test expects a specific message to be received to indicate success of the test, which does not take into account the possibility of that string changing in the implementation.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2602 | Bug #2602
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #368
TESTSUITE desktop | desktop-qt4
TEST tst_QTextDocumentFragment_whitespaceWithFragmentMarkers 66
SEVERITY failed
COMMENT The test assumes that whitespace added to the HTML document is unchanged when converted to plain text, but that assumption is not mentioned in the spec.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2603 | Bug #2603
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #369
TESTSUITE desktop | desktop-qt4
TEST tst_QDateTime_addSecs 18
| tst_QDateTime_addMSecs 19
| tst_QDateTime_toTimeSpec 20
| tst_QDateTime_toLocalTime 21
| tst_QDateTime_toUTC 22
| tst_QDateTime_secsTo 24
SEVERITY failed
COMMENT There is some dispute as to whether this test properly calculates the time zone in these cases.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2605 | Bug #2605
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #370
TESTSUITE desktop | desktop-qt4
TEST tst_QItemModel_rowCount 2
| tst_QItemModel_columnCount 3
| tst_QItemModel_hasIndex 4
| tst_QItemModel_index 5
| tst_QItemModel_data 7
| tst_QItemModel_sort 12
SEVERITY failed
COMMENT Although not specified in the LSB, the tests for Qt 4 database support require a working database driver. This is best supplied by installing the SQLite driver for Qt 4. Installing this driver should cause this test to pass.
RESOLUTION Missing test requirement
END
### Problem Record #371
TESTSUITE qt4-azov
TEST /Qt4_SQL-t2c/tests/QSqlDatabase/QSqlDatabase {1..4,7,11,13,18..26,28,30,32..37,39,41,43..46}
| /Qt4_SQL-t2c/tests/QSqlRelationalTableModel/QSqlRelationalTableModel {1,6,7,12,17,18}
| /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel {2,3,6,9,13,18,19,20,22,26,38,41..43,46..48}
| /Qt4_SQL-t2c/tests/QSqlQueryModel/QSqlQueryModel {5,6,8,12,14,15,21,24,27}
| /Qt4_SQL-t2c/tests/QSqlQuery/QSqlQuery {2,4,5..9,11,13..18,22,25,27,31,32,35,36,38,39,43,44}
SEVERITY failed
MARKER QSqlDatabase::isDriverAvailable("QSQLITE")
COMMENT Although not specified in the LSB, the tests for Qt 4 database support require a working database driver. This is best supplied by installing the SQLite driver for Qt 4. Installing this driver should cause this test to pass.
RESOLUTION Missing test requirement
END
### Problem Record #372
TESTSUITE qt4-azov
TEST /Qt4_Drag_and_Drop-t2c/tests/QDropEvent/QDropEvent 3
SEVERITY failed
COMMENT Newer versions of Qt allow new drop actions, but the test assumes these drop actions will fail.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2598 | Bug #2598
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #373
TESTSUITE qt4-azov
TEST /Qt4_Network-t2c/tests/QNetworkAddressEntry/QNetworkAddressEntry 11
SEVERITY failed
COMMENT This test fails to account for a different netmask in the presence of IPv6.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2599 | Bug #2599
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #374
TESTSUITE qt4-azov
TEST /Qt4_Widgets-t2c/tests/QDial/QDial 7
SEVERITY unresolved
COMMENT On newer versions of Qt, this test crashes.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2600 | Bug #2600
RESOLUTION Unknown
WAIVE
END
### Problem Record #375
TESTSUITE qt4-azov
TEST /Qt4_Paint_Device-t2c/tests/QPrinter/QPrinter {7,36,53}
SEVERITY failed
COMMENT This failure is caused by an incorrect test.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2614 | Bug #2614
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #376
TESTSUITE qt4-azov
TEST /Qt4_Menus-t2c/tests/QMenuBar/QMenuBar 22
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0 > 0'
COMMENT This is caused by a bug in the test suite, which has been fixed in newer versions of the test suite.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #377
TESTSUITE xts5
TEST /tset/Xlib8/flushgc/Test {1,2}
SEVERITY unresolved
MARKER unexpected signal 6 (SIGABRT) received
COMMENT This may be an issue with the test's use of xcb.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2636 | Bug #2636
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #378
TESTSUITE xts5
TEST /tset/Xlib13/grbpntr/Test 20
SEVERITY failed
COMMENT This failure occasionally happens when the test suite is run on a virtual machine. So far, it hasn't been seen on a native test run.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2532 | Bug #2532
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #379
TESTSUITE xts5
TEST /tset/Xlib12/staftrfnct/Test 1
SEVERITY failed
COMMENT These tests do not appear to interact well with the XGE extension.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2581 | Bug #2581
RESOLUTION Test interaction issue with extension
WAIVE
END
### Problem Record #380
TESTSUITE python
TEST /usr/bin/python 21
SEVERITY failed
COMMENT This failure occurs on some distributions, and may be a test issue.
COMMENT See the LSB Bugzilla for details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2516 | Bug #2516
RESOLUTION Unknown
WAIVE
END
### Problem Record #381
TESTSUITE python
TEST /usr/bin/python 54
SEVERITY failed
COMMENT This may be caused on systems where the "site-packages" directory is not on sys.path.
COMMENT See the LSB Bugzilla for details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2595 | Bug #2595
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #382
TESTSUITE python
TEST /usr/bin/python 87
SEVERITY failed
MARKER gaierror: [Errno -2] Name or service not known
COMMENT This may be caused when the hostname of the test machine cannot be resolved.
RESOLUTION Possible network issue
END
### Problem Record #383
TESTSUITE perl
TEST ../ext/B/t/concise-xs.t {768,752}
| ../ext/B/t/f_sort.t {763,776}
| ../ext/B/t/f_map.t {758,778}
| ../ext/Devel/Peek/t/Peek.t {658,827}
SEVERITY failed
COMMENT The Perl tests, in some cases, depend on Perl internals that are allowed to change. When this happens, we waive the results.
COMMENT See the LSB Bugzilla for details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1889 | Bug #1889
RESOLUTION Test suite deficency
WAIVE
END
### Problem Record #384
TESTSUITE perl
TEST ../lib/Pod/t/htmlview.t 437
| ../lib/Pod/t/basic.t 448
| ../lib/ExtUtils/t/INST.t 583
| ../lib/ExtUtils/t/INST_PREFIX.t 591
| ../lib/ExtUtils/t/Embed.t 592
SEVERITY failed
COMMENT A number of tests in the Perl test suite have been determined to be inappropriate for testing the API, and have been dropped.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2508 | Bug #2508
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #385
TESTSUITE perl
TEST ../lib/Term/Cap.t 380
SEVERITY failed
COMMENT The /etc/termcap file, required for this test, is not required by the LSB.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #386
TESTSUITE perl
TEST op/groups.t 110
SEVERITY failed
COMMENT This is caused by older versions of DTK Manager, when running the Perl tests with an incorrect path.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2567 | Bug #2567
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #387
TESTSUITE perl
TEST ../lib/Benchmark.t 420
SEVERITY failed
COMMENT This failure has been seen occasionally when running the test suite within a VM. Try running the test again, or run the tests on native hardware.
RESOLUTION Timing issue
END
### Problem Record #388
TESTSUITE perl
TEST ../ext/Sys/Syslog/t/syslog.t 686
SEVERITY failed
COMMENT The facility used to test the syslog module doesn't work on some distributions. The facility is not required to work by the specification.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2613 | Bug #2613
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #389
TESTSUITE perl
TEST ../lib/Net/Ping/t/200_ping_tcp.t 655
| ../lib/Net/Ping/t/400_ping_syn.t 657
| ../lib/Net/Ping/t/410_syn_host.t 658
SEVERITY unreported
COMMENT This may happen on machines without Internet access.
WAIVE FIP
END
### Problem Record #390
TESTSUITE libchk < 4.0.2
TEST libstdc++.so.6 {3144,3152}
SEVERITY failed
COMMENT This problem is caused by a bug in libstdc++ from gcc versions before 4.3.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1235 | Bug #1235
RESOLUTION Known problem
WAIVE
END
### Problem Record #391
# these are the same tests as the previous two,
# but bug 2745 caused the test numbers to all change
TESTSUITE libchk >= 4.0.2
TEST libstdc++.so.6 {151,159}
SEVERITY failed
COMMENT This problem is caused by a bug in libstdc++ from gcc versions before 4.3.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2844 | Bug #2844
RESOLUTION Known problem
WAIVE
END
### Problem Record #392
TESTSUITE libchk
TEST libasound.so.2 1
SEVERITY failed
MARKER Unable to find library
COMMENT The ALSA module is classified as trial use, and so distributions are not required to provide this library.
RESOLUTION Trial Use Module
WAIVE
END
### Problem Record #393
STANDARD LSB <= 4.0
TESTSUITE libchk
TEST libnspr4.so 1
| libnss3.so 1
| libssl3.so 1
SEVERITY failed
MARKER Unable to find library
COMMENT The NSS module is classified as trial use, and so distributions are not required to provide this library.
RESOLUTION Trial Use Module
WAIVE
END
### Problem Record #394
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GdkImages/GdkImages 2
SEVERITY failed
MARKER it's not a GDK_TYPE_IMAGE
COMMENT When run under Xvfb, some of the test images aren't registered correctly for some reason.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1893 | Bug #1893
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #395
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkToolbar/GtkToolbar 15
SEVERITY failed
MARKER tooltips is 1, should be 0
COMMENT The tooltip ABI changed upstream in a compatible way.
RESOLUTION Specification deficiency
WAIVE
END
### Problem Record #396
STANDARD LSB >= 3.2
TESTSUITE desktop < 4.0.5-1 | desktop-gtkvts < 4.0.5-1 | desktop > 4.1.0 & < 4.1.5-2 | desktop-gtkvts > 4.1.0 & < 4.1.5-2
TEST -g /tests/functions/GTimer/GTimer 2
| /tests/functions/MainLoop/MainLoop {6,7}
SEVERITY failed
COMMENT These tests have intermittent failures, presumably related to machine load or issues in running under a virtual machine and have been disabled in later versions of the tests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2621 | bug 2621
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #397
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GdkCursors/GdkCursors {9..24}
SEVERITY failed
COMMENT This test uses reference counting to determine test success or failure, but does not take into account the possibility of additional references being created by the implementation.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2589 | Bug #2589
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #398
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkEntry/GtkEntry {20..23,28..59}
SEVERITY failed
MARKER text length is 0 but it should be > 0
COMMENT GTK+ has disabled clipboard functions for invisible entry widgets.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2589 | Bug #2589
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #399
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkAdjustment/GtkAdjustment {61,62,63,69,72..75}
| /tests/functions/GtkSpinButton/GtkSpinButton 48
SEVERITY failed
COMMENT GTK+ 2.14 deprecated setting the page size to a nonzero value.
COMMENT See the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2589 | Bug #2589
RESOLUTION Possible test issue
WAIVE
END
### Problem Record #404
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 41
SEVERITY failed
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.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #405
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_base_gobject/gobject_base_gobject {1..6,11..16}
SEVERITY unresolved
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.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #406
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_type_module/gobject_type_module 5
| /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance {34,37..41}
SEVERITY unresolved
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, registered via g_type_register_dynamic.
COMMENT Detailed description of this problem is available here:
LINK http://linuxtesting.org/results/report?num=S0837
RESOLUTION Known problem
END
### Problem Record #407
TESTSUITE olver
TEST /olver/math/cexp/tests/cpow_spec 5162
SEVERITY failed
MARKER Registered bug: bug516_2(cpow)
COMMENT The cpow(x, y) family of functions shall compute the complex power function x^y, with a branch cut for the first parameter along the negative real axis.
COMMENT If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpow(x, y) return (-1) + (near)(1e-16) * i. This result is too far from (-1).
COMMENT If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpow(x, y) return (-1) - (near)(1e-16) * i. This result is too far from (-1).
COMMENT If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1).
COMMENT If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1).
COMMENT This failure is waived pending a fix from upstream.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=2912 | LSB bug.
LINK http://sourceware.org/bugzilla/show_bug.cgi?id=14473 | Upstream bug.
RESOLUTION Upstream issue.
WAIVE
END
### Problem Record #408
TESTSUITE olver
TEST /olver/pthread/mutex/tests/trylock_spec 501
SEVERITY failed
MARKER Registered bug: bug501(pthread_mutex_trylock)
COMMENT Function pthread_mutex_trylock() tries to lock a mutex. It shall return EBUSY error code 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
LINK http://linuxtesting.org/results/report?num=S0501
RESOLUTION Known problem
END
### Problem Record #409
TESTSUITE olver
TEST /olver/util/format/tests/strptime_spec 810
SEVERITY failed
MARKER Registered bug: bug810(strptime)
COMMENT Upstream believes that this behavior in strptime is valid according to POSIX, and will not be fixing it. Thus, we are waiving the test failure, and will be modifying the test to match upstream's expectations.
COMMENT
COMMENT Original description of the problem:
COMMENT
COMMENT Function strptime can not work properly with some input data.
COMMENT
COMMENT If buf = "0 Sun 2006" and format = "%U %a %Y" then strptime must find first Sunday in first week (Sunday as the first day of the week) 2006 year. 2006 year begins with Sunday.
COMMENT But after call to strptime tm.tm_yday = -7.
COMMENT If buf = "0 Mon 2007" and format = "%W %a %Y" then strptime must find first Monday in first week (Monday as the first day of the week) 2007 year. 2007 year begins with Monday.
COMMENT But after call to strptime tm.tm_yday = -7.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0810 | LinuxTesting (problem with link)
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2914 | LSB bug 2914
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #410
TESTSUITE olver
TEST /olver/util/format/tests/getdate_spec 803
SEVERITY failed
MARKER Registered bug: bug803(getdate)
COMMENT The function getdate uses strptime internally, which does not accept leading or trailing whitespace, but getdate does allow this. This has been fixed upstream. Additional information about this bug may be found at:
LINK http://linuxtesting.org/results/report?num=S0803
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2913 | LSB Bug 2913
LINK http://sourceware.org/git/?p=glibc.git;a=commit;h=abe7f530bf5c741fe6f0658da7be59d8db168f7f | Upstream fix in glibc
RESOLUTION Known problem
END
### Problem Record #411
TESTSUITE olver
TEST /olver/util/format/tests/getdate_spec 812
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
LINK http://linuxtesting.org/results/report?num=S0812
RESOLUTION Known problem
END
### Problem Record #412
TESTSUITE olver
TEST /olver/util/format/tests/strptime_spec 808
SEVERITY failed
MARKER Registered bug: bug808(strptime)
COMMENT Values of all fields of struct tm shall be positive or 0.
COMMENT Upstream has indicated that it does not consider this a violation of POSIX, and that mktime() should be used to normalize the time.
COMMENT Additional information about this bug may be found at
LINK http://linuxtesting.org/results/report?num=S0808 | LinuxTesting (problem with link)
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=2914 | LSB bug 2914
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #413
TESTSUITE olver
TEST /olver/util/format/tests/strptime_spec 816
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
LINK http://linuxtesting.org/results/report?num=S0816
RESOLUTION Known problem
END
### Problem Record #414
TESTSUITE olver
TEST /olver/util/format/tests/getdate_spec 818
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
LINK http://linuxtesting.org/results/report?num=S0818
RESOLUTION Known problem
END
### Problem Record #415
TESTSUITE olver
TEST /olver/math/exp/tests/exp2_spec 821
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
### Problem Record #416
TESTSUITE olver
TEST /olver/math/exp/tests/expm1_spec 822
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
### Problem Record #417
TESTSUITE olver
TEST /olver/math/exp/tests/exp_spec 823
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
### Problem Record #418
TESTSUITE olver
TEST /olver/math/error/tests/erfc_spec 824
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
LINK http://linuxtesting.org/results/report?num=S0824
RESOLUTION Known problem
END
### Problem Record #419
TESTSUITE olver
TEST /olver/memory/mman/tests/shm_open_spec 825
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
LINK http://linuxtesting.org/results/report?num=S0825
RESOLUTION Known problem
END
### Problem Record #420
TESTSUITE olver
TEST /olver/pthread/sem/tests/sem_open_spec 826
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
LINK http://linuxtesting.org/results/report?num=S0826
RESOLUTION Known problem
END
### Problem Record #421
TESTSUITE olver
TEST /olver/process/meta/tests/nice_spec 827
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
LINK http://linuxtesting.org/results/report?num=S0827
RESOLUTION Known problem
END
### Problem Record #422
TESTSUITE olver
TEST /olver/process/meta/tests/getpriority_spec 828
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
LINK http://linuxtesting.org/results/report?num=S0828
RESOLUTION Known problem
END
### Problem Record #423
TESTSUITE olver
TEST /olver/process/meta/tests/setpriority_spec 829
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
LINK http://linuxtesting.org/results/report?num=S0829
RESOLUTION Known problem
END
### Problem Record #424
TESTSUITE olver
TEST /olver/math/real/tests/fdim_spec 830
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
LINK http://linuxtesting.org/results/report?num=S0830
RESOLUTION Known problem
END
### Problem Record #425
TESTSUITE olver
TEST /olver/math/real/tests/fdim_spec 831
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
LINK http://linuxtesting.org/results/report?num=S0831
RESOLUTION Known problem
END
### Problem Record #426
TESTSUITE olver
TEST /olver/math/real/tests/drem_spec 832
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
LINK http://linuxtesting.org/results/report?num=S0832
RESOLUTION Known problem
END
### Problem Record #427
TESTSUITE olver
TEST /olver/util/search/tests/hsearch_spec 833
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
LINK http://linuxtesting.org/results/report?num=S0833
RESOLUTION Known problem
END
### Problem Record #428
TESTSUITE olver
TEST /olver/math/real/tests/fdim_spec 834
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
LINK http://linuxtesting.org/results/report?num=S0834
RESOLUTION Known problem
END
### Problem Record #429
TESTSUITE olver
TEST /olver/math/real/tests/lrint_spec 835
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
LINK http://linuxtesting.org/results/report?num=S0835
RESOLUTION Known problem
END
### Problem Record #430
TESTSUITE olver
TEST /olver/ncurses/window/tests/refresh_spec 836
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
LINK http://linuxtesting.org/results/report?num=S0836
RESOLUTION Known problem
END
### Problem Record #431
TESTSUITE desktop-t2c <= 4.0.90
TEST /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 4
SEVERITY failed
MARKER The file was not a directory and the font was not added to the set
COMMENT On some systems (e.g. Ubuntu 10.04), bitmap fonts are ignored by some fontconfig functions (at least by FcFileScan), even the fonts with Latin-1 encoding. This is controlled by fontconfig configuration files.
COMMENT
COMMENT The fontconfig reference manual does not require the implementation to actually ignore any of the bitmap fonts except those with non-Unicode and non-Latin-1 encoding. It seems however that any font MAY be ignored and this does not violate the requirements for fontconfig.
COMMENT
COMMENT To check FcFileScan properly, the tests from the newer versions of the suite use TrueType fonts instead of bitmap fonts.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #432
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_closures/gobject_closures 56
SEVERITY failed
MARKER The callback function of the closure was expected to be invoked when the source was executed - but it wasn't.
COMMENT g_source_set_clousre for GSource, created via g_child_watch_source_new (), shouldn't require closure_callback and closure_marshal fields to be set in GSourceFuncs structure.
LINK http://linuxtesting.org/results/report?num=S0840
RESOLUTION Known problem
WAIVE
END
### Problem Record #433
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_closures/gobject_closures {38,39}
SEVERITY failed
MARKER 'destroy_notify' function wasn't called when closure is invalidated.
COMMENT After g_closure_invalidate 'user_data' parameter of closure is no longer used, but 'destroy_notify' isn't called. 'destroy_notify' may be called at closure destroying state, but this is not the same, as 'when user_data is no longer used', as stated in documentation.
LINK http://linuxtesting.ru/results/impl_reports_admin?action=details&num=S0838
RESOLUTION Known problem
WAIVE
END
### Problem Record #434
TESTSUITE desktop-t2c <= 4.0.90
TEST /gobject-t2c/tests/gobject_closures/gobject_closures {5,36}
SEVERITY unresolved
COMMENT Tests allocate GClosure structure, but use it as GCClosure, which has greater size. So, some readings/writtings are done out of boundaries of the allocated memory.
COMMENT The problem should be fixed in a newer version of the test suite.
END
### Problem Record #435
#TESTSUITE desktop-t2c
#TEST /glib-t2c/tests/glib_threads/glib_threads {1,2,3}
# SEVERITY failed
# MARKER priority was not set
#COMMENT A race condition could still occur in these tests: the operations were performed in a thread-unsafe order in one of the thread functions.
#COMMENT The problem should be fixed in a newer version of the test suite.
#RESOLUTION Test suite deficiency
#WAIVE
#END
### Problem Record #436
STANDARD LSB <= 4.0
TESTSUITE qt3-azov < 4.0.2-1 | qt4-azov < 4.0.3-1
TESTCASE /Normal_Tests-t2c/tests/QSessionManager/QSessionManager
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT On the target system function SmsGenerateClientID returns NULL unexpectedly that causes the test to crash. Current versions of the test suite have corrected this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3014 | bug 3014
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #437
STANDARD LSB >= 3.2
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GMisc/GMisc 2
SEVERITY failed
MARKER g_get_prgname: failed
COMMENT This was an upstream regression with glib-2.23
COMMENT {noreplace}See GNOME bug 563627
COMMENT or LSB bug 2849 for more information.
COMMENT The change was later reverted by upstream.{/noreplace}
RESOLUTION Known Problem
WAIVE
END
### Problem Record #438
TESTSUITE olver
TEST /olver/math/complex/tests/cproj_spec 841
SEVERITY failed
MARKER Registered bug: bug841(cproj)
COMMENT According to LSB, the cproj(z) family of functions shall compute a projection of z onto Riemann sphere: z projects to z except all complex infinities.
COMMENT The implementation in glibc does a stereographic projection that contradicts the standard.
LINK http://sourceware.org/bugzilla/show_bug.cgi?id=10401 | Bug #10401
RESOLUTION Upstream bug
WAIVE
END
### Problem Record #439
ARCHITECTURE PPC32
TESTSUITE core
TEST /tset/POSIX.os/ioprim/select/T.select 6
SEVERITY failed
MARKER errno is expected to be 22[EINVAL], returned 14
COMMENT We believe this was a kernel issue on ppc32, that has since been corrected. There is a thread in LKML here:
COMMENT
LINK http://lkml.org/lkml/2008/9/23/6
RESOLUTION Known Problem
END
### Problem Record #440
TESTSUITE core
TEST /tset/POSIX.os/devclass/c_lflag/T.c_lflag {1,5,7,8}
SEVERITY failed
MARKER read() from VSX_TERMIOS_LOOP returned 54, expected 53
COMMENT This was a regression in n_tty.c from the Linux kernel between 2.6.28.10 and 2.6.29. It has been corrected in more recent kernel versions.
COMMENT See the entry in the LSB Bugzilla for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2692
RESOLUTION Known Problem
END
### Problem Record #441
STANDARD LSB > 3.0
TESTSUITE core
TEST /tset/POSIX.os/procenv/getlogin/T.getlogin 1
SEVERITY failed
MARKER getlogin() returned
MARKER expected "vsx0"
COMMENT This is most likely due to the underlying user account used when starting dist-checker. See LSB bug
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3089
RESOLUTION Known problem
WAIVE
END
### Problem Record #442
STANDARD LSB > 3.0
TESTSUITE core
TEST /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r {1,2}
SEVERITY failed
MARKER Unexpected login name
MARKER should be vsx0
OR
MARKER getlogin_r, expected
COMMENT This is most likely due to the underlying user account used when starting dist-checker. Rather than starting from a user account and then su - to start the checker, start the checker as a normal user and enter either the sudo or root password when prompted.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3089 | bug 3089
RESOLUTION Known problem
WAIVE
END
### Problem Record #445
STANDARD LSB >= 3.2
TESTSUITE perl
TEST ../ext/Storable/t/code.t 372
SEVERITY failed
MARKER Failed 59/59 tests, 0.00% okay
COMMENT Some distributions have split perl-Safe into a separate package from perl, without updating their
COMMENT "lsb" dependencies to still pull it in. Install perl-Safe and try running the test again.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3104 | Bug 3104
RESOLUTION Distribution Problem
END
### Problem Record #446
STANDARD LSB >= 3.2
TESTSUITE perl
TEST ../ext/Safe/t/safe3.t 363
SEVERITY failed
MARKER Failed 2/2 tests, 0.00% okay
COMMENT Some distributions have split perl-Safe into a separate package from perl, without updating their
COMMENT "lsb" dependencies to still pull it in. Install perl-Safe and try running the test again.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3104 | Bug 3104
RESOLUTION Distribution Problem
END
### Problem Record #447
STANDARD LSB >= 3.2
TESTSUITE perl
TEST ../ext/Safe/t/safe1.t 361
| ../ext/Safe/t/safe2.t 362
SEVERITY unreported
COMMENT Some distributions have split perl-Safe into a separate package from perl, without updating their
COMMENT "lsb" dependencies to still pull it in. Install perl-Safe and try running the test again.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3104 | Bug 3104
RESOLUTION Distribution Problem
END
### Problem Record #448
STANDARD LSB >= 3.2
TESTSUITE perl
TEST ../lib/autouse.t 407
| ../lib/autouse.t 397
SEVERITY failed
MARKER Failed 1/12 tests, 91.67% okay
COMMENT Some distributions have split perl-Class-ISA into a separate package from perl, without updating their "lsb" dependencies to still pull it in. Install perl-Class-ISA and try running the test again.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3092 | Bug 3092
COMMENT Note: Upstream has removed this module from perl-core, and LSB will follow suite with deprecation, but as of LSB 4.1 it is still required.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3096 | Bug 3096
RESOLUTION Distribution Problem
END
### Problem Record #449
STANDARD LSB >= 3.2
TESTSUITE perl
TEST ../lib/Class/ISA/t/00_about_verbose.t 445
| ../lib/Class/ISA/t/01_old_junk.t 446
| ../lib/Class/ISA/t/00_about_verbose.t 432
| ../lib/Class/ISA/t/01_old_junk.t 433
SEVERITY failed
MARKER Failed 2/2 tests, 0.00% okay
COMMENT Some distributions have split perl-Class-ISA into a separate package from perl, without updating their "lsb" dependencies to still pull it in. Install perl-Class-ISA and try running the test again.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3092 | Bug 3092
COMMENT Note: Upstream has removed this module from perl-core, and LSB will follow suite with deprecation, but as of LSB 4.1 it is still required.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3096 | Bug 3096
RESOLUTION Distribution Problem
END
### Problem Record #450
STANDARD LSB = 4.0
TESTSUITE core
TEST /tset/LSB.os/network/sendto/T.sendto 10
| /tset/LSB.os/network/sendmsg/T.sendmsg 10
SEVERITY failed
MARKER failed by returning Invalid argument instead of EMSGSIZE
COMMENT This is an issue in the core tests for LSB 4.0/4.1 beta. The test attempts to send a large message to a socket, expecting to fail with EMSGSIZE. The test fails to check that sendto/sendmsg return -1 before checking errno. On some systems, the large message transmission actually succeeds and there is no error. Updated test code accepts this condition and returns UNTESTED.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3081 | bug 3081
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #451
TESTSUITE core
TEST /tset/LSB.fhs/root/bin/bin-tc {11,43}
SEVERITY failed
MARKER Expected output to stdout, but none written
COMMENT These tests, for /bin/dmesg and /bin/hostname, expect output on stdout. On systems with SELinux enabled, it appears such output is suppressed. You can try changing the mode /etc/sysconfig/selinux to disabled and re-run the test.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2302 | bug 2302
RESOLUTION Known Problem
END
### Problem Record #452
STANDARD LSB >= 4.0
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_key_parser/glib_key_parser 43
SEVERITY failed
MARKER Returned value is "Hallo" should be "Hello".
MARKER Translated value for current locale is wrong.
OR
MARKER Returned value is "Bonjourn" should be "Hello".
MARKER Translated value for current locale is wrong.
OR
MARKER Returned value is "Ciao" should be "Hello".
MARKER Translated value for current locale is wrong.
COMMENT This test can fail if the system under test is using a de, fr, or it locale.
COMMENT The test calls g_key_file_get_locale_string with NULL as a locale value, expecting a return of "Hello".
COMMENT If one of the above 3 locales is being used, the test instead returns the key value as defined in the test setup.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2682 | Bug 2682
RESOLUTION Known Problem
WAIVE
END
### Problem Record #453
STANDARD LSB >= 3.2
ARCHITECTURE S390
TESTSUITE core
TEST /tset/POSIX.os/files/ftruncate/T.ftruncate 2
SEVERITY failed
MARKER Checks the ftruncate() for error value of EINVAL
MARKER ftruncate() returned 0, expected to return -1
COMMENT This appears to be a known problem on the s390 systems we have access to, and unique to this architecture.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3093 | Bug 3093
RESOLUTION Known Problem
END
### Problem Record #454
STANDARD LSB >= 3.2
ARCHITECTURE S390
TESTSUITE core
TEST /tset/POSIX.os/files/truncate/T.truncate 3
SEVERITY failed
MARKER Checks the truncate() for error value of EINVAL
MARKER truncate() returned 0, expected to return -1
COMMENT This appears to be a known problem on the s390 systems we have access to, and unique to this architecture.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3093 | Bug 3093
END
### Problem Record #455
STANDARD LSB >= 4.1
TESTSUITE core-t2c
TEST /libc-t2c/tests/system/system
SEVERITY failed
MARKER Expected to return non null value
MARKER Requirement failed:
MARKER {getutent.01}
COMMENT This test can fail if run in a chroot or a pristine system with no /var/run/utmp or /var/log/wtmp. It should not fail if these files are present.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2898 | Bug 2898
END
### Problem Record #456
STANDARD LSB >= 3.2
TESTSUITE perl < 4.0.8-1
TEST ../lib/CGI/t/fast.t 438
SEVERITY failed
MARKER FAILED test 7 Failed 1/7 tests, 85.71% okay
COMMENT perl-CGI, as well as the upstream testsuite have changed slightly, and the behavior expected by this test is no longer true. Subtest has been disable in newer versions of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3128 | bug 3128
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #457
STANDARD LSB >= 4.0
TESTSUITE core >= 4.1.0-1 & < 4.1.7-1 | core < 4.0.6-1
TEST /tset/LSB.os/ioprim/writev_L/T.writev_L 30
| /tset/LSB.os/ioprim/readv_L/T.readv_L 24
SEVERITY failed
MARKER ERRNO VALUES: expected: 22 (EINVAL)
COMMENT These tests continue to have issues and has been updated to return UNTESTED (disabled)
LINK http://bugs.linuxbase.org/show_bug.cgi?id=844 | bug 844
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #458
STANDARD LSB >= 4.0
TESTSUITE core < 4.0.6-1 | core >= 4.1.0-1 & < 4.1.7-2
TEST -g /tset/LSB.os/procprim/exec_L/T.exec{l,v}{,e,p}_L 7
| /tset/LSB.os/mfiles/msync_P/T.msync_P 1
SEVERITY failed
MARKER expected value between
OR
MARKER expected greater than
COMMENT These tests used a fixed, compile-time value as a delay and could fail on some systems. Updated versions of the test use a runtime determined delay value.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1614 | bug 1614
LINK http://bugs.linuxbase.org/show_bug.cgi?id=1618 | bug 1618
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #459
STANDARD LSB >= 3.2
TESTSUITE core < 4.0.6-1 | core >= 4.1.0-1 & < 4.1.4-1
TEST -g /tset/POSIX.os/procenv/times/T.times {3,5}
| /tset/POSIX.os/procprim/fork/T.fork 5
SEVERITY failed
MARKER tms_utime (as returned by times()) does not seem to change
OR
MARKER depends on success of test 3
OR
MARKER deletion reason: tms_utime and tms_stime are not both non-zero before fork()
COMMENT These tests depended on a fixed loop processing iteration in an internal use_time() and waste_time() function to allow for a sufficient change in tms_utime. They have since been changed to attempt to calculate a loop based on the runtime value from sysconf(_SC_CLK_TCK).
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2270 | bug 2270
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2688 | bug 2688
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #460
STANDARD LSB >= 3.2
TESTSUITE desktop < 4.0.5-1 | desktop-gtkvts < 4.0.5-1 | desktop >= 4.1.0 & < 4.1.4-1 | desktop-gtkvts >= 4.1.0 & < 4.1.4-1
TEST /tests/functions/Param_Value/Param_Value 20
SEVERITY failed
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This test has issues newer versions of glib2 (2.23.1+), apparently related to changes implemented to change the locking behavior and make things atomic. It has been disabled in later versions of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2868 | bug 2868
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #461
STANDARD LSB >= 3.2
TESTSUITE desktop < 4.0.5-1 | desktop-gtkvts < 4.0.5-1 | desktop >= 4.1.0 & < 4.1.3-1 | desktop-gtkvts >= 4.1.0 & < 4.1.3-1
TEST -g /tests/functions/Themeable_Stock_Images/Themeable_Stock_Images {195..210}
SEVERITY failed
MARKER Icon is not rendered
COMMENT Upstream changes in GTK have caused the test method used by these tests to fail. While the basic test assertion, that gtk_icon_set_render_icon() should never return NULL, seems valid, there isn't any movement upstream to make a change, and the tests have been disabled in more recent builds.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3044 | bug 3044
LINK https://bugzilla.gnome.org/show_bug.cgi?id=629878 | upstream bug
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #462
STANDARD LSB >= 3.2
TESTSUITE perl < 4.0.8-1 | perl >= 4.1.0 & < 4.1.2-1
TEST ../lib/Test/Simple/t/overload.t
| ../lib/Test/Simple/t/tbt_01basic.t
| ../lib/overload.t
SEVERITY failed
MARKER FAILED tests
OR
MARKER The test case returned no result
COMMENT Upstream changes in perl-Test-Simple have rendered the methods used in the test suite invalid and the tests have been disabled in more recent builds.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3113 | bug 3113
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #463
STANDARD LSB >= 3.2
TESTSUITE desktop < 4.0.5-1 | desktop-gtkvts < 4.0.5-1 | desktop >= 4.1.0 & < 4.1.4-1 | desktop-gtkvts >= 4.1.0 & < 4.1.4-1
TEST /tests/functions/GHashTable/GHashTable 5
SEVERITY failed
MARKER g_str_hash: failed
COMMENT The test as written expected a certain algorithm to be used to generate the hash, which is guaranteed by the specification. The test has been reworked to not have any pre-conceived expectations on the algorithm.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3133 | bug 3133
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #464
STANDARD LSB >= 3.2
TESTSUITE perl < 4.0.8-1 | perl >= 4.1.0 & < 4.1.1-2
TEST ../lib/CGI/t/html.t
SEVERITY failed
MARKER The test case returned no result
COMMENT perl-CGI upstream has changed and the method used by subtests 10,11 is no longer valid. The tests have been disabled in more recent builds of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3161 | bug 3161
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #465
STANDARD LSB >= 4.0
TESTSUITE libstdcpp < 4.1.0-8 | libstdcpp >= 4.1.0-13 & < 4.1.0-14
TEST -g /27_io/basic_filebuf/sync/{char,wchar_t}/1.cc 1
| /demangle/abi_examples/14.cc 1
| /demangle/regression/cw-13.cc 1
SEVERITY failed
MARKER Assertion `c == filebuf::traits_type::eof()' failed.
OR
MARKER Assertion `c == wfilebuf::traits_type::eof()' failed.
OR
MARKER FAIL: demangle/abi_examples/14.cc execution test
OR
MARKER FAIL: demangle/regression/cw-13.cc execution test
COMMENT Upstream has either dropped these tests or the changes are such that the new tests will fail on systems where they previously passed. Tests are disabled in the newer builds of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3182 | bug 3182
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #466
STANDARD LSB >= 4.0
TESTSUITE libstdcpp < 4.1.0-8 | libstdcpp >= 4.1.0-13 & < 4.1.0-14
TEST -g /27_io/basic_istream/tellg/{char,wchar_t}/8348.cc 1
SEVERITY failed
MARKER Assertion `test = !iss.fail()' failed.
COMMENT These tests fail again newer versions of libstdc++. Changes have been backported from upstream into newer test builds which correct the issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3182 | bug 3182
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #467
STANDARD LSB >= 4.0
TESTSUITE core < 4.0.6-1 | core >= 4.1.0-1 & < 4.1.1-1
TEST /tset/LSB.fhs/var/lib-hwclock/lib-hwclock-tc 1
SEVERITY failed
MARKER Reference 5.8.5.1
MARKER /var/lib/hwclock : State directory for hwclock (optional)
MARKER This directory contains the file /var/lib/hwclock/adjtime
MARKER In FHS 2.1, this file was /etc/adjtime, but as hwclock updates it, that was obviously incorrect.
COMMENT Test logic of this test fails if both /var/lib/hwclock and /etc/adjtime are missing. The test has been reworked to correctly handle this condition.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3188 | bug 3188
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #468
STANDARD LSB >= 3.2
TESTSUITE perl < 4.0.8-1 | perl >= 4.0.0 & < 4.1.1-1
TEST op/pat.t
SEVERITY failed
MARKER FAILED tests 940-4009 Failed 3070/4009 tests, 23.42% okay
COMMENT Upstream version of the test has changed considerably, and fails again current versions of perl. Recent builds of the test suite have disabled this test.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3194 | bug 3194
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #469
STANDARD LSB >= 3.2
TESTSUITE core < 4.0.6-1
TEST -g tset/POSIX.os/procprim/exec/T.exec{l,v}{,e,p} {15,16}
SEVERITY failed
MARKER did not accept ARG_MAX
OR
MARKER child process gave unexpected exit code 20
COMMENT These tests have issues when run against newer combinations of kernel and glibc. As the test method is rather convoluted, the tests have been disable in recent test suites.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2288 | bug 2288
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #470
STANDARD LSB <= 3.2
TESTSUITE core < 3.2.1-1
TEST /tset/POSIX.os/procenv/sysconf/T.sysconf 1
SEVERITY failed
MARKER sysconf(_SC_ARG_MAX) did not return the value of ARG_MAX
COMMENT This test incorrectly compares sysconf(_SC_ARG_MAX) to ARG_MAX (compile time value), which is not necessarily true. Updated tests have corrected the issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2288 | bug 2288
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #471
STANDARD LSB >= 3.2
TESTSUITE core < 4.0.6-1
TEST -g /tset/LSB.os/procprim/daemon/T.daemon {1,2}
SEVERITY unreported
COMMENT These tests seemed to have timing issues and/or issues with correctly reporting back the test result to the test harness. The tests have been reworked to correct the issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2398 | bug 2398
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #472
STANDARD LSB <= 4.0
ARCHITECTURE PPC64, S390X
TESTSUITE libstdcpp < 4.1.0-8
TEST /27_io/basic_ostream/inserters_arithmetic/{char,wchar_t}/4402.cc 1
SEVERITY failed
MARKER Assertion `os && os.str() == largebuf' failed
COMMENT This test was performing incorrectly on some architectures due to issues with the LSB SDK. A rebuilt test with an updated SDK corrects the issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2451 | bug 2451
RESOLUTION SDK Issue
WAIVE
END
### Problem Record #473
STANDARD LSB >= 4.0
TESTSUITE desktop-t2c < 4.0.3-1
TEST /gdk-pixbuf-t2c/tests/FileSaving/FileSaving {29..34}
SEVERITY unresolved
MARKER Cannot load pixbuf from file: Couldn't recognize the image file format for file
COMMENT Due to system variances as to where the cache file for pixbuf loaders is located, as well as some versions of libgdk_pixbuf actually scanning for mimetypes, these tests would fail. Improvements in detecting the system location for the pixbuf cache and adding an Overrides.xml for the mimetype issue seem to have stabilized the test behavior.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2455 | bug 2455
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #474
ARCHITECTURE S390X
TESTSUITE libstdcpp < 4.1.0-8
TEST /22_locale/{money_put,numput}/put/{char,wchar_t}/{4,wrapped_env,wrapped_locale}.cc
SEVERITY failed
COMMENT It is believed that these test failures were due to issues with long-double support in the LSB SDK. New versions of the test have been built with a corrected SDK.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2520 | bug 2520
RESOLUTION SDK Issue
WAIVE
END
### Problem Record #475
STANDARD LSB <= 4.0
TESTSUITE xts5 < 5.1.5-20.lsb4
TEST /tset/Xlib3/cnnctnnmbr/{Test,MTest} 1
SEVERITY unreported
COMMENT These tests hang on modern distributions, with issues apparently related to xcb, although not fully resolved. they have been disabled in current builds of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2637 | bug 2637
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #476
STANDARD LSB <= 4.0
TESTSUITE printing < 4.0.5-1
TEST /convenience/cupsConvenience {14,15,17,18,35}
SEVERITY failed, unresolved
COMMENT These tests have numerous issues testing against newer versions of libcups and have been disabled in newer test suite builds.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2645 | bug 2645
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #477
STANDARD LSB <= 4.0
TESTSUITE xts5 < 5.1.5-20.lsb4
TEST /tset/Xlib12/stioerrrhn/Test {1,7}
SEVERITY failed, unresolved
MARKER REPORT: Handler not invoked (got -1 exit status
OR
MARKER child process timed out
COMMENT These tests have issues on newer distributions and have been disabled in current versions of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2651 | bug 2651
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #478
STANDARD LSB <= 4.0
TESTSUITE desktop-t2c < 4.0.3-1
TEST /glib-t2c/tests/glib_commandline_option_parser/glib_commandline_option_parser {24,25,46,47}
SEVERITY failed
MARKER The help should contain the following string "translated_Integer".
COMMENT These tests have issues if the test system locale is not either "en" or "ru". Re-packaging the test with symlinks to the other known locales let them pass with the system locale under a number of experimental tests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2682 | bug 2682
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #479
STANDARD LSB = 4.0
TESTSUITE qt4-azov < 4.0.3-1
TEST /Qt4_Input_Output-t2c/tests/QSocketNotifier/QSocketNotifier {3,6}
SEVERITY unresolved
MARKER Child process timed out
COMMENT There was an issue with these tests on some distributions. Test were corrected in new builds of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2808 | bug 2808
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #480
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-qt4 < 4.0.5-1
TEST tst_QAbstractScrollArea_scrollBarWidgets 1
| tst_QItemSelectionModel_resetModel 6
| tst_QLineEdit_redo 10
| tst_QLineEdit_undo 12
| tst_QAbstractSlider_wheelEvent 4
SEVERITY failed
MARKER Compared values are not the same
COMMENT These tests fail against Qt >= 4.6.0. Upstream tests have changed and new builds of the test suite disable the tests that are incompatible with multiple qt versions.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2814 | bug 2814
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #481
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-xml < 4.0.5-1
TEST XML_{0,1,2,6,7,8,9,10,11} 79
| XML_28 72
SEVERITY failed
MARKER File ./test/utf16bebom.xml generated an error
OR
MARKER File ./test/relaxng/tutor8_2.rng generated an error
COMMENT These tests are part of the regression (rather than the API set) set of desktop/xml and require threading support in libxml. Some current builds on Linux disable threading. Current builds of the test suite disable these tests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2748 | test 2748
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #482
STANDARD LSB <= 4.0
TESTSUITE core < 4.0.6-1
TEST /tset/LSB.os/network/gethostbyname/T.gethostbyname 2
SEVERITY failed
MARKER h_errno was set to 2, expected HOST_NOT_FOUND (1)
OR
MARKER h_errno was set to 0, expected HOST_NOT_FOUND (1)
COMMENT Behavior of the test is not completely predictable. Upstream and LSB have deprecated this function. Test is disabled in current builds of the test suite.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2835 | bug 2835
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #483
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-qt4 < 4.0.5-1
TEST tst_QListView_singleSelectionRemoveRow 12
| tst_QTextDocumentFragment_whitespaceWithFragmentMarkers 66
| tst_QDateTime_operator_eqeq 25
SEVERITY failed
MARKER Compared values are not the same
COMMENT These tests have issues with versions of Qt >= 4.6.0. Upstream has changed the tests in many cases. Current builds of the test suite disable these tests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2838 | bug 2838
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #484
STANDARD LSB <= 4.0
TESTSUITE core < 4.0.6-1
TEST /tset/PTHR.os/threadattr/pthread_attr_setstacksize/T.pthread_attr_setstacksize 2
SEVERITY failed
MARKER pthread_attr_setstacksize, expected 22, got 0
COMMENT This test incorrectly compares compile-time values with runtime values on the system under test, and there's no guarantee this will be true. Current builds of the test suite have this test return UNTESTED (disabled)
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2939 | bug 2939
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #485
STANDARD LSB <= 4.0
TESTSUITE libstdcpp < 4.1.0-8
TEST /27_io/basic_istream/extractors_arithmetic/{char,wchar_t}/13.cc 1
SEVERITY failed
MARKER Assertion `i == 0' failed.
COMMENT This test has changed in upsteam, presumably corresponding to a change in libstdc++ and the current test fails on newer distributions. Current builds of the test suite disable this test.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2943 | bug 2943
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #486
STANDARD LSB <= 4.0
TESTSUITE python < 4.0.3-1
TEST /usr/bin/python 39
SEVERITY failed
MARKER IOError: File not open for reading
COMMENT This test fails again python-2.6.5+. Upstream has changed the test slightly and updated test suites have integrated this change.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2945 | bug 2945
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #487
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-gtkvts < 4.0.5-1
TEST /tests/functions/pango_layout/pango_layout 12
SEVERITY failed, unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This test was incorrectly trying to directly access the opaque PangoLayout structure, and segfaulting against newer versions of pango. Updated tests suites rework the test to use recommended techniques to access the data.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2947 | bug 2947
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #488
STANDARD LSB <= 4.0
TESTSUITE python_app < 2.4.5-4.lsb4
TEST test_commands *
SEVERITY failed
MARKER Traceback (most recent call last):
MARKER File "/opt/lsb/appbat/lib/python2.4/test/test_commands.py", line 56, in test_getstatus
MARKER self.assert_(re.match(pat, getstatus("/."), re.VERBOSE))
MARKER AssertionError
COMMENT This test has trouble recognizing the desired output if SELinux is enabled on the test system. Current builds of python in the appbat are patched to handle this.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2948 | bug 2948
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #489
STANDARD LSB <= 4.0
TESTSUITE python_app < 2.4.5-4
TEST test_zlib
SEVERITY failed
MARKER Traceback (most recent call last):
MARKER File "/opt/lsb/appbat/lib/python2.4/test/test_zlib.py", line 72, in test_baddecompressobj
MARKER self.assertRaises(ValueError, zlib.decompressobj, 0)
MARKER AssertionError: ValueError not raised
COMMENT The zlib API changed and the appbat python does not correctly handle the new zlib. Updated builds are patched to handle this.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2952 | bug 2952
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #490
STANDARD LSB <= 4.0
TESTSUITE perl < 4.0.8-1
TEST ../ext/B/t/b.t 209
| ../ext/B/t/deparse.t 212
| ../ext/B/t/terse.t 224
| ../ext/DynaLoader/t/XSLoader.t 257
| ../ext/attrs/t/attrs.t 208
| ../lib/overload.t 667
| base/lex.t
| run/fresh_perl.t
| op/attrs.t
| op/caller.t
| op/cproto.t
| op/index.t
| op/magic.t
| op/pat.t
| op/sprintf.t
| op/sprintf2.t
| op/stash.t
| op/sysio.t
| op/vec.t
| ../ext/Devel/Peek/t/Peek.t
| ../lib/Config.t
| ../lib/strict.t
SEVERITY failed, unreported
MARKER FAILED tests 6-57 Failed 52/57 tests, 8.77% okay
OR
MARKER FAILED test 8 Failed 1/54 tests, 98.15% okay
OR
MARKER FAILED test 16 Failed 1/16 tests, 93.75% okay
OR
MARKER FAILED tests 6, 9, 12, 15, 18 Failed 5/20 tests, 75.00% okay
OR
MARKER FAILED test 237 Failed 1/556 tests, 99.82% okay
OR
MARKER The test case returned no result
COMMENT These tests are incompatible with perl-5.12+. Current versions of the test suite have either reworked or disabled the failing subtests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2953 | bug 2953
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3008 | bug 3008
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #491
STANDARD LSB <= 4.0
TESTSUITE desktop-t2c < 4.0.3-1
TEST /glib-t2c/tests/glib_threads/glib_threads {1,2,3}
SEVERITY failed
MARKER g_thread_create_full: thread priority was not set.
COMMENT There was a race condition in this test, only found under certain conditions. Current builds of the test suite have corrected this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2997 | bug 2997
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #492
STANDARD LSB <= 4.0
TESTSUITE desktop < 4.0.5-1 | desktop-qt4 < 4.0.5-1
TEST tst_QDate_isLeapYear 17
| tst_QDoubleSpinBox_editingFinished 15
SEVERITY failed
MARKER Compared values are not the same
COMMENT These tests fail against Qt >= 4.6.2+. Upstream tests have changed and new builds of the test suite disable the tests that are incompatible with multiple qt versions.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3017 | bug 3017
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3075 | bug 3075
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #493
STANDARD LSB <= 4.0
TESTSUITE python < 4.0.3-1
TEST /usr/bin/python 9
SEVERITY failed
COMMENT Both Red Hat and Suse removed the audioop module from their python builds due to security issues. The workgroup decided that it should have never been included in LSB and the requirement for this module has been removed. Current builds of the test suite no longer test for this module.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3019 | bug 3019
RESOLUTION Specification Issue
WAIVE
END
### Problem Record #494
STANDARD LSB <= 4.0
TESTSUITE python < 4.0.3-1
TEST /usr/bin/python 4
| /usr/bin/python 27
| /usr/bin/python 43
| /usr/bin/python 44
| /usr/bin/python 46
| /usr/bin/python 58
| /usr/bin/python 88
| /usr/bin/python 91
| /usr/bin/python 95
| /usr/bin/python 100
| /usr/bin/python 101
| /usr/bin/python 105
SEVERITY failed
COMMENT These tests are incompatible with python-2.7+. Current builds of the test suite have updated the tests or dropped subtests to handle 2.7.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3024 | bug 3024
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #495
STANDARD LSB <= 4.0
TESTSUITE core < 4.0.6-1
TEST /tset/ANSI.os/streamio/setvbuf_X/T.setvbuf_X {3,8}
SEVERITY failed
MARKER buffer buf1 contained wrong character (b) at position 0
OR
MARKER read returned wrong character (b) at position 0
COMMENT These 2 tests are too strict, treating "may" in the setvbuf() specification as if it was "shall". Current builds of the test suite disable these 2 subtests.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3028 | bug 3028
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #496
STANDARD LSB <= 4.0
TESTSUITE desktop-t2c < 4.0.3-1
TEST /glib-t2c/tests/glib_threads/glib_threads {26,27}
SEVERITY unresolved
MARKER Abnormal child process termination. errno: 22
COMMENT Finalization of these tests was incorrect, and they segfault on a system, which verifies mutex state when a mutex is freed. Current versions of the test suite correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3042 | bug 3042
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #497
STANDARD LSB <= 4.0
TESTSUITE perl < 4.0.8-1
TEST ../ext/PerlIO/t/scalar.t
SEVERITY failed
MARKER Failed 27/51 tests, 47.06% okay
COMMENT This test fails against perl-5.12.2. Current builds of the test suite correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3043 | bug 3043
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #498
STANDARD LSB <= 4.0
TESTSUITE perl < 4.0.8-1
TEST ../lib/ExtUtils/t/00compile.t
SEVERITY failed
MARKER Failed 15/30 tests, 50.00% okay
COMMENT This test fails if Test::Pod is installed. Current versions of the test suite disable tests that attempt to use the optional Test::Pod.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3066 | bug 3066
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #499
STANDARD LSB <= 4.0
TESTSUITE perl < 4.0.8-1
TEST op/sprintf.t 166
SEVERITY unreported
COMMENT This test fails on some systems due to the lack of the perl-version package. As version.pm is not required by LSB, current builds of the test suite disable subtests that need this.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3112 | bug 3112
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #500
STANDARD LSB <= 4.0
TESTSUITE python < 4.0.3-1
TEST /usr/bin/python 77
SEVERITY failed
MARKER AssertionError: TypeError not raised
COMMENT This test (test_random.py) fails against python-2.7.1. Current versions of the test suite follow upstream and remove the subtest that is not portable to different versions of python.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3115 | bug 3115
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #501
STANDARD LSB <= 4.0
TESTSUITE perl < 4.0.8-1
TEST ../ext/Storable/t/malice.t
SEVERITY failed
MARKER Failed 24/404 tests, 94.06% okay
COMMENT This test fails against newer versions of Storable. Current builds of the test suite disable the subtests that don't work across different versions.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3154 | bug 3154
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #502
STANDARD LSB
TESTSUITE core >= 4.1.0-1 & < 4.1.7-1 | core < 4.0.6-1
TEST /tset/LSB.fhs/root/lib/lib-tc 4
SEVERITY failed
MARKER The /lib directory contains the shared dynamic linker /lib/libc.so.*
COMMENT This test checks for the existence of libc.so* in /lib or /lib64. Some distributions are moving things to %{arch}-linux-gnu for multi-arch support. It would appear the test is more strict than the FHS specification has been reworked.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3225 | bug 3225
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #503
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/pango_layout/pango_layout 13
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This issue would appear to be similar to a previous test bug in pango_layout, but is still being researched.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3224 | bug 3224
RESOLUTION Known Problem
END
### Problem Record #504
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GArray/GArray 7
SEVERITY failed
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This test fails against newer versions of glib2 (first observed on OpenSuse-11.5). Issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3223 | bug 3223
RESOLUTION Known Problem
END
### Problem Record #505
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/Resource_Files/Resource_Files 34
SEVERITY unresolved
MARKER unexpected signal 6 (SIGABRT) received
COMMENT This test was observed to fail on Opensuse-11.5. Issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3222 | bug 3222
RESOLUTION Known Problem
END
### Problem Record #506
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/Selections/Selections {33,34}
SEVERITY failed
MARKER global_iter = 0, should be 1
COMMENT This failure is thought to appear with certain versions of GTK, and may also be driven by locale settings. Final resolution of the issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2849 | bug 2849
RESOLUTION Known Problem
END
### Problem Record #507
STANDARD LSB
TESTSUITE desktop | desktop-qt4
TEST tst_QHash_keys_values_uniqueKeys 19
SEVERITY failed
COMMENT This test fails against Qt >= 4.6.0. Upstream tests have changed and new builds of the test suite disable the tests that are incompatible with multiple qt versions. See:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3566 | bug 3566
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #508
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.fhs/usr/lib/lib-tc 2
SEVERITY failed
MARKER stderr:lsb_issymlink: lstat (/usr/lib/sendmail) returned -1, errno= 2, (No such file or directory)
COMMENT The Ubuntu lsb-invalid-mta package provides /usr/sbin/sendmail but not the symbolic link /usr/lib/sendmail. This bug has been filed upstream with the vendor on 2011-01-05:
LINK https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/697632 | bug 697632
RESOLUTION Distribution Problem
END
### Problem Record #509
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/dataform/tar/T.tar 9
SEVERITY failed
MARKER "devmajor" field "" is not a zero-filled octal number
MARKER "devminor" field "" is not a zero-filled octal number
COMMENT The pax program in Debian and Ubuntu incorrectly omits the devmajor/devminor when writing archives in the ustar format. It has been fixed in Debian and a bug has been filed with Ubuntu to correct the issue on 2011-04-21:
LINK https://bugs.launchpad.net/ubuntu/+source/pax/+bug/768260 | bug 768260
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2743 | bug 2743
COMMENT Update: The patch has been now dropped in Debian/Ubuntu and there is some question as to whether the spec/test are correct.
RESOLUTION Known Problem
END
### Problem Record #510
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/files/dev_tty/T.dev_tty 1
SEVERITY failed
MARKER read() on VSX_TERMIOS_LOOP failed - errno 4 (EINTR)
COMMENT This may be a transient, timing related issue. It was observed on a machine running 4 vms at the time, all running the test suite. Failure was not repeatable running the test manually. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3228 | bug 3228
RESOLUTION Known Problem
END
### Problem Record #511
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/files/mkfifo/T.mkfifo 16
SEVERITY unresolved
MARKER deletion reason: could not make directory mkfifo-d.16
COMMENT It is possible that a previous test run can leave files behind that will prevent a successful run of this test later. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3229 | bug 3229
RESOLUTION Known Problem
END
### Problem Record #512
STANDARD LSB
TESTSUITE qt4-azov < 4.0.3-2 | qt4-azov >= 4.1.0-1 & < 4.1.2-1
TEST /Qt4_Input_Output-t2c/tests/QFileInfo/QFileInfo 45
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0==QString::null'
COMMENT This test has been observed to fail for Qt4 4.7.0+. Updated tests correct the issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3034 | bug 3034
RESOLUTION Known Problem
WAIVE
END
### Problem Record #513
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Internationalization-t2c/tests/QLocale/QLocale 28
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == 1234.56'
COMMENT This issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3125 | bug 3125
RESOLUTION Known Problem
END
### Problem Record #514
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Miscellaneous-t2c/tests/Qt4_Miscellaneous/Qt4_Miscellaneous 1
SEVERITY unresolved
MARKER Child process was terminated by signal 6
MARKER Abnormal child process termination. errno: 22
COMMENT The test in this case assumes the internal data format for a QKeySequence in a QDataStream, which is explicitly documented to be opaque. See the LSB bug for more details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3134 | bug 3134
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #515
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_SQL-t2c/tests/QSqlTableModel/QSqlTableModel 46
SEVERITY failed
MARKER Target interface(s):
MARKER QSqlTableModel::deleteRowFromTable(int)
MARKER CONSTRAINT FOR RETURN FAILED: '($0 == true)'
COMMENT The deleteRowFromTable method is not intended to be called except by low-level code. The test does not implement the proper checking to be able to delete rows safely, causing this problem.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2782 | LSB bug 2782
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #516
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_OpenGL-t2c/tests/QGLFramebufferObject/QGLFramebufferObject *
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT These seem to be transient failures. Possibly related to memory leaks with Xvfb. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2829 | bug 2829
RESOLUTION Known Problem
END
### Problem Record #517
STANDARD LSB
TESTSUITE olver
TEST /olver/other/other/tests/others *
SEVERITY failed
MARKER parser error
COMMENT There seems to be some issue with collating the report data for these tests on some systems, with failure ranging from a handful to double-digits. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3091 | bug 3091
RESOLUTION Known Problem
END
### Problem Record #518
TESTSUITE desktop-t2c < 4.0.5-1 | desktop-t2c >= 4.1.0-1 & < 4.1.2-1
TEST /fontconfig-t2c/tests/FcConfig/FcConfig 26
SEVERITY failed
MARKER The function didn't return the most close matching font
COMMENT This issue appears to be unique to Mandriva (and now Mageia). A bug has been filed upstream. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2854 | bug 2854
LINK https://bugs.freedesktop.org/show_bug.cgi?id=25670 | upstream bug
COMMENT Update: The test has been modified slightly to handle the particular font situation on these systems.
RESOLUTION Known Problem
WAIVE
END
### Problem Record #519
STANDARD LSB
TESTSUITE desktop-t2c
TEST /freetype-t2c/tests/truetype_tables/truetype_tables 2
SEVERITY failed
MARKER This function is expected to return a pointer to given TT_MaxProfile table, but it is NOT
COMMENT This issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3153 | bug 3153
RESOLUTION Known Problem
WAIVE
END
### Problem Record #520
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 39
SEVERITY failed
MARKER g_type_add_class_cache_func: all classes were not routed through the same GTypeClassCacheFunc chain
COMMENT This issue is still under investigation
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3184 | bug 3184
RESOLUTION Known Problem
WAIVE
END
### Problem Record #521
STANDARD LSB
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_relation/AtkObject_relation 2
SEVERITY failed
MARKER atk_object_add_relationship
MARKER When there are no such relationship in the object relationset, function should add relationship.
MARKER Returns TRUE if the relationship is added.
COMMENT This appears to be a regression introduced by a patch submitted upstream for another issue revealed in testing. Upstream is now aware of the issue, but the proposed fix may include an API change.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3189 | bug 3189
LINK https://bugzilla.gnome.org/show_bug.cgi?id=578602
LINK https://bugzilla.gnome.org/show_bug.cgi?id=672869
RESOLUTION Known Problem
WAIVE
END
### Problem Record #522
STANDARD LSB
TESTSUITE desktop-t2c
TEST /atk-t2c/tests/AtkObject_relation/AtkObject_relation {5,6}
SEVERITY unresolved
MARKER atk_object_remove_relationship
MARKER Cannot add relationship to the object.
MARKER Error: Smth wrong in test purpose.
COMMENT This appears to be a regression introduced by a patch submitted upstream for another issue revealed in testing. Upstream is now aware of the issue, but the proposed fix may include an API change.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3189 | bug 3189
LINK https://bugzilla.gnome.org/show_bug.cgi?id=578602
LINK https://bugzilla.gnome.org/show_bug.cgi?id=672869
RESOLUTION Known Problem
WAIVE
END
### Problem Record #523
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/files/fpathconf/T.fpathconf {15,16}
| /tset/POSIX.os/files/pathconf/T.pathconf 15
SEVERITY failed
MARKER fpathconf(fd, _PC_PIPE_BUF) on "fpathconf-t.15" did not return same value as pathconf("fpathconf-t.15", _PC_PIPE_BUF)
MARKER expected: 4096, observed: 65536
OR
MARKER fpathconf(fd, _PC_PIPE_BUF) on "." did not return same value as fpathconf(fd, _PC_PIPE_BUF) on "fpathconf-t.16"
MARKER expected: 65536, observed: 4096
OR
MARKER pathconf(".", _PC_PIPE_BUF) did not return same value as pathconf("pathconf-t.15", _PC_PIPE_BUF)
MARKER expected: 65536, observed: 4096
COMMENT This is a problem with newer versions of glibc up to and including 2.16, and requires a patch to glibc for those versions. Test 15 was fixed on earlier versions.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3078 | bug 3078
LINK http://sourceware.org/bugzilla/show_bug.cgi?id=12723 | upstream bug report
LINK http://sourceware.org/git/?p=glibc.git;a=commit;h=6e04cbbe79f5965809fdbf1f28d7ae8b4af74d31 | test 15 fix
LINK http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=adbb8027be47b3295367019b2f45863ea3d6c727 | test 16 fix
RESOLUTION Upstream Problem
END
### Problem Record #524
STANDARD LSB
TESTSUITE qt4-azov < 4.1.3
TEST /Qt4_Menus-t2c/tests/QMenuBar/QMenuBar 30
SEVERITY failed
MARKER Target interface(s):
MARKER QMenuBar::actionAt(QPoint const&) const
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == NULL'
COMMENT This is likely caused by differences in the default theme on the test system.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3124 | bug 3124
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #525
STANDARD LSB
TESTSUITE qt4-azov < 4.1.3
TEST /Qt4_Menus-t2c/tests/QMenuBar/QMenuBar 49
SEVERITY failed
MARKER Target interface(s):
MARKER QMenuBar::activeAction() const
MARKER CONSTRAINT FOR RETURN FAILED: '$0 != NULL'
COMMENT In this test, activeAction() is tested without explicitly setting an active action; thus, a NULL return value can't be ruled out. See the LSB bug for more details:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3067 | bug 3067
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #526
STANDARD LSB
TESTSUITE qt3-azov
TEST /Qt3_Object_Model-t2c/tests/QMetaObject/QMetaObject {3,15}
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This issue is still under investigation
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3231 | bug 3231
RESOLUTION Known Problem
END
### Problem Record #527
STANDARD LSB
TESTSUITE olver
TEST /olver/fs/symlink/tests/readlink_spec 1
SEVERITY failed
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {readlink.06.02} error not met because its predicate (file!=((void*) 0) && file->kind!=SymbolicLinkFile) is false while error code EINVAL is set
OR
MARKER POSTCONDITION_FAILED
MARKER error not met because its predicate
COMMENT This issue is still being investigated
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3232 | bug 3232
RESOLUTION Known Problem
END
### Problem Record #528
STANDARD LSB
TESTSUITE olver
TEST /olver/util/compress/tests/gzputc_spec {1,844}
SEVERITY failed
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {gzputc.02} On success, shall return the value written
OR
MARKER Registered bug: bug844
COMMENT According to LSB, the gzputc() function shall write the single character c, converted from integer to unsigned character. On success, gzputc() shall return the value written, but it returns
COMMENT initial argument instead.
COMMENT Additional information about this bug may be found at:
LINK http://linuxtesting.org/results/report?num=S0844 | LinuxTesting report
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3057 | LSB bug 3057
RESOLUTION Upstream library issue
END
### Problem Record #529
STANDARD LSB
TESTSUITE core < 4.0.7-1 | core >= 4.1.0-1 & < 4.1.10-2
TEST /tset/POSIX.os/procprim/sched_setscheduler/T.sched_setscheduler {1,2}
SEVERITY failed
MARKER sched_setscheduler() returned -1
MARKER errno was set to 1
COMMENT Some modern systems real time group scheduling which was preventing these tests from being able to use SCHED_RT. Updated tests correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3116 | bug 3116
RESOLUTION Known Problem
WAIVE
END
### Problem Record #530
STANDARD LSB
TESTSUITE core < 4.0.7-1 | core >= 4.1.0-1 & < 4.1.10-2
TEST /tset/LSB.os/procenv/nice_X/T.nice_X 1
SEVERITY failed
MARKER sched_setscheduler failed for SCHED_RR with priority
COMMENT Some modern systems real time group scheduling which was preventing these tests from being able to use SCHED_RT. Updated tests correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3116 | bug 3116
RESOLUTION Known Problem
WAIVE
END
### Problem Record #531
STANDARD LSB
TESTSUITE core < 4.0.7-1 | core >= 4.1.0-1 & < 4.1.10-2
TEST /tset/PTHR.os/cfuncs/asctime_r/T.asctime_r 1
| /tset/PTHR.os/cfuncs/ctime_r/T.ctime_r 1
| /tset/PTHR.os/cfuncs/getc_unlocked/T.getc_unlocked {1,2}
| /tset/PTHR.os/cfuncs/getchar_unlocked/T.getchar_unlocked 2
| /tset/PTHR.os/cfuncs/gmtime_r/T.gmtime_r {1,2}
| /tset/PTHR.os/cfuncs/localtime_r/T.localtime_r 1
| /tset/PTHR.os/cfuncs/rand_r/T.rand_r {1,3}
| /tset/PTHR.os/cfuncs/strtok_r/T.strtok_r {1,2,3}
| /tset/PTHR.os/files/readdir_r/T.readdir_r {1,2,3,4}
| /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r {1,2}
| /tset/PTHR.os/procenv/ttyname_r/T.ttyname_r {1,2,3,4}
| /tset/PTHR.os/sysdb/getgrgid_r/T.getgrgid_r {1,3}
| /tset/PTHR.os/sysdb/getgrnam_r/T.getgrnam_r {1,2,3}
| /tset/PTHR.os/sysdb/getpwnam_r/T.getpwnam_r {1,2,3}
| /tset/PTHR.os/sysdb/getpwuid_r/T.getpwuid_r {1,3}
SEVERITY unresolved, unreported, testsuite_error
MARKER Error reported by the test suite
OR
MARKER vsth_newthread, expected 0, got 1
COMMENT Some modern systems real time group scheduling which was preventing these tests from being able to use SCHED_RT. Updated tests correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3116 | bug 3116
RESOLUTION Known Problem
WAIVE
END
### Problem Record #532
STANDARD LSB
TESTSUITE olver
TEST /olver/ncurses/terminal/tests/initscr_spec 1
SEVERITY failed
MARKER Segmentation fault: Invalid memory address
COMMENT Upstream ncurses defines the 'chtype' type as 'unsigned' without specifying int vs. long, but the LSB specification requires it to be 'long'. This causes a problem on some 64-bit architectures. The problem can be fixed in some cases by building ncurses using the --with-chtype=long configure flag.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3106 | LSB bug 3106
LINK https://bugs.mageia.org/show_bug.cgi?id=7235 | Mageia bug 7235
RESOLUTION Known Problem
END
### Problem Record #533
STANDARD LSB
TESTSUITE olver < 4.0.2-1 | olver >= 4.1.0-1 & < 4.1.2-4
TEST /olver/other/other/tests/others {1,2}
SEVERITY failed
MARKER setlocale_spec(context, SUT_LC_ALL, _CS("Olver_Locale")) != NULL failed
OR
MARKER Unable to change current locale
COMMENT These failures are due to the test locale not being setup properly. More recent versions of the test suite setup the locale for each test run.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2871 | bug 2871
RESOLUTION Known Problem
WAIVE
END
### Problem Record #534
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/libdl/dlerror/T.dlerror {1,2}
SEVERITY unresolved
MARKER dlclose() did not return non-zero
COMMENT This issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3499 | bug 3499
RESOLUTION Known Problem
WAIVE
END
### Problem Record #535
STANDARD LSB
TESTSUITE olver
TEST /olver/locale/textdomain/tests/gettext_caller_spec 1
SEVERITY failed
MARKER Requirement failed: {gettext.01}
COMMENT This issue is still under investigation
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3234 | bug 3234
RESOLUTION Known Problem
END
### Problem Record #536
STANDARD LSB
TESTSUITE xts5
TEST /tset/Xlib3/stclsdwnmd/Test 3
SEVERITY failed
MARKER REPORT: save-set window was not mapped after save-set processing
COMMENT This issue has only been seen on a couple of occasions and is believed to be some sort of transient/timing related issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=2964 | bug 2964
RESOLUTION Known Problem
END
### Problem Record #537
STANDARD LSB
TESTSUITE xts5
TEST /tset/Xlib3/clsdsply/Test 14
SEVERITY failed
MARKER REPORT: Got error Success instead of BadGC
COMMENT This seems to be a transient issue, recorded only a few times in internal distribution testing. More details are in bugzilla. Re-open the bug if warranted.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3032 | bug 3032
RESOLUTION Known Problem
END
### Problem Record #538
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Text-t2c/tests/QTextDocument/QTextDocument 31
SEVERITY failed
MARKER QTextDocument::markContentsDirty(int, int)
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This appears to be a regression in qt-4.7.1, corrected in qt-4.7.2. Update the qt4 version or patch to correct this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3135 | LSB bug 3135
LINK http://bugreports.qt.nokia.com/browse/QTBUG-15777 | Qt bug 15777
RESOLUTION Upstream Problem
END
### Problem Record #539
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkTreeSortable/GtkTreeSortable {15..18}
SEVERITY failed
COMMENT This is appearing on some distributions using gtk2-2.24.4. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3238 | bug 3238
RESOLUTION Known Problem
END
### Problem Record #540
STANDARD LSB
TESTSUITE libchk
TEST libQtOpenGL.so.4
SEVERITY testsuite_warning
MARKER Test Case block wasn't closed
COMMENT This appears to be an issue with libQtOpenGL on Ubuntu
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3233 | LSB bug 3233
LINK https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/785318 | Ubuntu bug
RESOLUTION Distribution Problem
END
### Problem Record #541
STANDARD LSB
TESTSUITE perl < 4.0.9 | perl >= 4.1.0 & < 4.1.3
TEST ../ext/IPC/SysV/t/ipcsysv.t 304
SEVERITY failed
MARKER The test case returned no result
COMMENT This test can fail if run when the system is first booted. Updated versions of the test have corrected this issue.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3249 | bug 3249
RESOLUTION Known Problem
WAIVE
END
### Problem Record #542
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/devclass/c_iflag/T.c_iflag {6..9}
| /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr {1,2}
SEVERITY failed
MARKER read() returned 1, expected 0
OR
MARKER read() returned 1, expected 3
MARKER when ISTRIP flag was clear
OR
MARKER read() returned 1, expected 3
MARKER when ISTRIP flag was set
OR
MARKER read 0377, expected 0
OR
MARKER (c_cflag & PARENB) was not set
MARKER (c_cflag & CSIZE) was not set to CS7
COMMENT This appears to be caused by a kernel bug introduced recently. Red Hat has provided a glibc patch to cover the kernel bug.
LINK http://pkgs.fedoraproject.org/cgit/glibc.git/tree/glibc-fedora-linux-tcsetattr.patch | Red Hat patch,
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3033 | bug 3033
RESOLUTION Upstream bug
END
### Problem Record #543
STANDARD LSB
TESTSUITE printing
TEST /testgs/testgs {2,6,8,10}
SEVERITY failed
MARKER The gs command provides support for the cups device.
MARKER exit code 1 returned, expected 0
OR
MARKER The gs command provides support for the opvp device.
MARKER exit code 1 returned, expected 0
OR
MARKER The gs command provides support for the pxlmono device.
MARKER exit code 1 returned, expected 0
OR
MARKER The gs command provides support for the pxlcolor device.
MARKER exit code 1 returned, expected 0
COMMENT This appears to be an issue with the way the test collects the list of supported drivers, on some systems. The issue is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3270 | bug 3270
RESOLUTION Known Problem
END
### Problem Record #544
STANDARD LSB
TESTSUITE perl
TEST ../lib/Unicode/UCD.t 801
SEVERITY failed
MARKER FAILED test 156 Failed 1/185 tests, 99.46% okay
COMMENT This failure is appearing on only the 32bit version of OpenSuse factory at present. IT is still under investigation.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3269 | bug 3269
RESOLUTION Known Problem
END
### Problem Record #545
#STANDARD LSB
#TESTSUITE printing
#TEST /testfoomaticrip/testfoomaticrip 2
# SEVERITY unreported
# MARKER Reference III.8.2
# MARKER foomatic-rip inserts standard PPD options correctly into the PostScript data stream.
#COMMENT This issue is still under investigation
#LINK http://bugs.linuxbase.org/show_bug.cgi?id=3272 | bug 3272
#RESOLUTION Known Problem
#END
### Problem Record #546
STANDARD LSB
TESTSUITE qt4-azov < 4.1.3
TEST /Qt4_Widgets-t2c/tests/QListView/QListView 59
SEVERITY failed
MARKER Target interface(s):
MARKER QListView::isRowHidden(int) const
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == true'
MARKER Requirement failed:
MARKER {isRowHidden.01}
MARKER <<< REQ NOT FOUND >>>
COMMENT This test checks the behavior of a QListView without an underlying model object. Although legal, it's not clear from the documentation that the behavior is defined in this case, and experimentation shows that the behavior is inconsistent without an underlying model. The test should be fixed to provide a model to refer to for this test. See the LSB bug for more information:
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3275 | bug 3275
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #547
STANDARD LSB
TESTSUITE qt4-azov < 4.1.3
TEST /Qt4_Paint_Device-t2c/tests/QPixmap/QPixmap 67
SEVERITY failed
MARKER Target interface(s):
MARKER QPixmap::handle() const
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 > 0'
MARKER Requirement failed:
MARKER {handle.01}
MARKER <<< REQ NOT FOUND >>>
COMMENT Qt 4.8 and later require explicit tying to X11 before allowing this function. Will be deprecated in the next version of the LSB.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3274 | bug 3274
RESOLUTION Upstream change
WAIVE
END
### Problem Record #548
STANDARD LSB
TESTSUITE qt4-azov < 4.0.4 | qt4-azov 4.1.0
TEST /Qt4_Core_Functions-t2c/tests/Qt4_Core_Functions/Qt4_Core_Functions 33
SEVERITY unresolved
MARKER Child process was terminated by signal 6.
MARKER Abnormal child process termination. errno: 22.
COMMENT The implementation has changed as of Qt-4.8. Updated builds of the test suite have this test disabled.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3273 | bug 3273
RESOLUTION Known Problem
WAIVE
END
### Problem Record #549
#STANDARD LSB
#TESTSUITE desktop | desktop-qt4
#TEST -g tst_QHostAddress_constructor_QString {1,2}
# SEVERITY failed
# MARKER Compared values are not the same Actual (hostAddr.toString()): 1080::8:800:200C:417A Expected ("resAddr"): 1080:0:0:0:8:800:200C:417A
# OR
# MARKER Compared values are not the same
#COMMENT This issue is still under investigation. Appears to occur with qt-4.8.0
#LINK http://bugs.linuxbase.org/show_bug.cgi?id=3271 | bug 3271
#RESOLUTION Known Problem
#END
### Problem Record #550
#STANDARD LSB
#TESTSUITE desktop | desktop-qt4
#TEST tst_QHostAddress_scopeId 6
# SEVERITY failed
# MARKER QMetaObject::invokeMethod: No such method tst_QHostAddress::scopeId_data()
# MARKER Compared values are not the same Actual (address.toString().toLower()): fe80::2e0:4cff:fefb:662a%eth0 Expected (QString("fe80:0:0:0:2e0:4cff:fefb:662a%eth0")): fe80:0:0:0:2e0:4cff:fefb:662a%eth0
#COMMENT This issue is still under investigation. It appears to occur with qt-4.8.0
#LINK http://bugs.linuxbase.org/show_bug.cgi?id=3271 | bug 3271
#RESOLUTION Known Problem
#END
### Problem Record #551
STANDARD LSB
TESTSUITE printing < 4.0.6-1 | printing >= 4.1.0
TEST /convenience/cupsConvenience {10,19}
SEVERITY failed
MARKER When cupsAddDest is called to add a destination to the list of destinations, the function returns the new number of destinations
MARKER cupsAddDest returned 2, expected 1
OR
MARKER When cupsGetDests2 is called to get the list of destinations from the default server, the function returns the number of destinations
MARKER cupsGetDests2 returned 0, expected 1
OR
MARKER unexpected signal 11 (SIGSEGV) received
TESTCASE /convenience/cupsConvenience {1,8,9,11}
SEVERITY unresolved,unreported
MARKER unexpected signal 15 (SIGTERM) received
OR
MARKER cupsPrintFile returned 0, expected a positive value
TESTCASE /convenience/cupsConvenience {2,3,4,5,6,7}
SEVERITY failed
MARKER cupsGetDefault2 returned NULL, expected a value
OR
MARKER cupsGetPPD returned NULL, expected a filename
OR
MARKER cupsGetPPD2 returned NULL, expected a filename
OR
MARKER cupsPrintFile returned 0, expected a positive value
OR
MARKER cupsPrintFile2 returned 0, expected a value
OR
MARKER cupsPrintFiles returned 0, expected a positive value
COMMENT This issue appear testing against cups >= 1.5. There are some problems in attempting to use an alternate port for the test cupsd, as well as test issues with this version of cups.
COMMENT Updated tests correct the problem.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3256 | bug 3256
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3440 | bug 3440
COMMENT While the fix worked for cups-1.5.x, the issue has re-appeared for cups-1.6.x.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3629 | bug 3629
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #552
STANDARD LSB
TESTSUITE perl
TEST all/tst_perlModPresent.pl 1
SEVERITY failed
MARKER 190
OR
MARKER test 190 'use Pod::Plainer;' failed
COMMENT This is due to a missing Pod::Plainer perl module. While deprecated in LSB-4.1, it is still required by LSB until the deprecation cycle runs it's course.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3276 | bug 3276
RESOLUTION Distribution Problem
END
### Problem Record #553
STANDARD LSB
TESTSUITE perl
TEST pod/plainer.t 815
| pod/plainer.t 812
SEVERITY unreported
MARKER The test case returned no result
COMMENT This is due to a missing Pod::Plainer perl module. While deprecated in LSB-4.1, it is still required by LSB until the deprecation cycle runs it's course.
LINK http://bugs.linuxbase.org/show_bug.cgi?id=3276 | bug 3276
RESOLUTION Distribution Problem
END
### Problem Record #554
STANDARD LSB <= 4.1
TESTSUITE qt3-azov
TEST /Normal_Test-t2c/tests/QGLContext/QGLContext 1
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This issue has been reported by an ISV trying to certify. It does not seem to be common.
LINK http://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3041 | Bug 3041
RESOLUTION Known Problem
END
### Problem Record #555
STANDARD LSB <= 4.1
TESTSUITE desktop | desktop-qt4
TEST -g tst_QHostAddress_constructor_QString 1
| tst_QHostAddress_setAddress_QString 2
| tst_QHostAddress_scopeId 6
SEVERITY failed
MARKER Compared values are not the same Actual (hostAddr.toString()):
MARKER 1080::8:800:200C:417A Expected ("resAddr"): 1080:0:0:0:8:800:200C:417A
OR
MARKER Compared values are not the same Actual (hostAddr.toString()):
MARKER 1080::8:800:200C:417A Expected ("resAddr"): 1080:0:0:0:8:800:200C:417A
OR
MARKER Compared values are not the same Actual (hostAddr.toString()): 1080::8:800:200C:417A Expected ("resAddr"): 1080:0:0:0:8:800:200C:417A
OR
MARKER Compared values are not the same Actual (address.toString().toLower()):
MARKER fe80::2e0:4cff:fefb:662a%eth0 Expected
MARKER (QString("fe80:0:0:0:2e0:4cff:fefb:662a%eth0")):
MARKER fe80:0:0:0:2e0:4cff:fefb:662a%eth0
COMMENT The Qt4 behavior (and upstream tests) has been changed to comply with RFC-5952 for IPv6 address format. The tests have been disabled in more recent builds of the test suite.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3271 | Bug 3271
RESOLUTION Known Problem
WAIVE
END
### Problem Record #556
STANDARD LSB
TESTSUITE perl
TEST ../lib/Locale/Codes/t/constants.t 542
| ../lib/Locale/Codes/t/languages.t 545
| ../lib/Locale/Codes/t/constants.t 539
| ../lib/Locale/Codes/t/languages.t 542
SEVERITY unreported
MARKER The test case returned no result
COMMENT Support for Locale::Constants, Locale::Country, Locale::Currency, Locale::Language, Locale::Maketext
COMMENT and Locale::Script has been re-organized in more recent Perl, and some distributions have followed suit. In particular "use Locale::Contants" will fail on these systems. How to handle this in LSB is still undetermined.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3282 | Bug 3282
RESOLUTION Known Problem
WAIVE
END
### Problem Record #557
STANDARD LSB
TESTSUITE olver
TEST /olver/other/other/tests/others *
SEVERITY failed
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {} columns number check
OR
MARKER SERIALIZATION_FAILED
OR
MARKER Serialization Failed
OR
MARKER POSTCONDITION_FAILED
MARKER Test has been terminated by signal SIGTERM
OR
MARKER (structural)
COMMENT This issue is showing up on more recent distributions. The problem is still under analysis.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3285 | Bug 3285
RESOLUTION Known Problem
END
### Problem Record #558
STANDARD LSB
TESTSUITE python < 4.0.4-1 | python >= 4.1.1-2 & < 4.1.2-1
TEST /usr/bin/python 99
SEVERITY failed
MARKER Traceback (most recent call last):
MARKER File "/opt/lsb/test/python/Lib25/test/test_unicode.py", line 541, in
MARKER test_codecs_utf7
MARKER self.assertRaises(UnicodeError, unicode, '+3ADYAA-', 'utf-7')
MARKER AssertionError: UnicodeError not raised
COMMENT This subtest has been removed in current versions of the python test suite.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3286 | Bug 3286
RESOLUTION Known Problem
WAIVE
END
### Problem Record #559
TESTSUITE cpp-t2c
TEST -g /libstdcxx-t2c/tests/num_get_get/num_get_get {1,5,19,20}
SEVERITY failed
MARKER Expected that after call of the function value will be 12345, but it is 1.
MARKER Function should modify value in the same manner as do_F-function.
OR
MARKER Expected that after call of the function value will be 1(true), but it is
MARKER 0(false).
MARKER Function should modify value in the same manner as do_F-function.
COMMENT This appears to be driven by upstream changes in libstdc++. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3343 | bug 3343
RESOLUTION Known Problem
END
### Problem Record #560
STANDARD LSB
TESTSUITE core < 4.1.15
TEST /tset/POSIX.os/procprim/sigconcept/T.sigconcept 31
| /tset/ANSI.os/streamio/scanf/T.scanf 51
SEVERITY testsuite_error, unreported, testsuite_error
MARKER system 0, errno = 9 (EBADF): (dresfile.c, 932) write failed on temp result file
COMMENT This is caused by a bug in the TET test framework in how it handles temporary result files.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3345 | Bug 3345 (original test-core bug)
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3789 | Bug 3789 (bug in lsb-tet3-lite)
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #561
STANDARD LSB
TESTSUITE xts5
TEST -g /tset/Xlib16/rmptrsrc/Test {2,3}
SEVERITY failed
MARKER REPORT: XrmPutResource did not update the database contents as expected.
OR
MARKER REPORT: XrmPutResource did not add to the database as expected.
COMMENT This failure is appearing on some leading edge distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3386 | Bug 3386
RESOLUTION Known Problem
END
### Problem Record #562
STANDARD LSB
TESTSUITE xts5
TEST /tset/Xlib17/gtdflt/Test 3
SEVERITY failed
MARKER REPORT: XGetDefault() returned NULL
COMMENT While this failure was seen on some test runs under VMWare some years ago, it is now appearing again on more recent distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3387 | Bug 3387
RESOLUTION Known Problem
END
### Problem Record #563
STANDARD LSB
TESTSUITE olver
TEST -g /olver/ncurses/char/tests/addch_spec {1..4}
| /olver/ncurses/char/tests/insch_spec 1
| /olver/ncurses/char/tests/inch_spec {1,2}
| /olver/ncurses/chgat/tests/chgat_spec 1
| /olver/ncurses/chstr/tests/inchstr_spec {1,2}
| /olver/ncurses/chstr/tests/addchstr_spec 1
| /olver/ncurses/clear/tests/clear_spec 1
| /olver/ncurses/input/tests/getstr_spec 1
| /olver/ncurses/input/tests/halfdelay_spec 1
| /olver/ncurses/input/tests/getnstr_spec 1
| /olver/ncurses/input/tests/getch_spec {1..3}
| /olver/ncurses/input/tests/ungetch_spec 1
| /olver/ncurses/line/tests/hline_spec 1
| /olver/ncurses/line/tests/vline_spec 1
| /olver/ncurses/line/tests/insertln_spec 1
| /olver/ncurses/line/tests/insdelln_spec 1
| /olver/ncurses/misc/tests/typeahead_spec 1
| /olver/ncurses/move/tests/move_spec {1,2}
| /olver/ncurses/string/tests/scanw_spec 1
| /olver/ncurses/string/tests/getstr_noErrorFromReq_spec 1
| /olver/ncurses/string/tests/printw_spec 1
| /olver/ncurses/string/tests/instr_spec 1
| /olver/ncurses/string/tests/addstr_spec {1,2}
| /olver/ncurses/terminal/tests/endwin_spec {1..12}
| /olver/ncurses/window/tests/attr_set_spec 1
| /olver/ncurses/window/tests/newpad_spec 1
| /olver/ncurses/window/tests/attroff_spec 1
| /olver/ncurses/window/tests/attr_off_spec 1
| /olver/ncurses/window/tests/standout_spec 1
| /olver/ncurses/window/tests/is_linetouched_spec 1
| /olver/ncurses/window/tests/attron_spec 1
| /olver/ncurses/window/tests/touchwin_spec 1
| /olver/ncurses/window/tests/refresh_spec {1,3..22}
| /olver/ncurses/window/tests/touchline_spec 1
| /olver/ncurses/window/tests/attrset_spec 1
| /olver/ncurses/window/tests/standend_spec 1
| /olver/ncurses/window/tests/wtouchln_spec 1
| /olver/ncurses/window/tests/untouchwin_spec 1
| /olver/ncurses/window/tests/copywin_spec 1
| /olver/ncurses/window/tests/attr_on_spec 1
| /olver/ncurses/window/tests/attr_get_spec 1
| /olver/ncurses/window/tests/is_wintouched_spec 1
| /olver/util/format/tests/wscanf_spec 1
| /olver/util/format/tests/vswscanf_spec 1
| /olver/util/format/tests/fwscanf_spec 1
| /olver/util/format/tests/wprintf_spec 1
| /olver/util/format/tests/vwprintf_spec 1
| /olver/util/format/tests/swscanf_spec 1
| /olver/util/format/tests/swprintf_spec 1
| /olver/util/format/tests/vfwprintf_spec 1
| /olver/util/format/tests/fwprintf_spec 1
| /olver/util/format/tests/vfwscanf_spec 1
| /olver/util/format/tests/vwscanf_spec 1
| /olver/util/format/tests/vswprintf_spec 2
| /olver/util/string/tests/wcsncasecmp_spec 1
| /olver/io/fstream/tests/fgetwc_spec 1
| /olver/time/timer/tests/timer_getoverrun_spec 1
SEVERITY failed
MARKER MEDIATOR_FAILED
MARKER Execution failed
OR
MARKER MEDIATOR_FAILED
MARKER Connection closed
OR
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {refresh.01;wrefresh.01} Refresh the current or specified window
COMMENT These failures are occuring on some newer systems. The issue is still under investigation, but are most likely issues with a component of the test suite. Waiving pending investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3397 | Bug 3397
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3472 | Bug 3472
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3582 | Bug 3582
RESOLUTION Probable test suite deficiency
WAIVE
END
### Problem Record #564
STANDARD LSB
TESTSUITE desktop < 4.1.9-1 | desktop-gtkvts < 4.1.9-1
TEST /tests/functions/Keyboard_Accelerator_Groups/Keyboard_Accelerator_Groups {27,28,29}
SEVERITY failed
MARKER Accelerator = 'q'
OR
MARKER Accelerator = 'a'
OR
MARKER Accelerator = 'F11'
COMMENT Upstream GTK has changed the behavior of gtk_accelerator_name. Where previously the function would return '' if the Ctrl key had been pressed, it now returns ''. We are considering this to be an incorrect test. For the full details, see the bug:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3408 | Bug 3408
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #565
STANDARD LSB
TESTSUITE desktop-t2c < 4.1.4-1
TEST /gobject-t2c/tests/gobject_value_arrays/gobject_value_arrays 24
SEVERITY failed
MARKER After sorting array, the 0-th element of array should be 1, but is 2
MARKER After sorting array, the 1-th element of array should be 2, but is 1
MARKER After sorting array, the 2-th element of array should be 3, but is 5
MARKER After sorting array, the 4-th element of array should be 5, but is 3
COMMENT This test is written to alter the sort order in a way to prove that user data is being passed, but does not take the user data change into account when comparing the results.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3412 | LSB bug 3412
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #566
STANDARD LSB
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 17
SEVERITY failed
MARKER Requirement failed:
MARKER {g_main_context_iteration.01.02.01}
MARKER may_block is TRUE, waiting for a source to become ready
COMMENT This appears to be specified somewhat ambiguously, with upstream's clarification being different from the test author. See the bug for more details.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3413 | Bug 3413
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #567
STANDARD LSB
TESTSUITE desktop-t2c
TEST -g /atk-t2c/tests/AtkObject_signals/AtkObject_signals {13,14,22,23}
SEVERITY failed
MARKER The signal "property-change" should be emitted when an object's property value
MARKER changes
OR
MARKER Function, passed to atk_object_connect_property_change_handler(), should be
MARKER called when property changes value
COMMENT Upstream fixed a performance issue which changed the behavior of ATK. It no longer notifies the app when the name or description properties are set on initialization.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3415 | LSB bug 3415
LINK https://bugzilla.gnome.org/show_bug.cgi?id=665870 | Upstream bug 665870
LINK https://git.gnome.org/browse/atk/commit/?id=d6edbd24abeb1dd340f450ddaa562de56fbd912b | Upstream commit which introduced the change
RESOLUTION Upstream behavior change
WAIVE
END
### Problem Record #568
STANDARD LSB
TESTSUITE desktop-t2c
TEST -g /glib-t2c/tests/glib_threads/glib_threads {1,2,3,8}
SEVERITY failed
MARKER g_thread_create_full: thread priority was not set.
OR
MARKER g_thread_create_full: invalid GThread struct returned upon thread creation.
COMMENT Upstream glib has deprecated g_thread_create_full, and now ignores priority.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3416 | Bug 3416
RESOLUTION Upstream change
WAIVE
END
### Problem Record #569
STANDARD LSB
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_messagelog/glib_messagelog 8
SEVERITY failed
MARKER Nothing was printed to stdout or the message did not match the expected one.
COMMENT This is caused by an upstream change to the default log handler for glib; debug and informational messages are now suppressed except when explicitly requested with the environment variable G_MESSAGES_DEBUG.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3417 | LSB bug 3417
LINK https://bugzilla.gnome.org/show_bug.cgi?id=661926 | Upstream bug
RESOLUTION Upstream change
WAIVE
END
### Problem Record #570
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 13
SEVERITY unresolved
MARKER Cannot create loader with type 'png': Image type 'png' is not supported.
COMMENT This test is failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3418 | Bug 3418
RESOLUTION Known Problem
END
### Problem Record #571
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 29
SEVERITY failed
MARKER The function was expected to return format with name 'png',
MARKER but name of the returned format is 'png12'.
MARKER The function returned invalid format name.
COMMENT This test is failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3418 | Bug 3418
RESOLUTION Known Problem
END
### Problem Record #572
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 20
SEVERITY failed
MARKER By default, "jpeg", "png" and "ico" are possible file formats to save in, but
MARKER more formats may be installed.
COMMENT This test is failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3419 | Bug 3419
RESOLUTION Known Problem
END
### Problem Record #573
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 15
SEVERITY failed
MARKER Image format is 'png',
MARKER but the function returned format name 'png12'
COMMENT This test is failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3420 | Bug 3420
RESOLUTION Known Problem
END
### Problem Record #574
STANDARD LSB
TESTSUITE desktop-t2c
TEST -g /gdk-pixbuf-t2c/tests/FileSaving/FileSaving {7,8,11,15,16,17,18,19,20}
SEVERITY failed
MARKER Saving is expected to complete successfully, but the function returned FALSE.
COMMENT These tests are failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
COMMENT LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3421 | Bug 3421
RESOLUTION Known Problem
END
### Problem Record #575
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST -g /tests/functions/GdkPixbufFileSaving/GdkPixbufFileSaving {2,7}
SEVERITY failed
MARKER "gdk_pixbuf_save":error happened!
COMMENT These tests are failing on some distributions where the GTK stack is built against libpng15 and the 'png' loader is reported as 'png12'.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3422 | Bug 3422
RESOLUTION Known Problem
END
### Problem Record #576
STANDARD LSB
TESTSUITE libstdcpp < 4.1.0-10 | libstdcpp >= 4.1.0-16 & < 4.1.0-18
TEST /21_strings/basic_string/cons/char/1.cc 1
| /21_strings/basic_string/cons/wchar_t/1.cc 1
| /21_strings/basic_string/insert/char/1.cc 1
| /21_strings/basic_string/insert/wchar_t/1.cc 1
| /27_io/ios_base/storage/1.cc 1
| /27_io/ios_base/storage/2.cc 1
SEVERITY failed
MARKER DejaGNUTest.command_output_1: terminate called after throwing an instance of 'St9bad_alloc'
MARKER DejaGNUTest.command_output_1: what(): std::bad_alloc
OR
MARKER DejaGNUTest.command_output_1: Unexpected error.
COMMENT These tests are failing, primarily on x86_64 on newer distributions with the latest libstdc++. There was a change in the upstream tests that allocates more memory for the test, which has now been applied to the LSB versions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3317 | Bug 3317
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #577
STANDARD LSB
TESTSUITE perl
TEST pod/plainer.t 815
SEVERITY unreported
MARKER The test case returned no result
COMMENT Pod::Plainer has been deprecated as of LSB 4.1, but it is disappearing in distributions before LSB's deprecation policy allows us to drop it. As such, the test for this module fails.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3276 | bug 3276
RESOLUTION Known Problem
END
### Problem Record #578
STANDARD LSB
TESTSUITE xml2-azov < 4.1.2-1
TEST -g /XML_SAX2_Parser-t2c/tests/XML_SAX2_Parser/XML_SAX2_Parser {32,37}
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT These two tests segfault on some x86_64 systems.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3110 | bug 3110
COMMENT Updated test suites have corrected the issues with these tests.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #579
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Fonts-t2c/tests/QFontDatabase/QFontDatabase {8,10}
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == false'
MARKER Requirement failed:
MARKER {italic.01}
MARKER <<< REQ NOT FOUND >>>
OR
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == false'
MARKER Requirement failed:
MARKER {bold.01}
MARKER <<< REQ NOT FOUND >>>
COMMENT This test fails on some leading edge distribution. Cause is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3423 | Bug 3423
RESOLUTION Known Problem
END
### Problem Record #580
STANDARD LSB
TESTSUITE perl < 4.0.10-1 | perl >= 4.1.0 & < 4.1.4-3
TEST ../lib/ExtUtils/t/MM_Unix.t 471
SEVERITY failed
MARKER FAILED test 105 Failed 1/105 tests, 99.05% okay
COMMENT This test fails on some systems. Updated versions of the test are patched to address this issue.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3424 | Bug 3424
RESOLUTION Known Problem
WAIVE
END
### Problem Record #581
STANDARD LSB
TESTSUITE rsync
TEST List localhost::rsync
| Retrieve localhost::rsync/rsyncd.conf
| Upload localhost::rsync/rsyncd.conf
| Compare uploaded file with the original one
SEVERITY failed
MARKER rsync: failed to connect to localhost: Connection refused (111)
OR
MARKER *
COMMENT This test fails on some systems when run under dist-checker, but seems to be OK when running the FVT manually. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3425 | bug 3425
RESOLUTION Known Problem
END
### Problem Record #582
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GMisc/GMisc 16
SEVERITY failed
MARKER g_find_program_in_path: failed
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3433 | bug 3433
RESOLUTION Known Problem
END
### Problem Record #583
STANDARD LSB
TESTSUITE desktop-t2c
TEST /glib-t2c/tests/glib_AsyncQueue/glib_AsyncQueue {8,18}
SEVERITY unresolved
MARKER Child process was terminated by signal 6.
MARKER Abnormal child process termination. errno: 22.
COMMENT These failures are still under investigation. They seem to be happening on some newer distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3434 | Bug 3434
RESOLUTION Known Problem
END
### Problem Record #584
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Arrays-t2c/tests/Qt4_Arrays/Qt4_Arrays 1
SEVERITY unresolved
MARKER Child process timed out.
COMMENT This failure is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3431 | bug 3431
RESOLUTION Known Problem
END
### Problem Record #585
STANDARD LSB
TESTSUITE perl
TEST all/tst_perlModPresent.pl 1
| ../lib/autouse.t 398
| ../lib/Class/ISA/t/00_about_verbose.t 435
| ../lib/Class/ISA/t/01_old_junk.t 436
SEVERITY failed
MARKER 26
OR
MARKER FAILED test 12 Failed 1/12 tests, 91.67% okay
OR
MARKER FAILED tests 1-2 Failed 2/2 tests, 0.00% okay
OR
MARKER test 26 'use Class::ISA;' failed
COMMENT Class::ISA is deprecated as of LSB 4.1, but it is disappearing from some distributions more quickly than it will from LSB.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3435 | Bug 3435
RESOLUTION Known Problem
END
### Problem Record #586
STANDARD LSB
TESTSUITE core < 4.0.7-1 | core >= 4.1.0-1 & < 4.1.10-1
TEST /tset/LSB.os/network/gethostbyaddr/T.gethostbyaddr 2
SEVERITY failed
MARKER after gethostbyaddr() for 127.0.0.2, h_errno was set to 3
COMMENT Newer version of the test accept 3 (NO_RECOVERY) as a valid result also.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3438 | Bug 3438
RESOLUTION Known Problem
WAIVE
END
### Problem Record #587
STANDARD LSB
TESTSUITE desktop | desktop-cairo
TEST composite-integer-translate-source-image 4
| composite-integer-translate-source-xlib 5
| create-from-png-image 8
| create-from-png-xlib 9
| create-from-png-stream-image 10
| create-from-png-stream-xlib 11
SEVERITY failed
MARKER Error: Function under test left cairo status in an error state: NULL pointer
OR
MARKER Error: Function under test left cairo status in an error state: out of memory
OR
MARKER Error: Function under test failed
COMMENT These failures are occurring on new distributions where the gtk stack is built against libpng15. The tests are LSB compliant, built against libpng12, but on the host system end up attempting to use both libraries. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3364 | bug 3364
RESOLUTION Known Problem
END
### Problem Record #588
STANDARD LSB
TESTSUITE desktop | desktop-qt4
TEST tst_QCalendarWidget_buttonClickCheck 2
SEVERITY failed
MARKER Compared values are not the same Actual (2006): 2006 Expected (object.yearShown()):
COMMENT This issue is still under investigation. Test returns the current year rather than the expected 2006.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3064 | bug 3064
RESOLUTION Known Problem
END
### Problem Record #589
STANDARD LSB
TESTSUITE olver
TEST /olver/util/compress/tests/deflateSetDictionary_spec 1
SEVERITY failed
MARKER Scenario util_compress_scenario:
MARKER MEDIATOR_FAILED
MARKER Segmentation fault: Invalid memory address
OR
MARKER MEDIATOR_FAILED
MARKER Connection closed
COMMENT This issue is still under investigation, but is most likely an issue with a component of the test suite. Waiving until a resolution is known.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3439 | bug 3439
RESOLUTION Probable test suite deficiency
WAIVE
END
### Problem Record #590
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Dialogs-t2c/tests/QMessageBox/QMessageBox 27
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0.isNull() == false'
MARKER Requirement failed:
MARKER {standardIcon.01}
MARKER <<< REQ NOT FOUND >>>
COMMENT This is failing on some newer distributions. The issue is still under investigation. It seems to be related to Xvfb also.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3230 | bug 3230
COMMENT If you find the test to fail, you can try running it under the native display:
COMMENT TET_ROOT=`pwd` /opt/lsb/test/qt4-azov/Qt4_Dialogs-t2c/tests/QMessageBox/QMessageBox 27 && cat tet_xres
RESOLUTION Known Problem
WAIVE FIP
END
### Problem Record #591
STANDARD LSB
TESTSUITE olver
TEST /olver/util/compress/tests/get_crc_table_spec 1
| /olver/util/compress/tests/get_crc_table_spec 846
SEVERITY failed
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {get_crc_table.01;get_crc_table.03} Shall return a pointer to the first of a set of tables
COMMENT This was caused by an upstream change to the signature of get_crc_table, which under subsequent testing does cause ABI compatibility issues. Since this is an upstream bug, am pursuing with upstream. See:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3441 | bug 3441
RESOLUTION Upstream issue
WAIVE
END
### Problem Record #592
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Core_Functions-t2c/tests/Qt4_Core_Functions/Qt4_Core_Functions 33
SEVERITY unresolved
MARKER Target interface(s):
MARKER qt_check_pointer(char const*, int)
MARKER Child process was terminated by signal 6.
MARKER Abnormal child process termination. errno: 22.
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3444 | Bug 3444
RESOLUTION Known Problem
END
### Problem Record #593
STANDARD LSB
TESTSUITE printing
TEST /testfoomaticrip/testfoomaticrip 2
SEVERITY unreported
MARKER foomatic-rip inserts standard PPD options correctly into
MARKER the PostScript data stream.
MARKER Executing /usr/bin/foomatic-rip --ppd
COMMENT Due to a change in the way foomaticrip handles the environment variable PPD, newer versions of foomaticrip fail to run the test set correctly, attempting to spool the print jobs to cups. Updated versions of the test use a different environment variable to be able to handle this change.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3272 | Bug 3272
RESOLUTION Known Problem
WAIVE
END
### Problem Record #594
STANDARD LSB
TESTSUITE libstdcpp < 4.1.0-8 | libstdcpp >= 4.1.0-13 & < 4.1.0-16
TEST /22_locale/num_put/put/char/9780-2.cc 1
SEVERITY failed
MARKER Assertion `res == "1234567890"' failed.
MARKER DejaGNUTest.command_status_1: 134
MARKER DejaGNUTest.result_1: FAIL: 22_locale/num_put/put/char/9780-2.cc execution test
COMMENT This test is failing on some newer systems due to changes in the locales being used by the test. Updated test packages have corrected the issue.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3287 | Bug 3287
RESOLUTION Known Problem
WAIVE
END
### Problem Record #595
STANDARD LSB
TESTSUITE core < 4.0.7-1 | core >= 4.1.0-1 & < 4.1.11-1
TEST /tset/ANSI.os/streamio/freopen/T.freopen {33,34,38}
SEVERITY failed, uninitiated
MARKER fstat() on file descriptor associated with stream after freopen() did not return expected values
MARKER RETURN VALUES: expected: -1, observed: 0
MARKER ERRNO VALUES: expected: 9 (EBADF), observed: 0 (NO ERROR)
OR
MARKER depends on success of test 33
OR
MARKER freopen() did not re-use closed file descriptor
COMMENT Upstream behavior has changed slightly and test relied on behavior not defined in the spec. Updated tests disable these subtests.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3436 | Bug 3436
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #596
STANDARD LSB
TESTSUITE tcl
TEST http-6.1
SEVERITY failed
MARKER Test generated error; Return code was: 1
MARKER Return code should have been one of: 0 2
MARKER errorInfo: couldn't open socket: host is unreachable (No address associated with hostname)
COMMENT This issue is still under investigation. The test is failing on some newer distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3347 | Bug 3347
RESOLUTION Known Problem
END
### Problem Record #597
STANDARD LSB
TESTSUITE python
TEST /usr/bin/python 30
SEVERITY failed
MARKER errors occurred; run in verbose mode for details
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3320 | Bug 3320
RESOLUTION Known Problem
END
### Problem Record #598
STANDARD LSB
TESTSUITE libstdcpp
TEST /demangle/regression/cw-16.cc 1
SEVERITY failed
MARKER DejaGNUTest.command_output_1: terminate called after throwing an instance of 'std::runtime_error'
MARKER DejaGNUTest.command_output_1: what(): void f<5, A>(C::q)
COMMENT This issue is still under investigation
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3449 | Bug 3449
RESOLUTION Known Problem
WAIVE
END
### Problem Record #599
STANDARD LSB
TESTSUITE perl < 4.0.10-1 | perl >= 4.1.0 & < 4.1.4-4
TEST ../lib/ExtUtils/t/basic.t
SEVERITY failed
MARKER FAILED tests 60, 62-64 Failed 4/73 tests, 94.52% okay
COMMENT This issue is still under investigation
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3450 | Bug 3450
RESOLUTION Known Problem
WAIVE
END
### Problem Record #600
STANDARD LSB
TESTSUITE perl
TEST all/tst_perlModPresent.pl
SEVERITY failed
MARKER 131
OR
MARKER test 131 'use Locale::Constants;' failed
COMMENT Locale::Constants is not available on some newer distributions. LSB still requires it.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3282 | Bug 3282
RESOLUTION Known Problem
WAIVE
END
### Problem Record #601
STANDARD LSB
TESTSUITE perl < 4.0.10-1 | perl >= 4.1.0 & < 4.1.4-4
TEST ../lib/ExtUtils/t/basic.t 461
SEVERITY failed
MARKER FAILED test 64
COMMENT Some versions of perl-ExtUtils-MakeMaker return a slightly different string. Tests will proably be corrected to handle this.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3457 | bug 3457
RESOLUTION Known Problem
WAIVE
END
### Problem Record #602
STANDARD LSB
TESTSUITE xml2-azov
TEST /XML_Tree-t2c/tests/XML_Tree/XML_Tree 52
SEVERITY failed
MARKER xmlGetDocCompressMode
MARKER CONSTRAINT FOR RETURN FAILED: '$0 > -1'
COMMENT This test fails against libxml 2.9.0 and 2.9.1, introduced accidentally along with xzlib compression support. The linked patch reportedly fixes it, and the fix should become available in libxml 2.9.2.
LINK https://git.gnome.org/browse/libxml2/commit/?id=63588f476f2dc89d4c6ef70a474d7230fbf4d45e | Upstream fix.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3456 | Bug 3456.
RESOLUTION Upstream bug
END
### Problem Record #603
STANDARD LSB
TESTSUITE qt4-azov
TEST /Normal_Test-t2c/tests/QSessionManager/QSessionManager {1..20}
SEVERITY unresolved
MARKER Child process timed out
COMMENT These tests are failing on some leading edge distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3454 | Bug 3454
RESOLUTION Known Problem
END
### Problem Record #604
STANDARD LSB
TESTSUITE desktop < 4.0.7-1 | desktop-xml < 4.0.7-1 | desktop >= 4.1.0-2 & < 4.1.7-1 | desktop-xml >= 4.1.0-2 & < 4.1.7-1
TEST XML_3 10
| XML_14 25
| XML_22 {4,5}
SEVERITY failed
MARKER Result for ./test/namespaces/err_7.xml failed
MARKER File ./test/namespaces/err_7.xml generated an error
OR
MARKER Error for ./test/valid/xlink.xml failed
MARKER File ./test/valid/xlink.xml generated an error
OR
MARKER Result for ./test/xmlid/id_tst2.xml failed
MARKER File ./test/xmlid/id_tst2.xml generated an error
OR
MARKER Result for ./test/xmlid/id_tst3.xml failed
MARKER File ./test/xmlid/id_tst3.xml generated an error
COMMENT These test are failing on some leading edge distributions. These are regression tests and the expected result has changed upstream. The tests are disabled in new builds of the test suite.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3455 | Bug 3455
RESOLUTION Known Problem
WAIVE
END
### Problem Record #605
STANDARD LSB
TESTSUITE printing
TEST /testgs/testgs 7
SEVERITY failed
MARKER Checking result of processing a known .ps file using the opvp device
MARKER /usr/bin/gs returned 1 using the opvp driver, expected 0
COMMENT This problem seems to come and go, and may be related to the build or configuration of Ghostscript on the installed system. If you see this problem, check that Ghostscript is otherwise functional on your system, and please report your observations to the bug below.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=2994 | Bug 2994
RESOLUTION Known Problem
END
### Problem Record #606
STANDARD LSB
TESTSUITE perl < 4.0.10-1 | perl >= 4.1.0 & < 4.1.4-5
TEST ../lib/Carp.t 419
SEVERITY unreported
MARKER The test case returned no result
COMMENT Some distributions package a different version of Carp than what is in perl-core. Expectations of the test don't work against this version. New versions of the test disable several subtests.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3466 | Bug 3466
RESOLUTION Known Problem
WAIVE
END
### Problem Record #607
STANDARD LSB
TESTSUITE xts5
TEST /tset/Xproto/cnvrtslctn/Test 3
SEVERITY failed
MARKER REPORT: Expect: wanted NOTHING, got TIMEOUT! (server may be dead)
MARKER REPORT: Test ConvertSelection failed with 1 error.
MARKER CHECK: ConvertSelection-3 1, line 327
COMMENT This test is failing on some newer distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3473 | Bug 3473
RESOLUTION Known Problem
END
### Problem Record #608
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_closures/gobject_closures {7,8}
SEVERITY failed
MARKER Checked requirement: {app.g_closure_set_meta_marshal.04}
MARKER Count of notifiers hasn't increased by 1.
MARKER Requirement failed:
MARKER {g_closure_set_meta_marshal.01}
MARKER Sets the meta marshaller as notifier of closure.
COMMENT This is caused by a performance improvement on an internal struct; not being fixed upstream.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3474 | Bug 3474
RESOLUTION Upstream change
WAIVE
END
### Problem Record #609
STANDARD LSB
TESTSUITE olver
TEST /olver/ncurses/terminal/tests/tigetnum_spec 1
SEVERITY failed
MARKER POSTCONDITION_FAILED
MARKER Requirement failed: {tigetnum.01;tigetnum.03.01} return value should be equal to the capability requested
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3475 | Bug 3475
RESOLUTION Known Problem
END
### Problem Record #610
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_OpenGL-t2c/tests/QGLPixelBuffer/QGLPixelBuffer 1
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT This issue is still under investigation
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3471 | Bug 3471
RESOLUTION Known Problem
END
### Problem Record #611
STANDARD LSB
TESTSUITE xts5 < 5.1.5-43
TEST /tset/Xlib7/qryclrs/Test 2
SEVERITY failed
MARKER VSW5TESTSUITE PURPOSE 2
MARKER Assertion XQueryColors-2.(A)
MARKER When a colourmap argument does not name a valid colourmap,
MARKER then a BadColor error occurs.
MARKER METH: Create a bad colourmap by creating and freeing a colourmap.
MARKER METH: Call test function using bad colourmap as the colourmap argument.
MARKER METH: Verify that a BadColor error occurs.
MARKER REPORT: Got Success, Expecting BadColor
COMMENT This failure is occurring on some leading edge distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3480 | Bug 3480
COMMENT It appears the change in behavior is fallout from a different bugfix from upstream. A new bug upstream has been opened on this issue.
LINK https://bugs.freedesktop.org/show_bug.cgi?id=51313 | bug 51313
COMMENT The test has been disabled in updated testsuites. It's not clear from the spec whether a BadColor error must be emitted.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #612
STANDARD LSB
TESTSUITE core
TEST T.misc {35..73}
SEVERITY unresolved, failed
COMMENT These tests may fail if you have SELinux enabled on the system under test. Please disable or relax SELinux restrictions for LSB testing.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3476 | bug 3476
RESOLUTION Known Problem
END
### Problem Record #613
STANDARD LSB
TESTSUITE olver < 4.1.3-8
TEST /olver/other/other/tests/others {1,3,6,7,9,11,13,15..18,21..23}
SEVERITY failed
MARKER verifyLength_TSStream failed
COMMENT These tests are failing on some of the leading edge distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3491 | bug 3491
COMMENT Updated test suites correct the test issue (WString alignment problem).
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #614
STANDARD LSB
TESTSUITE python < 4.0.4-1 | python >= 4.1.1-1 & < 4.1.5-1
TEST /usr/bin/python 30
SEVERITY failed
MARKER errors occurred; run in verbose mode for details
COMMENT The behavior/test for the test_csv/test_float_write, test_double_write has changed. New builds of the test suite disable these tests.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3320 | bug 3320
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #615
STANDARD LSB
TESTSUITE olver
TEST /olver/other/other/tests/others 1
SEVERITY failed
MARKER Scenario util_assert_error_scenario
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3528 | bug 3528
RESOLUTION Known Problem
END
### Problem Record #616
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/network/recvfrom/T.recvfrom 3
SEVERITY failed
MARKER recvfrom failed for flag=MSG_WAITALL returning error Invalid argument
COMMENT This problem was seen with Linux kernels 3.7 and 3.8, at least, and may affect older kernels. A patch has been accepted to fix the problem. See:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3523 | LSB bug 3523,
LINK http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0e82e7f6dfeec1013339612f74abc2cdd29d43d2 | the Linux kernel patch fixing the problem.
RESOLUTION Upstream bug
END
### Problem Record #617
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/network/recvmsg/T.recvmsg 3
SEVERITY failed
MARKER recvmsg failed for flag=MSG_WAITALL returning error Invalid argument
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3525 | Bug 3525
RESOLUTION Known Problem
END
### Problem Record #618
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/network/recvmsg/T.recvmsg {5,7,8,10,11,12}
| /tset/LSB.os/network/recvfrom/T.recvfrom {3,5,7,8,10,11}
SEVERITY unreported
MARKER ERROR on binding
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3524 | Bug 3524
RESOLUTION Known Problem
END
### Problem Record #619
STANDARD LSB
TESTSUITE qt4-azov
TEST /Qt4_Multimedia-t2c/tests/QImage/QImage 66
SEVERITY failed
MARKER Target interface(s):
MARKER QImage::save(QIODevice*, char const*, int) const
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == true'
COMMENT This test is failing on some newer distributions. It appears when Qt4 is linked against libpng >= 1.5.10.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3538 | bug 3538
RESOLUTION Known Problem
WAIVE
END
### Problem Record #620
STANDARD LSB
TESTSUITE qt3-azov
TEST /Qt3_Multimedia-t2c/tests/QImage/QImage {15,32,42,56}
| /Qt3_Paint_Device-t2c/tests/QPixmap/QPixmap 26
SEVERITY failed
MARKER Target interface(s):
MARKER QImage::QImage[in-charge](QMemArray const&)
MARKER --------
MARKER CONSTRAINT FOR OBJECT FAILED: '$0.isNull() == false'
OR
MARKER Target interface(s):
MARKER QImage::save(QIODevice*, char const*, int) const
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == true'
OR
MARKER Target interface(s):
MARKER QImage::QImage[not-in-charge](QMemArray const&)
MARKER --------
MARKER CONSTRAINT FOR OBJECT FAILED: '$0.isNull() == false'
OR
MARKER Target interface(s):
MARKER QImage::loadFromData(QMemArray, char const*)
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == true'
OR
MARKER Target interface(s):
MARKER QPixmap::loadFromData(QMemArray const&, char const*, int)
MARKER --------
MARKER CONSTRAINT FOR RETURN FAILED: '$0 == true'
COMMENT These tests are failing on newer distributions. It appears when Qt3 is linked against libpng >= 1.5.10.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3533 | bug 3533
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3534 | bug 3534
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3535 | bug 3535
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3536 | bug 3536
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3537 | bug 3537
RESOLUTION Known Problem
WAIVE
END
### Problem Record #621
STANDARD LSB
TESTSUITE core < 4.1.15-1
TEST /tset/LSB.os/network/gethostbyaddr/T.gethostbyaddr 1
SEVERITY failed
MARKER Checks gethostbyaddr to return hostent structure
MARKER gethostbyaddr() returned NULL
MARKER h_errno was set to 1
COMMENT This test has been found to call getaddrinfo() incorrectly, which causes the lookup to fail under some system configurations.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=2583 | bug 2583
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #622
STANDARD LSB
ARCHITECTURE PPC64
TESTSUITE core
TEST /tset/LSB.os/mfiles/mmap_P/T.mmap_P {3,4}
SEVERITY failed
MARKER write() failed, errno = 0 (NO ERROR)
COMMENT This is being caused by an error in a setup routine that's unrelated to the condition being tested.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3568 | LSB bug 3568
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #623
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 4
SEVERITY failed
MARKER write() failed, errno = 0 (NO ERROR)
COMMENT This failure is happening on some ppc64 systems. The issue is still under investigation, but is most likely a test bug.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3569 | bug 3569
RESOLUTION Known Problem
WAIVE
END
### Problem Record #624
STANDARD LSB
TESTSUITE perl
TEST all/tst_perlModPresent.pl 1
| ../lib/Shell.t {655,656}
SEVERITY failed
MARKER test 203 'use Shell;' failed
OR
MARKER 203
OR
MARKER test 1 'use Shell;' failed
COMMENT Shell has been deprecated upstream by Perl and removed in 5.16 and some distributions. As of LSB 4.1, it is still a requirement.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3459 | bug 3459
RESOLUTION Distribution Problem
END
### Problem Record #625
STANDARD LSB < 5.0
ARCHITECTURE S390X
TESTSUITE xts5
TEST /tset/XI/chgfctl/Test 4
SEVERITY unreported
MARKER REPORT: A fatal I/O error occurred
MARKER REPORT: Any following results can not be relied upon
COMMENT This is most likely a build issue with some versions of the xts5 test suite on s390x. Newer packages correct this issue (LSB 4.0 and up)
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=2116 | bug 2116
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3613 | bug 3613
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #626
STANDARD LSB
TESTSUITE xml2-azov < 4.1.1-1
TEST /XML_Parser-t2c/tests/XML_Parser/XML_Parser 43
SEVERITY failed
MARKER CONSTRAINT FOR RETURN FAILED: '$0 > -1'
COMMENT This test is failing on some of the leading edge distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3632 | bug 3662
COMMENT Upstream has deprecated this interface and newer versions always return -1. The test has been modified to accept >= -1.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #627
STANDARD LSB
TESTSUITE perl < 4.1.7-1
TEST ../lib/CGI/t/form.t 421
| ../lib/CGI/t/function.t 422
SEVERITY failed
MARKER test 2 'start_form()' failed
OR
MARKER Line 2963: The test case returned no result
COMMENT These tests are failing against perl-CGI-3.600.0.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3660 | bug 3660
COMMENT Updated test suites disable these subtests.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #628
STANDARD LSB
TESTSUITE perl < 4.1.7-1
TEST ../lib/Getopt/Long/t/gol-compat.t 518
SEVERITY unreported
MARKER The test case returned no result
COMMENT This test is failing on some newer distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3664 | Bug 3664
COMMENT Updated test suites disable this test as newgetopt.pl is deprecated.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #629
STANDARD LSB
TESTSUITE desktop-t2c < 4.1.3-1
TEST /fontconfig-t2c/tests/FcConfig/FcConfig {3,11}
SEVERITY failed
MARKER The folder /home/tester/.local/share/fonts was presented nowhere in the contents of config files
MARKER The list of directories is incorrect
OR
MARKER Could not properly return font directories list
COMMENT This test is failing on some newer distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3663 | bug 3663
COMMENT Updated test suites address these issues.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #630
STANDARD LSB
TESTSUITE core < 4.1.13-1
TEST /tset/LSB.os/network/send/T.send 7
| /tset/LSB.os/network/sendto/T.sendto 8
SEVERITY failed
MARKER send failed by returning Operation not supported instead of EPIPE
OR
MARKER sendto failed by returning Operation not supported instead of EPIPE
COMMENT These tests are failing on some newer distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3661 | Bug 3661
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #631
STANDARD LSB
TESTSUITE desktop < 4.1.8-1 | desktop-xml < 4.1.8-1
TEST XML_14 {20,21}
SEVERITY failed
MARKER Error for ./test/valid/t8.xml failed
MARKER File ./test/valid/t8.xml generated an error
OR
MARKER Error for ./test/valid/t8a.xml failed
MARKER File ./test/valid/t8a.xml generated an error
COMMENT These tests are failing on some newer distributions.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3665 | Bug 3665
COMMENT Expected error output changed slightly with newer libxml2. These tests have been disabled.
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #632
STANDARD LSB
TESTSUITE alsa-t2c
TEST /ALSA-t2c/tests/ALSA_High_level_Control_Interface/ALSA_High_level_Control_Interface {2..10}
| /ALSA-t2c/tests/ALSA_Mixer_Interface/ALSA_Mixer_Interface {4..9}
| /ALSA-t2c/tests/ALSA_Simple_Mixer_Interface/ALSA_Simple_Mixer_Interface {4..9,14..37,46..51,53..59,63..68}
SEVERITY failed
MARKER child process was terminated by signal 6
COMMENT These tests are failing on some newer distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3666 | Bug 3666
RESOLUTION Known Problem
END
### Problem Record #633
STANDARD LSB
TESTSUITE tcl
TEST clock34.{6,12..18}
SEVERITY failed
MARKER ---- Test generated error; Return code was: 1
MARKER ---- Return code should have been one of: 0 2
MARKER ---- errorInfo: time value too large/small to represent while executing
COMMENT These tests seem to fail on systems where /etc/localtime is missing. Manually place the correct timezone file in this locate or use the systems configuration tools to configure the timezone.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3668 | Bug 3668
RESOLUTION Distribution Problem
END
### Problem Record #634
STANDARD LSB
TESTSUITE core
TEST -g /tset/initd/misc/install/general-tc {2,4}
SEVERITY failed
MARKER If an initscript depends on a boot facility it shall be activated
MARKER by a call to install_initd if the dependency is met
MARKER Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initB
MARKER exit code 1 returned, expected 0
MARKER Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initA
MARKER exit code 1 returned, expected 0
OR
MARKER An initscript shall be deactivated by a call to remove_initd
MARKER Call /usr/lib/lsb/install_initd /etc/init.d/lsb-initB
MARKER exit code 1 returned, expected 0
COMMENT These tests are failing on some leading edge distributions. The issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3669 | Bug 3669
RESOLUTION Known Problem
END
### Problem Record #635
STANDARD LSB
TESTSUITE tcl
TEST chan-io-53.9
SEVERITY failed
MARKER ---- Result was:
MARKER fcopy hangs
MARKER ---- Result should have been (exact matching):
MARKER OK
COMMENT This test is failing on some newer distributions, the issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3684 | Bug 3684
RESOLUTION Known Problem
END
### Problem Record #636
STANDARD LSB
TESTSUITE core
TEST -g /tset/ANSI.os/streamio/fputs/T.fputs 6
| /tset/ANSI.os/streamio/fwrite/T.fwrite {2,9..16}
| /tset/ANSI.os/streamio/printf/T.fprintf 63
| /tset/ANSI.os/streamio/printf/T.printf 63
| /tset/ANSI.os/streamio/puts/T.puts 6
| /tset/ANSI.os/streamio/vprintf/T.vfprintf 63
| /tset/ANSI.os/streamio/vprintf/T.vprintf 63
| /tset/POSIX.os/Csupport/fdopen/T.fdopen {3,11}
SEVERITY failed, unresolved
MARKER deletion reason: error in do_ferr(): child process timed out
OR
MARKER fwrite() failed to return expected values when ulimit was exceeded
MARKER expected between 0 and 12, got 20
OR
MARKER fwrite() returned nitems when testing for errno 11(EAGAIN), expected < nitems
OR
MARKER fwrite() returned nitems when testing for errno 9(EBADF), expected < nitems
OR
MARKER fwrite() returned nitems when testing for errno 27(EFBIG), expected < nitems
OR
MARKER fwrite() returned nitems when testing for errno 32(EPIPE), expected < nitems
OR
MARKER fwrite() from orphaned background process group did not give correct results
MARKER expected return: <= 0, actual: 1
OR
MARKER after fdopen(fd, "r") on read/write file descriptor, fwrite() succeeded
OR
MARKER after fdopen(fd, "rb") on read/write file descriptor, fwrite() succeededafter fdopen(fd, "rb") on read/write file descriptor, fwrite() succeeded
COMMENT This issue appears on newer distributions, using glibc-2.17. The bug has been confirmed upstream, and a fix is reportedly under development.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3702 | bug 3702
LINK http://sourceware.org/bugzilla/show_bug.cgi?id=15362 | glibc bug 15362
RESOLUTION Upstream bug
END
### Problem Record #637
STANDARD LSB
TESTSUITE perl < 4.1.8-1
TEST ../lib/ExtUtils/t/Liblist.t 465
SEVERITY failed
MARKER test 6 '' failed
MARKER FAILED test 6 Failed 1/6 tests, 83.33% okay
COMMENT This test is failing with newer distributions/perl.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3735 | bug 3735
COMMENT Updated test suites correct the issue
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #638
TESTSUITE olver
TEST /olver/util/crypt/tests/crypt_spec 1
SEVERITY failed
MARKER Unexpected error code returned: [EINVAL]
COMMENT This is a Linux extension to indicate an issue with an illegal salt. See
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3762 | bug 3762
COMMENT for more details.
RESOLUTION Specification / test suite deficiency
WAIVE
END
### Problem Record #639
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/files/ioctl/T.ioctl 3
SEVERITY failed
MARKER Checks ioctl() for error value EINVAL
MARKER errno was set to 25, it is expected to be 22[EINVAL]
COMMENT In newer kernels, the return value of ioctl() under certain circumstances was changed. The new value (ENOTTY instead of EINVAL) is legal, but the test requires the old kernel behavior. For more information, see:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3768 | bug 3768
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #640
STANDARD LSB
TESTSUITE olver
TEST /olver/fs/glob/tests/glob64_spec 1
SEVERITY failed
MARKER MEDIATOR_FAILED
COMMENT This issue is still under investigation, but is most likely a bug in a component of the test suite. Waiving pending a full resolution.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3769 | bug 3769
RESOLUTION Probable test suite deficiency
WAIVE
END
### Problem Record #641
STANDARD LSB
ARCHITECTURE S390X
TESTSUITE xml2-azov
TEST /XML_Catalogs-t2c/tests/XML_Catalogs/XML_Catalogs {1..34}
SEVERITY failed
MARKER SIGSEGV
COMMENT This failure is still under investigation. It may be caused by a bug in the LSB SDK.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3761 | bug 3761
RESOLUTION Probable test suite deficiency
END
### Problem Record #642
STANDARD LSB
TESTSUITE olver
TEST /olver/system/sysconf/tests/pathconf_spec 1
SEVERITY failed
MARKER Shall not change errno
COMMENT This is caused by glibc modifying errno internally when performing some operations against a XFS filesystem. The bug is fixed in recent glibc, and a patch is available.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3763 | LSB bug 3763
LINK http://sourceware.org/bugzilla/show_bug.cgi?id=15305 | glibc bug 15305
LINK http://repo.or.cz/w/glibc.git/commit/d755bba40f880c01ced8740a26fecc85534454b9 | Upstream fix
RESOLUTION Upstream bug
END
### Problem Record #643
STANDARD LSB
TESTSUITE desktop < 4.1.9-1 | desktop-gtkvts < 4.1.9-1
TEST /tests/functions/GtkTextTag/GtkTextTag {1..7}
SEVERITY failed
MARKER parent_instance.ref_count
MARKER should be 0
COMMENT This portion of the test is inappropriate; the test should not be checking an unspecified implementation detail of the GObject opaque type.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3565 | LSB bug 3565
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #644
STANDARD LSB
TESTSUITE perl
TEST ../lib/CGI/t/function.t 422
SEVERITY failed
MARKER The test case returned no result
COMMENT This issue is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3744 | bug 3744
RESOLUTION Known problem
END
### Problem Record #645
STANDARD LSB
TESTSUITE desktop < 4.1.9-1 | desktop-gtkvts < 4.1.9-1
TEST /tests/functions/GdkColormaps/GdkColormaps 47
SEVERITY failed
MARKER green value of color should be 65535, not 32896
COMMENT Upstream has changed the value of some of the predefined colors to match CSS's definitions more closely. Apart from a reference to X11's rgb.txt, these color names are not clearly specified, and so requiring a specific RGB value is not specified.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3777 | LSB bug 3777
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #646
#STANDARD LSB
#TESTSUITE desktop
#TEST XML_14 {20,21}
# SEVERITY failed
# MARKER Error for ./test/valid/t8.xml failed
# MARKER File ./test/valid/t8.xml generated an error
# OR
# MARKER Error for ./test/valid/t8a.xml failed
# MARKER File ./test/valid/t8a.xml generated an error
#COMMENT An upstream bug fix changed the format of some error messages. As we do not specify the exact error output, this should be considered a test bug.
#LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3786 | bug 3786
#RESOLUTION Test suite deficiency
#WAIVE
#END
### Problem Record #647
STANDARD LSB
ARCHITECTURE PPC64
TESTSUITE olver < 5.0
TEST /olver/io/term/tests/read_tty_spec 1
SEVERITY failed
MARKER Requirement failed: {app.read.10} IEXTEN flag is not set
COMMENT This issue is currently under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3788 | LSB bug 3788
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #648
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /opt/lsb/test/desktop/gtkvts/tet_tmp_dir/07312aa/tests/functions/atk_tcs/atk_tcs 14
SEVERITY failed
MARKER Role is not correctly registered!
COMMENT This bug is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3797 | LSB bug 3797
LINK https://bugzilla.redhat.com/show_bug.cgi?id=983891 | Red Hat bug 983891
RESOLUTION Known problem
END
### Problem Record #649
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gdk-pixbuf-t2c/tests/Animation/Animation 8
SEVERITY unresolved
MARKER Child process was terminated by signal 6.
COMMENT This has been confirmed to be a bug in GTK that appeared during the Fedora 19 development cycle. A fix is expected by the final released of Fedora 19.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3798 | LSB bug 3798
LINK https://bugzilla.redhat.com/show_bug.cgi?id=971747 | Red Hat bug 971747
RESOLUTION Upstream bug
END
### Problem Record #650
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_type_module/gobject_type_module {4..7}
SEVERITY failed
MARKER Plugin was not unloaded after the last instance of the registered type got unreferenced.
COMMENT This issue is still under investigation. See the LSB bug for more details.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3799 | LSB bug 3799
RESOLUTION Known problem
END
### Problem Record #651
STANDARD LSB
TESTSUITE perl
TEST ../ext/Encode/t/Unicode.t 262
SEVERITY failed
MARKER test 15 'decode UCS-2BE: fallback' failed
MARKER test 16 'decode UCS-2LE: fallback' failed
COMMENT An upstream bug in Unicode handling, which was reflected in the test suite, was fixed.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3800 | LSB bug 3800
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #652
STANDARD LSB
TESTSUITE core < 4.1.16 | runtime
TEST /tset/ANSI.os/streamio/scanf/T.scanf {54,55}
SEVERITY unresolved
MARKER dup() failed - errno 9 (EBADF)
COMMENT This is caused by a change to the behavior in freopen(). Although that behavior is likely wrong, it is unrelated to scanf(), and thus this failure is not legitimate. We will be changing the test to accomodate the current behavior of freopen(), and adding a separate test for that behavior.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3795 | LSB bug 3795
RESOLUTION Unrelated upstream problem
WAIVE
END
### Problem Record #653
STANDARD LSB
TESTSUITE core
TEST /tset/ANSI.os/streamio/fopen/T.fopen 23
| /tset/ANSI.os/streamio/freopen/T.freopen 25
| /tset/ANSI.os/streamio/remove/T.remove 19
| /tset/POSIX.os/files/access/T.access 43
| /tset/POSIX.os/files/chmod/T.chmod 18
| /tset/POSIX.os/files/chown/T.chown 18
| /tset/POSIX.os/files/creat/T.creat 28
| /tset/POSIX.os/files/link/T.link 23
| /tset/POSIX.os/files/mkdir/T.mkdir 18
| /tset/POSIX.os/files/mkfifo/T.mkfifo 16
| /tset/POSIX.os/files/open/T.open 44
| /tset/POSIX.os/files/rename/T.rename 33
| /tset/POSIX.os/files/rmdir/T.rmdir 20
| /tset/POSIX.os/files/unlink/T.unlink 20
| /tset/POSIX.os/files/utime/T.utime 19
SEVERITY failed
MARKER on a read-only file system did not return NULL
OR
MARKER expected: 30 (EROFS), observed: 0 (NO ERROR)
OR
MARKER expected: 30 (EROFS), observed: 2 (ENOENT)
COMMENT The tests use loopback mounts to test certain features; these failures occur when the file systems fail to be unmounted properly.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3785 | LSB bug 3785
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #654
STANDARD LSB
TESTSUITE perl
TEST ../lib/Tie/Memoize.t 775
SEVERITY failed
MARKER test 11 '' failed
COMMENT This test depends on unrelated modules existing in specific places in the implementation, and upstream has moved those modules.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3808 | Bug 3808
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #655
STANDARD LSB
TESTSUITE perl
TEST op/hash.t 111
SEVERITY unresolved
COMMENT This test is dependent on internal hash implementation details, and is thus not appropriate. Recent versions of Perl have changed those details in response to security issues, which cause this test to fail.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3814 | LSB bug 3814
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #656
STANDARD LSB
TESTSUITE desktop | desktop-qt4
TEST tst_QIcon_isNull 3
SEVERITY failed
COMMENT This problem is still under investigation. For more information, see:
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3065 | LSB bug 3065
RESOLUTION Known problem
END
### Problem Record #657
STANDARD LSB
TESTSUITE olver
TEST /olver/ncurses/terminal/tests/vidattr_spec 1
SEVERITY failed
MARKER Requirement failed: {vidattr.02} Read character shall be valid
COMMENT This failure is caused by an unrelated upstream change in buffer management.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3791 | LSB bug 3791
LINK https://bugzilla.redhat.com/show_bug.cgi?id=892674#c3 | Red Hat bug 892674 (feedback from upstream)
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #658
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/files/posix_madvise/T.posix_madvise 3
SEVERITY failed
MARKER posix_madvise returned Success instead of ENOMEM
COMMENT The test is supposed to request more memory than is available; advances in available memory on newer systems have made the current size request too small.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3792 | LSB bug 3792
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #659
STANDARD LSB
ARCHITECTURE PPC64
TESTSUITE libchk
TEST libQtGui.so.4 1380
SEVERITY failed
MARKER Virtual Function[0][0] _ZN15QListWidgetItemD1Ev (expected) doesn't match _ZN15QListWidgetItemD2Ev (found)
MARKER Symbol address found for Virtual table entry [0][3] 0x1ffffe0a1270 (found) doesn't match 0x1ffffe0a1280 (expected)
MARKER Virtual Function[0][3] NULL or _ZN15QListWidgetItem18setBackgroundColorERK6QColor (expected) doesn't match _ZNK11QListWidget10metaObjectEv (found)
COMMENT These problems are still under investigation. Note that there is a general issue with virtual table resolution on PPC64 systems under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3820 | LSB bug 3820
RESOLUTION Known problem
END
### Problem Record #660
STANDARD LSB
ARCHITECTURE PPC64
TESTSUITE libchk
TEST libQtXml.so.4 47
SEVERITY failed
MARKER Virtual Function[0][0] NULL or _ZN10QXmlReaderD1Ev (expected) doesn't match _ZN12QDomDocument10setContentERK10QByteArrayP7QStringPiS5_ (found)
MARKER Virtual Function[0][1] NULL or _ZN10QXmlReaderD0Ev (expected) doesn't match _ZN16QXmlSimpleReader5parseEPK15QXmlInputSource (found)
COMMENT This issue is currently under investigation. Note that there are issues with libchk's reading of vtables on PPC64.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3821 | LSB bug 3821
RESOLUTION Known problem
END
### Problem Record #661
STANDARD LSB
ARCHITECTURE PPC64
TESTSUITE libchk
TEST libstdc++.so.6 1171
SEVERITY failed
MARKER Virtual Function[0][0] NULL or _ZNSt23__codecvt_abstract_baseIwc11__mbstate_tED1Ev (expected) doesn't match _ZNSt15time_get_bynameIwSt19istreambuf_iteratorIwSt11char_traitsIwEEED1Ev (found)
MARKER Virtual Function[0][1] NULL or _ZNSt23__codecvt_abstract_baseIwc11__mbstate_tED0Ev (expected) doesn't match _ZNSt15time_get_bynameIwSt19istreambuf_iteratorIwSt11char_traitsIwEEED0Ev (found)
COMMENT This problem is currently under investigation. Note that there are a number of issues with libchk and vtables on PPC64.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3602 | LSB bug 3602
RESOLUTION Known problem
END
### Problem Record #662
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/dataform/cpio/T.cpio 24
| /tset/POSIX.os/dataform/tar/T.tar 31
SEVERITY failed
MARKER expected user ID: 1002; observed user ID: 1001
COMMENT At least one known version of pax forces the effective UID to match the real UID, which can cause some of our tests that are not setuid root to use the real instead of the expected effective UID.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3824 | LSB bug 3824
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #663
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/dataform/cpio/T.cpio 27
| /tset/POSIX.os/dataform/tar/T.tar 5
SEVERITY failed
MARKER file name was not resolved to "F"
COMMENT As a security measure, some tar/cpio/pax implementations strip leading path separators and disallow relative path links (i.e. "/" and ".."). This should be allowed as an exception to the regular spec.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3824 LSB bug 3824
RESOLUTION Specification deficiency
WAIVE
END
### Problem Record #664
STANDARD LSB
ARCHITECTURE S390X
TESTSUITE printing
TEST /convenience/cupsConvenience 37
SEVERITY failed
MARKER unexpected signal 6 (SIGABRT) received
COMMENT This is caused by a build issue with the CUPS libraries; a rebuild of the test should be sufficient to cause the issue to go away.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3828 | LSB bug 3828
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #665
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkTextIter/GtkTextIter {234,235,241,340..344,349,951,963,968..971,974..981,984,991,995..997}
SEVERITY failed
MARKER gtk_text_ends_word () returned not 1 incorrectly
OR
MARKER moved iterator incorrectly
COMMENT This changed in GTK+ in order to conform to current Unicode specifications; words are not supposed to break between adjacent letters and numbers now.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3823 | LSB bug 3823
LINK https://bugzilla.redhat.com/show_bug.cgi?id=984537 | Red Hat bug 984537
LINK https://git.gnome.org/browse/pango/commit/?id=1aeb5c840e25a7d8538f701659d77dcd7b3a8444 | Upstream commit changing this behavior
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #666
STANDARD LSB
TESTSUITE printing
TEST /convenience/cupsConvenience {1,2}
SEVERITY failed
MARKER returned NULL, expected a value
TEST /convenience/cupsConvenience {3,4}
SEVERITY failed
MARKER returned NULL, expected a filename
TEST /convenience/cupsConvenience {5,7-9,32}
SEVERITY failed
MARKER returned 0, expected a positive value
TEST /convenience/cupsConvenience {6,12}
SEVERITY unresolved
MARKER returned 0, expected a value
TEST /convenience/cupsConvenience 10
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV)
TEST /convenience/cupsConvenience 13
SEVERITY unresolved
MARKER returned error 'Bad file descriptor', expected nothing
COMMENT An upstream bug in cupsd appears to affect our local cupsd under certain builds. This is due to our reliance on the system's cupsd for our tests.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3629 | LSB bug 3629
LINK https://bugzilla.redhat.com/show_bug.cgi?id=977813#c3 | Red Hat bug 977813
LINK https://bugzilla.redhat.com/show_bug.cgi?id=978387 | Red Hat bug 978387
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #667
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/SpawnProc/SpawnProc 2
SEVERITY unresolved
MARKER unexpected signal 11 (SIGSEGV) received
COMMENT According to the bug report, the test function tries to use g_strdupv() on an array that is not NULL-terminated.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3865
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #668
STANDARD LSB
TESTSUITE desktop-t2c
TEST /fontconfig-t2c/tests/FcConstant/FcConstant {1..3}
SEVERITY failed
TEST /fontconfig-t2c/tests/FcObjectType/FcObjectType 1
SEVERITY failed
COMMENT Upstream has deprecated the FcNameRegisterObjectTypes and FcNameRegisterConstants functions; both now return FcFalse always. This test relies on those functions, and thus no longer works properly.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3740 | bug 3740
RESOLUTION Specification deficiency
WAIVE
END
### Problem Record #669
STANDARD LSB
TESTSUITE desktop | desktop-gtkvts
TEST /tests/functions/GtkButton/GtkButton {32,33}
MARKER unexpected signal
COMMENT This is caused by improper reference counting in some versions of GTK+. This bug has been fixed upstream. As it causes crashes under certain circumstances, all distributions should apply the fix.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3866 | LSB bug 3866
LINK https://bugzilla.gnome.org/show_bug.cgi?id=711552 | GNOME bug 711552
RESOLUTION Upstream bug
END
### Problem Record #670
STANDARD LSB
TESTSUITE core
TEST /tset/LSB.os/network/gethostbyaddr/T.gethostbyaddr 2
SEVERITY failed
MARKER after gethostbyaddr() for 127.0.0.2, h_errno was set to -1
COMMENT The test does not check the return value properly. See bug for details.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3843 | Bug 3843
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #671
STANDARD LSB
TESTSUITE desktop-t2c
TEST /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance {38,40,42}
SEVERITY failed
MARKER {g_type_add_class_cache_func.01}
COMMENT Upstream change; still investigating.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3844 | LSB bug 3844
LINK https://git.gnome.org/browse/glib/commit/?id=72df62600d1ab473125b6e8beb998e71aa63701e | Upstream patch introducing change
LINK https://bugzilla.gnome.org/show_bug.cgi?id=693351 | Upstream bug 693351
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #672
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/devclass/tcflush/T.tcflush 4
SEVERITY failed
MARKER when TOSTOP was set
COMMENT This is a kernel regression, fixed in more recent kernels. See the LSB bug or the mailing list discussion for more details.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3863 | LSB bug 3863
LINK http://lkml.iu.edu/hypermail/linux/kernel/1309.3/01613.html | Kernel patch
LINK http://lkml.iu.edu/hypermail/linux/kernel/1309.3/01277.html | LKML discussion
RESOLUTION Kernel bug
END
### Problem Record #673
STANDARD LSB
TESTSUITE core
TEST /tset/POSIX.os/procenv/setenv/T.setenv 1
SEVERITY unresolved
MARKER child process gave unexpected exit code
TEST /tset/POSIX.os/procenv/unsetenv/T.unsetenv 1
SEVERITY unresolved
MARKER child process gave unexpected exit code
COMMENT Bug in test code. See bug for details.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3847 | Bug 3847
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #674
STANDARD LSB
TESTSUITE core
TEST /tset/ANSI.os/genuts/abort/T.abort 7
SEVERITY unresolved
MARKER unexpected signal received
TEST /tset/ANSI.os/genuts/exit/T.exit 8
SEVERITY unresolved
MARKER unexpected signal received
TEST /tset/ANSI.os/genuts/_exit/T._exit 8
SEVERITY unresolved
MARKER unexpected signal received
TEST /tset/POSIX.os/procprim/sigconcept/T.sigconcept 40
SEVERITY unresolved
MARKER unexpected signal received
COMMENT This is caused by a kernel regression introduced in 3.10, and subsequently fixed. See the LSB bug for more information, and the linux-kernel mailing list thread for a patch.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3863 | LSB bug 3863
LINK https://lkml.org/lkml/2013/9/15/63 | LKML thread about this bug
RESOLUTION Test suite deficiency
END
### Problem Record #675
STANDARD LSB
TESTSUITE olver
TEST /olver/process/meta/tests/getpriority_spec 828
SEVERITY failed
MARKER Requirement failed: {getpriority.09.02}
COMMENT This happens inconsistently when testing on a virtual machine, and is still under investigation.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3927 | Bug 3927
RESOLUTION Known problem
WAIVE
END
### Problem Record #676
STANDARD LSB
TESTSUITE core < 5.0
TEST /tset/LSB.os/network/accept/T.accept 1
MARKER fcntl syscall returned error
TEST /tset/LSB.os/network/connect/T.connect 1
MARKER fcntl syscall returned error
COMMENT This is caused by a bug in the tests, which should be fixed with newer tests.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3957 | Bug 3957
RESOLUTION Test suite deficiency
WAIVE
END
### Problem Record #677
STANDARD LSB
TESTSUITE printing
TEST /convenience/cupsConvenience 11
MARKER unexpected signal 15 (SIGTERM) received
COMMENT This appears to be an interaction problem between newer CUPS versions and our test cupsd. It is still under investigation, but is almost certainly a test bug.
LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3964 | LSB bug 3964
RESOLUTION Test suite deficiency
WAIVE
END