test libstdc++.so.6 3052
expected_severity failed
marker Did not find symbol addr for Virtual table entry [0][4]
marker Did not find symbol name for Virtual table entry [0][4]
quell
resolution False positive
comment Test suite issue, virtual table entries are incorrect in the specification.
lsb_report_id 0071
lsb_resolution_id INT.0012
end

test libstdc++.so.6 3059
expected_severity failed
marker Did not find symbol addr for Virtual table entry [0][4]
marker Did not find symbol name for Virtual table entry [0][4]
quell
resolution False positive
comment Test suite issue, virtual table entries are incorrect in the specification.
lsb_report_id 0071
lsb_resolution_id INT.0012
end

test libstdc++.so.6 3401
expected_severity failed
marker Virtual Function[0][7] _ZNSt15basic_streambuf
marker showmanyc
quell
resolution False positive
comment Test suite issue, the basic_streambuf::showmanyc() method was reimplemented
comment in basic_streambuf instead of being inherited starting from gcc 4.0
lsb_report_id 0090
lsb_resolution_id TSD.0056
end

test libstdc++.so.6 3414
expected_severity failed
marker Virtual Function[0][7] _ZNSt15basic_streambuf
marker showmanyc
quell
resolution False positive
comment Test suite issue, the basic_streambuf::showmanyc() method was reimplemented
comment in basic_streambuf instead of being inherited starting from gcc 4.0
lsb_report_id 0090
lsb_resolution_id TSD.0056
end

test /demangle/abi_examples/01.cc 1
expected_severity failed
marker terminate called after throwing an instance of 'std::runtime_error'
marker what(): float
quell
resolution False positive
comment The ABI changed from the last version of the test, the test suite was not yet updated.
lsb_report_id 0080
lsb_resolution_id INT.0014
end

test /demangle/abi_examples/02.cc 1
expected_severity failed
marker terminate called after throwing an instance of 'std::runtime_error'
marker what(): float
quell
resolution False positive
comment The ABI changed from the last version of the test, the test suite was not yet updated.
lsb_report_id 0080
lsb_resolution_id INT.0014
end

test /24_iterators/istreambuf_iterator/1.cc 1
expected_severity failed
marker _24_iterators_istreambuf_iterator_1.exe
quell
resolution False positive
comment Probably a bug in test suite header files (works with normal header files).
lsb_report_id 0065
lsb_resolution_id TSD.0047
end

test /24_iterators/istreambuf_iterator/2.cc 1
expected_severity failed
marker _24_iterators_istreambuf_iterator_2.exe
quell
resolution False positive
comment Probably a bug in test suite header files (works with normal header files).
lsb_report_id 0079
lsb_resolution_id TSD.0053
end

test /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 8
expected_severity unreported
quell
resolution False positive
comment The 32-bit binary test fails on PPC64 because mprotect() modifies
comment permissions of some of the pages in the specified range even if
comment it later fails; the test does not take this into account.
lsb_report_id 0099
lsb_resolution_id TSD.0066
end

test /tset/POSIX.os/procenv/sysconf/T.sysconf 2
expected_severity failed
quell
marker sysconf(_SC_CHILD_MAX) did not return the value of CHILD_MAX
resolution False positive
comment The test seems to be incorrectly built with hard-wired value
comment of the CHILD_MAX constant.
comment Entered into LSB bugzilla as bug #1188.
lsb_report_id 0112
end

test /tset/LI18NUX2K.L1/utils/shell/T.shell 8
expected_severity failed
resolution Reported to LSB
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 Test suite bug suspected; reported to LSB bugzilla as bug #1151
lsb_report_id 0114
end

test /tset/LSB.pam/testcases/pam_start/pam_start 3
expected_severity failed
quell
resolution Debatable
marker pam_start returned System error for NULL conv structure
marker It was expected to return PAM_BUF_ERR.
comment It is unclear what should be returned, both error values
comment make sense.
comment Entered into LSB Bugzilla as bug #1281
lsb_report_id 0111
end


test Test comments Case-05 0
expected_severity failed
marker Case > still in comment --> | 05 |
resolution Wrong behaviour of the application
comment This is a contradiction with HTML standart, not LSB.
quell
end

test expect-1.3 0
expected_severity failed
marker expect -ex hi {set x 3}
resolution Test suite deficiency
comment Fixed, but only in further versions.
quell
lsb_report_id 0109
end

test /thread/pthread1.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end
test /thread/pthread2.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end
test /thread/pthread3.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end
test /thread/pthread4.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end
test /thread/pthread5.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end
test /thread/pthread6.cc 1
expected_severity unreported
resolution This bug is still under investigation
lsb_report_id 0083
end

test /tset/CH03/mprsd/mprsd 12
expected_severity unresolved
resolution This problem is because of runnig tests on Xvfb.
comment The test setup required to run the tests has been written to assume a live display or a virtual frame buffer with backing store,
comment even though an X server and/or xvfb are not required by the LSB. This is a method to test the X library functions.
comment Until recently the default xvfb had the backing store enabled, and this is expected to be reinstated. Its a one line change.
comment Future releases of the test suite might include a working xvfb binary.
lsb_report_id 0085
quell
end
test /tset/CH03/mpsbws/mpsbws 11
expected_severity unresolved
resolution This problem is because of runnig tests on Xvfb.
lsb_report_id 0085
quell
end
test /tset/CH03/mpsbws/mpsbws 12
expected_severity unresolved
resolution This problem is because of runnig tests on Xvfb.
lsb_report_id 0085
quell
end
test /tset/CH03/mpwdw/mpwdw 12
expected_severity unresolved
resolution This problem is because of runnig tests on Xvfb.
lsb_report_id 0085
quell
end
test /tset/CH03/mpwdw/mpwdw 13
expected_severity unresolved
resolution This problem is because of runnig tests on Xvfb.
lsb_report_id 0085
quell
end

test /tset/LSB.os/mfiles/msync_P/T.msync_P 7
expected_severity failed
resolution msync test fails if memory is mapped unexpectedly.
lsb_report_id 0010
quell
end

test /tset/CH02/vndrrls/vndrrls 1
expected_severity failed
marker XVendorRelease() returned 7
lsb_report_id 0122
resolution OK for Xserver 7.XX
comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX.
quell
end

test /tset/CH02/vndrrls/mvndrrls 1
expected_severity failed
marker VendorRelease() returned 7
lsb_report_id 0122
resolution OK for Xserver 7.XX
comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX.
quell
end

test /tset/LSB.fhs/root/bin/bin-tc 37
expected_severity failed
marker Unexpected output written to stdout
lsb_report_id 0015
resolution Test suite deficiency
comment The csh test checks for stdout output. In some cases stdout output from 
comment csh startup is normal. This includes emitting an escape sequence 
comment to ensure that the terminal is in Unicode mode. This escape sequence is 
comment not emitted if stdout is not a tty, so one could simply change the line:
comment   lsb_test_exec /bin/csh tfile >out.stdout 2>out.stderr
comment to:
comment   lsb_test_exec /bin/csh tfile >out.stdout 2>out.stderr < /dev/null
quell
end

test /tset/LSB.fhs/usr/share-misc/share-misc-tc 3
expected_severity failed
marker /usr/share/misc/magic: found a symlink
lsb_report_id 0020
resolution The test is too strict.
comment If the file is a symlink, the test result should be PASS.
quell
end

test /tset/LSB.fhs/usr/share-misc/share-misc-tc 3
expected_severity failed
marker /usr/share/misc/magic: file not found
lsb_report_id 0020
resolution This check is optional. Treat it as FIP.
comment /tset/LSB.fhs/usr/share-misc/share-misc-tc.3 checks for 
comment /usr/share/misc/magic. First, the FHS marks this as optional.
comment If it does not exist, the test result is FAIL, should be FIP.
quell
end

test /21_strings/char_traits/requirements/wchar_t/1.cc 1
expected_severity failed
marker DejaGNUTest.command_1: /opt/lsb/test/lib/qmtest_libstdcpp_3.4.3/_21_strings_char_traits_requirements_wchar_t_1.exe
marker DejaGNUTest.command_status_1: 11
marker DejaGNUTest.result_1: FAIL: 21_strings/char_traits/requirements/wchar_t/1.cc execution test
marker INFO: qmtest.cause: 21_strings/char_traits/requirements/wchar_t/1.cc execution test
lsb_report_id 0091
resolution Test suite deficiency
comment See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23550.
comment Also tracked here: http://bugs.linuxbase.org/show_bug.cgi?id=1069.
quell
end

test /tset/PTHR.os/thread/pthread_create/T.pthread_create 4
expected_severity unresolved
marker Posix Ref: Component PTHREAD_CREATE
marker Assertion 9945-1:1996 16.2.2.2-4(A)
marker waitpid() failed - errno 10 (ECHILD)
marker tet_fork, expected 0, got -1
lsb_report_id 0082
resolution Test suite deficiency
comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called.
quell
end

test /tset/PTHR.os/thread/pthread_create/T.pthread_create 11
expected_severity unresolved
marker Posix Ref: Component PTHREAD_CREATE
marker Assertion 9945-1:1996 16.2.1.2-11(A)
marker waitpid() failed - errno 10 (ECHILD)
marker tet_fork, expected 0, got -1
lsb_report_id 0103
resolution Test suite deficiency
comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called.
quell
end

test /tset/PTHR.os/thread/pthread_join/T.pthread_join 4
expected_severity unresolved
marker Posix Ref: Component PTHREAD_JOIN
marker Assertion 9945-1:1996 16.2.3.4-4(A)
marker waitpid() failed - errno 10 (ECHILD)
marker tet_fork, expected 0, got -1
lsb_report_id 0084
resolution Test suite deficiency
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.
quell
end

test Checking the port 80 0
expected_severity failed
marker httpd: Could not 
marker determine the server's fully qualified domain name, using
resolution Warning message
comment `apachectl' returns the error code 1, but it works normally.
quell
end

test httpold-4.12 0
expected_severity failed
marker set token [http_get $url -timeout 1 -command {lappend x fail}]		 
marker timeout ok 
lsb_report_id 0088
resolution Test suite deficiency
comment It is resolved by a newer tcl version and newer test suite.
quell
end

test /22_locale/locale/cons/12352.cc 1
expected_severity failed
comment It was decided that this test does not test any identifiable part of the specification, and should be removed.
lsb_report_id 0119
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.
quell
end

test /tset/LSB.os/ioprim/readv_L/T.readv_L 24
expected_severity failed
marker ERRNO VALUES: expected: 21 (EINVAL), observed: 14 (EFAULT)
lsb_report_id 0117
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).
quell
end

test LSB.os/ioprim/writev_L/T.writev_L 30
expected_severity failed
marker iov[0].iov_len = 1024
marker readv(5, iov, 1024) did not behave as expected
marker ERRNO VALUES: expected: 
marker (EINVAL)
marker observed:
marker (EFAULT)
lsb_report_id 0116
comment The test attempts to do a writev() call with sum of sizes I/O buffers larger than ssize_t, to test whether the call properly returns EINVAL. This however fails on 64-bit architectures because they have ssize_t so large that it is not possible to allocate a buffer of such size (2 TB). This causes the test to fail.
comment Reported to LSB bugzilla as bug #844
comment See also LSB bugzilla bug #6
quell
end

test /test/LSB.os/mfiles/mmap_P/T.mmap_P 23
expected_severity failed
marker vsrt_wait_for: Timed-out waiting for child to exit
lsb_report_id 0108
quell
end

test /tset/ANSI.os/streamio/fwrite 3
expected_severity unresolved
marker fwrite() on non-blocking pipe failed with errno set to EAGAIN
lsb_report_id 105
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.
quell
end

test /tset/LSB.os/ioprim/writev_L 13
expected_severity failed
marker writev() returned -1, expected > 0
lsb_report_id 105
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.
quell
end

test /tset/POSIX.os/ioprim/write 13
expected_severity failed
marker write() returned -1, expected > 0
lsb_report_id 105
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.
quell
end

test /tset/POSIX.os/procprim/sleep/T.sleep 1
expected_severity failed
marker sleep returned after 26 seconds instead of 25 seconds
lsb_report_id 104
quell
end

test libstdc++.so.6 3401
expected_severity failed
resolution It is expected waivers will be granted
comment See http://www.linux-foundation.org/en/TestPilot31#lsblibchk
end

test libstdc++.so.6 3414
expected_severity failed
resolution It is expected waivers will be granted
comment See http://www.linux-foundation.org/en/TestPilot31#lsblibchk
end


test /tset/LSB.os/genuts/ftw_L/T.ftw_L 4
expected_severity warning
marker FTW_SL
quell
resolution Insignificant
comment The linux ftw() function follows symlinks, it does not report them.
end

test /tset/ANSI.os/maths/pow/T.pow 4
expected_severity warning
marker pow(0.0, -1.0)
marker expected: -inf
marker observed: inf
quell
resolution Insignificant
comment Both -inf and +inf are equally artificial results, Linux libc picks this one.
end

test /tset/ANSI.os/streamio/fopen/T.fopen 28
expected_severity warning
marker fopen() succeeded
marker FOPEN_MAX streams
marker already open
quell
resolution Insignificant
comment FOPEN_MAX is just an advisory limit, there is probably no real limit except memory.
end

test /tset/POSIX.os/procprim/kill_X/T.kill_X 1
expected_severity warning
marker process calling kill()
marker did not receive signal
quell
resolution Insignificant
comment The Linux implementation of kill() sends the signal to everyone except its own process,
comment which is also logical.
end

test /tset/ANSI.os/streamio/remove_X/T.remove_X 1
expected_severity warning
marker expected: 26 (ETXTBSY)
marker observed: 0 (NO ERROR)
quell
resolution Feature
comment Linux allows to remove a running executable file without any side effects.
end

test /tset/ANSI.os/streamio/tmpfile/T.tmpfile 2
expected_severity warning
marker mode 0666
marker found 0600
quell
resolution Feature
comment Not a bug but feature. Linux tmpfile() creates files with access rights 0600
comment which is more secure than POSIX mandated 0666.
end

test /tset/POSIX.os/dataform/tar/T.tar 12
expected_severity fip
marker create utility exited with code 1
quell
resolution Correct
comment This test tries to call tar with a file with too long name (>100 chars).
comment The tar utility can either skip the file, or fail completely; both results
comment are correct.
end

test /tset/POSIX.os/devclass/c_iflag/T.c_iflag 19
expected_severity warning
marker This test will not pass when using pseudo ttys
quell
resolution Normal
comment This is a normal result unless a hardware terminal is used (which is very rare).
end

test /tset/POSIX.os/devclass/c_lflag/T.c_lflag 6
expected_severity warning
marker This test will not pass when using pseudo ttys
quell
resolution Normal
comment This is a normal result unless a hardware terminal is used (which is very rare).
end

test /tset/POSIX.os/devclass/tcdrain/T.tcdrain 2
expected_severity warning
marker This test will not pass when using pseudo ttys
quell
resolution Normal
comment This is a normal result unless a hardware terminal is used (which is very rare).
end

test /tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 8
expected_severity warning
marker This test will not pass when using pseudo ttys
quell
resolution Normal
comment This is a normal result unless a hardware terminal is used (which is very rare).
end

test /tset/POSIX.os/files/access_X/T.access_X 1
expected_severity warning
marker did not give correct results
marker expected: -1, observed: 0
marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
quell
resolution Feature
comment On Linux, running executable files are normally accessible.
end

test /tset/POSIX.os/files/rename_X/T.rename_X 1
expected_severity warning
marker did not give correct results
marker expected: -1, observed: 0
marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
quell
resolution Feature
comment Not a bug but feature. On Linux, running executable files are normally accessible.
end

test /tset/POSIX.os/files/stat_X/T.stat_X 1
expected_severity fip
marker stat("/dev/sda", buf)
marker returned st_rdev value of 0x800
quell
resolution Correct
comment This is a correct result, /dev/sda has major/minor number 0x0800.
end

test /tset/POSIX.os/files/stat_X/T.stat_X 2
expected_severity fip
marker stat("/dev/tty", buf)
marker returned st_rdev value of 0x500
quell
resolution Correct
comment This is a correct result, /dev/tty has major/minor number 0x0500.
end

test /tset/POSIX.os/files/unlink_X/T.unlink_X 1
expected_severity warning
marker did not give correct results
marker expected: -1, observed: 0
marker expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
quell
resolution Feature
comment On Linux, running executable files are normally accessible.
end

test /tset/POSIX.os/procenv/sysconf/T.sysconf 3
expected_severity warning
marker CLK_TCK not defined
quell
resolution Insignificant
comment Insignificant; CLK_TCK is obsolete anyway.
end

test /tset/LSB.os/procenv/chroot/T.chroot 4
expected_severity fip
marker execve() of ./chroot_t4
marker failed - errno 2 (ENOENT)
quell
resolution Correct
comment This is correct behavior. The ./chroot_t4 executable cannot be run
comment because the needed shared libraries are not present
comment in the chrooted environment.
end

test /tset/LSB.fhs/var/spool-lpd/spool-lpd-tc 2
expected_severity fip
marker /var/spool/lpd/lpd.lock:
marker file not found
quell
resolution Normal
comment Normal when lpd is not installed.
end

test /tset/LSB.fhs/var/spool-rwho/spool-rwho-tc 1
expected_severity fip
marker /var/spool/rwho:
marker directory not found
quell
resolution Normal
comment Normal when rwho is not installed.
end

test /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 17
expected_severity fip
marker sysconf(_SC_2_C_VERSION) returned -1
marker sysconf(_SC_XOPEN_ENH_I18N) returned 1
marker sysconf(_SC_XOPEN_SHM) returned 1
marker sysconf(_SC_XOPEN_LEGACY) returned 1
quell
resolution Correct
comment This is a typical result on Linux.
end

test /tset/LI18NUX2K.L1/utils/localedef/T.localedef 3
expected_severity warning
marker created locale unexpectedly
marker eixt code of localedef is 0
marker This test result is waived now.
quell
resolution Waived
comment This test is waived by the LSB committee.
end

test /tset/LSB.os/genuts/getopt/T.getopt 1
expected_severity warning
marker getopt() failed when called with :-
marker optstring : [ab:cd:e]
marker arguments : [-a] [-d]
marker getopt() failed on the following :-
marker optind : expected [4], actual [3]
marker arguments : [-ab]
marker optind : expected [3], actual [2]
quell
resolution Known minor bug
comment This is a known minor bug related to locale handling.
end


test /23_containers/bitset/cons/16020.cc 1
expected_severity warning
marker 23_containers/bitset/cons/16020.cc compilation failed
quell
resolution False positive
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).
end

test /23_containers/bitset/invalidation/1.cc 1
expected_severity warning
marker 23_containers/bitset/invalidation/1.cc compilation failed
quell
resolution False positive
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).
end

test /23_containers/bitset/operations/13838.cc 1
expected_severity warning
marker 23_containers/bitset/operations/13838.cc compilation failed
quell
resolution False positive
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).
end

test /backward/11460.cc 1
expected_severity warning
marker backward/11460.cc compilation failed to produce executable
quell
resolution False positive
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).
end

test /ext/enc_filebuf/char/13189.cc 1
expected_severity warning
marker ext/enc_filebuf/char/13189.cc compilation failed to produce
quell
resolution False positive
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).
end

test /ext/enc_filebuf/wchar_t/13189.cc 1
expected_severity warning
marker ext/enc_filebuf/wchar_t/13189.cc compilation failed to produce
quell
resolution False positive
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).
end

test /backward/strstream_members.cc 1
expected_severity warning
marker backward/strstream_members.cc compilation failed to produce
quell
resolution False positive
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).
end

test /23_containers/deque/invalidation/1.cc 1
expected_severity warning
marker 23_containers/deque/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/deque/invalidation/2.cc 1
expected_severity warning
marker 23_containers/deque/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/deque/invalidation/3.cc 1
expected_severity warning
marker 23_containers/deque/invalidation/3.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/deque/invalidation/4.cc 1
expected_severity warning
marker 23_containers/deque/invalidation/4.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/list/invalidation/1.cc 1
expected_severity warning
marker 23_containers/list/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/list/invalidation/2.cc 1
expected_severity warning
marker 23_containers/list/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/list/invalidation/3.cc 1
expected_severity warning
marker 23_containers/list/invalidation/3.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/list/invalidation/4.cc 1
expected_severity warning
marker 23_containers/list/invalidation/4.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/map/insert/16813.cc 1
expected_severity warning
marker 23_containers/map/insert/16813.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/map/invalidation/1.cc 1
expected_severity warning
marker 23_containers/map/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/map/invalidation/2.cc 1
expected_severity warning
marker 23_containers/map/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/multimap/invalidation/1.cc 1
expected_severity warning
marker 23_containers/multimap/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/multimap/invalidation/2.cc 1
expected_severity warning
marker 23_containers/multimap/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/multiset/invalidation/1.cc 1
expected_severity warning
marker 23_containers/multiset/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/multiset/invalidation/2.cc 1
expected_severity warning
marker 23_containers/multiset/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/set/invalidation/1.cc 1
expected_severity warning
marker 23_containers/set/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/set/invalidation/2.cc 1
expected_severity warning
marker 23_containers/set/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/vector/invalidation/1.cc 1
expected_severity warning
marker 23_containers/vector/invalidation/1.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/vector/invalidation/2.cc 1
expected_severity warning
marker 23_containers/vector/invalidation/2.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/vector/invalidation/3.cc 1
expected_severity warning
marker 23_containers/vector/invalidation/3.cc compilation failed to
quell
resolution False positive
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).
end

test /23_containers/vector/invalidation/4.cc 1
expected_severity warning
marker 23_containers/vector/invalidation/4.cc compilation failed to
quell
resolution False positive
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).
end

test /tset/Xlib3/vndrrls/MTest 1
expected_severity fip
marker REPORT: VendorRelease() returned 60900000 instead of 40201001.
resolution Correct answer for X.Org 6.9
comment This answer is correct provided that the X server is X.org 6.9.
quell
end

test /tset/Xlib3/vndrrls/Test 1
expected_severity fip
marker REPORT: XVendorRelease() returned 60900000 instead of 40201001.
resolution Correct answer for X.Org 6.9
comment This answer is correct provided that the X server is X.org 6.9.
quell
end

test /tset/Xlib3/srvrvndr/MTest 1
expected_severity fip
marker REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation"
marker REPORT: Observed value "The X.Org Foundation"
resolution Correct answer for X.Org-based X server
comment This answer is correct provided that the X server is X.Org-based.
quell
end

test /tset/Xlib3/srvrvndr/Test 1
expected_severity fip
marker REPORT: Expected value "The XFree86 Project, Inc:The X.Org Foundation"
marker REPORT: Observed value "The X.Org Foundation"
resolution Correct answer for X.Org-based X server
comment This answer is correct provided that the X server is X.Org-based.
quell
end

####################

test /tset/Xlib14/vcnlist/Test 2
expected_severity failed
resolution Test suite bug
marker REPORT: Returned value does not match expected value for foreground
marker REPORT: returned 0
marker REPORT: expected 1
marker TRACE: background
marker CHECK: XVaCreateNestedList-2 7, line 673
comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla
end

test /tset/Xlib14/vcnlist/Test 3
expected_severity failed
resolution Test suite bug
marker REPORT: Returned value does not match expected value for foreground
marker REPORT: returned 0
marker REPORT: expected 1
marker TRACE: background
comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla
end

test /tset/Xlib14/vcnlist/Test 4
expected_severity failed
resolution Test suite bug
marker 4
marker 5
marker TRACE: foreground
marker REPORT: Returned value does not match expected value for foreground
marker REPORT: returned 0
marker REPORT: expected 1
marker 5
marker TRACE: background
comment Bug in test suite (code not 64-bit safe), see bug #1365 in LSB bugzilla and bug #176078 in SuSE bugzilla
end


test /tset/Xlib13/allwevnts/Test 20
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xlib13/allwevnts/Test 24
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xlib17/gtdflt/Test 5
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xt11/tcalbrcrl/Test 1
expected_severity unresolved
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xt8/tmkgmreqt/Test 4
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xt8/tmkrsizrt/Test 4
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xlib17/gtdflt/Test 5
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end

test /tset/Xlib13/stpntrmppn/Test 3
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
end
