# Problem Database
# Version 2.5 2008-04-29

# LSB 3.0
test libstdc++.so.6 3052
expected_severity failed
marker Did not find symbol addr for Virtual table entry [0][4]
marker Did not find symbol name for Virtual table entry [0][4]
comment Test suite issue, virtual table entries are incorrect in the specification.
lsb_report_id 0071
resolution Test suite deficiency
quell
dup libstdc++.so.6 3059
end

# LSB 3.0
test /24_iterators/istreambuf_iterator/2.cc 1
expected_severity failed
marker _24_iterators_istreambuf_iterator_2.exe
comment Probably a bug in test suite header files (works with normal header files).
comment The same problems are PR 0065 and PR 0095
#lsb_report_id 0065
#lsb_report_id 0095
#lsb_report_id 0129
lsb_report_id 0079
resolution Test suite deficiency
quell
end

# LSB 3.0
test /demangle/abi_examples/01.cc 1
expected_severity failed
marker terminate called after throwing an instance of 'std::runtime_error'
marker what(): float
comment The ABI changed from the last version of the test, the test suite was not yet updated.
lsb_report_id 0080
#lsb_report_id 0130
resolution Test suite deficiency
quell
dup /demangle/abi_examples/02.cc 1
end

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

# LSB 3.0
test /thread/pthread1.cc 1
expected_severity unreported
lsb_report_id 0083
resolution Withdrawn
quell
dup /thread/pthread2.cc 1
dup /thread/pthread3.cc 1
dup /thread/pthread4.cc 1
dup /thread/pthread5.cc 1
dup /thread/pthread6.cc 1
end

# LSB 3.0
test /tset/PTHR.os/thread/pthread_join/T.pthread_join 4
expected_severity unresolved
marker Posix Ref: Component PTHREAD_JOIN
marker Assertion 9945-1:1996 16.2.3.4-4(A)
marker waitpid() failed - errno 10 (ECHILD)
marker tet_fork, expected 0, got -1
comment There is a race condition in these tests, as the detached thread could exit before pthread_join() is called.
comment See also Problem Report #102.
#lsb_report_id 0102
lsb_report_id 0084
resolution Test suite deficiency
quell
end

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

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

# LSB 3.0
test /tset/POSIX.os/procprim/sigconcept/T.sigconcept 41
expected_severity unresolved
marker unexpected signal 15 (SIGTERM) received
comment Bugzilla 1065 highlights a possible timing error in this test case and has been accepted as a test suite deficiency. A patch has been proposed with bugzilla 1065 to address this.
comment http://bugs.linuxbase.org/show_bug.cgi?id=1065
comment See also PR 0094, PR 0093
#lsb_report_id 0093
#lsb_report_id 0094
lsb_report_id 0089
resolution Test suite deficiency
quell
end

# LSB 3.0
test libstdc++.so.6 3401
expected_severity failed
marker _ZNSt15basic_streambuf
marker showmanyc
comment Test suite issue, the basic_streambuf::showmanyc() method was reimplemented
comment in basic_streambuf instead of being inherited starting from gcc 4.0
lsb_report_id 0090
#lsb_report_id 0127
resolution Test suite deficiency
quell
dup libstdc++.so.6 3414
end

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

# LSB 3.0
test /tset/LSB.os/jump/makecontext/T.makecontext 1
expected_severity unresolved
marker child process timed out
comment The problem is the following: /* Save context area */ oucp = ucp; ucontext_t on PPC32 contains pointer into the struct itself. So, after this, the pointers will show to the wrong place. If you removes this line and add instead: + getcontext(&oucp); rval = getcontext(&ucp); a second getcontext call, it works.
comment See also PR 0067
#lsb_report_id 0067
lsb_report_id 0092
resolution Test suite deficiency
quell
dup /tset/LSB.os/jump/makecontext/T.makecontext 3
end

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

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

# LSB 3.0
test /tset/POSIX.os/procprim/sleep/T.sleep 1
expected_severity failed
marker sleep returned after 26 seconds instead of 25 seconds
comment See also PR 0096
#lsb_report_id 0096
lsb_report_id 0104
resolution Test suite deficiency
quell
end

# LSB 3.0
test /tset/ANSI.os/streamio/fwrite 3
expected_severity unresolved
marker fwrite() on non-blocking pipe failed with errno set to EAGAIN
comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem.
lsb_report_id 0105
resolution Test suite deficiency
quell
end
test /tset/LSB.os/ioprim/writev_L 13
expected_severity failed
marker writev() returned -1, expected > 0
comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem.
lsb_report_id 0105
resolution Test suite deficiency
quell
end
test /tset/POSIX.os/ioprim/write 13
expected_severity failed
marker write() returned -1, expected > 0
comment The test depends on a pipe unblocking when PIPE_BUF bytes are read from it. On Linux, this happens when the kernel's PAGE_SIZE setting is equal to PIPE_BUF, or on kernels 2.6.9 or earlier. On architectures where PAGE_SIZE is a multiple of PIPE_BUF (ia64 being notable among them) with kernel 2.6.10 or later, the pipe will not unblock under many circumstances after PIPE_BUF bytes are read. A patch to change this behavior was rejected by Linus Torvalds. Bug #1100 in the LSB Test bug tracker refers to this problem.
lsb_report_id 0105
resolution Test suite deficiency
quell
end

# LSB 1.3
test /test/LSB.os/mfiles/mmap_P/T.mmap_P 23
expected_severity failed
marker vsrt_wait_for: Timed-out waiting for
marker child to exit
comment This is an S390 issue
lsb_report_id 0108
resolution Regression
end

# LSB 3.0
test expect-1.3 0
expected_severity failed
marker expect -ex hi {set x 3}
comment See LSB Bugzilla #1116
lsb_report_id 0109
resolution Test suite deficiency
quell
end

# LSB 3.0
test /tset/LSB.os/mfiles/msync_P/T.msync_P 5
expected_severity failed
lsb_report_id 0110
resolution Test suite deficiency
quell
dup /tset/ANSI.os/streamio/freopen/T.freopen 17
dup /tset/LSB.os/ipc/msgget/T.msgget 2
dup /tset/LSB.os/ipc/msgget/T.msgget 3
end

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

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

# LSB 3.0
test /tset/LI18NUX2K.L1/base/setlocale/T.setlocale 1
expected_severity failed
marker path tracing error: path counter
comment The /tset/LI18NUX2K.L1/base/setlocale/T.setlocale{1,2} tests fail, reporting that the LC_CTYPE setting is not honored, when the iswxdigit() call returns a nonzero value different from 1 when applied on a digit. As the POSIX specs do not mandate the exact value, only the nonzero-ness, this test is overly strict. 
comment Reported to LSB Bugzilla as bug #1151 (http://bugs.linuxbase.org/show_bug.cgi?id=1151) and fixed for LSB 3.1.
lsb_report_id 0113
resolution Test is too strict
quell
dup /tset/LI18NUX2K.L1/base/setlocale/T.setlocale 2
end

# LSB 3.0
test /tset/LI18NUX2K.L1/utils/shell/T.shell 8
expected_severity failed
marker test shell: bash
marker diff is 1c1 < 0 1 2 3 4 a b c z - --- > 0 1 2 3 4 a b c z [[:hyphen:]]
marker examined '[[:xdigit:]] [[:hyphen:]]'
marker expected '0 1 2 3 4 a b c z -'
marker in the locale LC_CTYPE = LTP_1.UTF-8
marker [[:xdigit:]] should contain 'z'('Z')
marker [[:hyphen:]] should be '-'
comment This test tries to create a file named '-' and then match it against a character class. However, it issues an incorrect command "touch -" which does not do what was expected. Reported to LSB Bugzilla as part of bug #1151 (please see comment #7 and following), fixed for LSB 3.1.
comment LSB Bug #1151 tracks this. A patch has been developed. This is a test suite deficiency.
comment http://bugs.linuxbase.org/show_bug.cgi?id=1151
lsb_report_id 0114
resolution Test suite deficiency
quell
end

# LSB 3.0
test libpam.so.0 15
expected_severity failed
marker ((unversioned))
comment The lsblibcheck tool does not expect symbols in libpam to be versioned,
comment so it fails on every such symbol. Reported to LSB bugzilla as bug #1122
comment and fixed for LSB 3.1.
lsb_report_id 0115
resolution Test suite deficiency
quell
dup libpam.so.0 16
dup libpam.so.0 17
dup libpam.so.0 18
dup libpam.so.0 19
dup libpam.so.0 20
dup libpam.so.0 21
dup libpam.so.0 22
dup libpam.so.0 23
dup libpam.so.0 24
dup libpam.so.0 25
dup libpam.so.0 26
dup libpam.so.0 27
end

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

# LSB 3.0
test /tset/LSB.os/ioprim/readv_L/T.readv_L 24
expected_severity failed
marker ERRNO VALUES: expected: 21 (EINVAL), observed: 14 (EFAULT)
comment The test fails after trying to do a readv() with the sum of buffers larger than ssize_t (the 64-bit architecture has ssize_t so large that it is not possible to create a buffer so large that it would overflow).
lsb_report_id 0117
#lsb_report_id 0143
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/CH02/clsdsply/clsdsply 8
expected_severity Unreported
comment The clsdsply.8 test crashes (glibc reports memory corruption) when run with a Xvfb server with Rui Feng's patch (which fixes failures with overlong requests and deadlock on rprntwdw test).
lsb_report_id 0118
resolution Test suite deficiency
quell
end

# LSB 3.1
test /22_locale/locale/cons/12352.cc 1
expected_severity failed
comment It was decided that this test does not test any identifiable part of the specification, and should be removed.
comment It is the sense of the SA that this failure, while not perhaps a violation of the LSB specification, may possibly cause QA problems for any distribution which sees it, and should thus be taken seriously.
lsb_report_id 0119
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/CH02/vndrrls/vndrrls 1
expected_severity failed
marker XVendorRelease() returned 7
comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX.
comment See also bug 1339 in the Bugzilla: http://bugs.linuxbase.org/show_bug.cgi?id=1339
lsb_report_id 0122
#lsb_report_id 0123
#lsb_report_id 0124
resolution OK for Xserver 7.XX
quell
end
test /tset/CH02/vndrrls/mvndrrls 1
expected_severity failed
marker VendorRelease() returned 7
comment The lsb-vsw4-test suites is targeted to the Xserver 4.XX or 6.XX, but your system seemingly uses Xserver 7.XX.
comment See also bug 1339 in the Bugzilla: http://bugs.linuxbase.org/show_bug.cgi?id=1339
lsb_report_id 0122
#lsb_report_id 0123
#lsb_report_id 0124
resolution OK for Xserver 7.XX
quell
end

# LSB 3.1
test libX11.so.6 478
expected_severity failed
marker Did not find Xau
marker ((unversioned)) in libX11.so.6
comment Bug 1330: http://bugs.linuxbase.org/show_bug.cgi?id=1330
lsb_report_id 0125
#lsb_report_id 0126
#lsb_report_id 0128
resolution Test suite deficiency
quell
dup libX11.so.6 479
dup libX11.so.6 480
dup libX11.so.6 481
end

test /tset/LSB.os/genuts/nftw/T.nftw 9
expected_severity failed
lsb_report_id 0132
resolution Known problem
dup /tset/LSB.os/mfiles/msync_P/T.msync_P 7
end

test /22_locale/locale/cons/12438.cc 1
expected_severity failed
marker St9bad_alloc
lsb_report_id 0133
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/PTHR.os/threadattr/pthread_attr_getstacksize/T.pthread_attr_getstacksize 1
expected_severity failed
comment This failure is caused by VSTH_VALID_STACKSIZE=16384 which is too small
comment for ppc{32,64} in glibc-2.5, due to the decision to go with 64KB pages.
lsb_report_id 0134
resolution Test suite deficiency
quell
dup /tset/PTHR.os/threadattr/pthread_attr_setstacksize/T.pthread_attr_setstacksize 2
end

# LSB 3.1
test /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r 1
expected_severity failed
marker The system does not support the PTHREAD_SCOPE_PROCESS
lsb_report_id 0137
resolution Known problem
dup /tset/PTHR.os/procenv/getlogin_r/T.getlogin_r 2
end

# LSB 3.1
test /tset/POSIX.os/procenv/getlogin/T.getlogin 1
expected_severity failed
marker getlogin() returned failed - errno 2 (ENOENT)
resolution Known problem
lsb_report_id 0138
end

# LSB 3.1
test /tests/functions/GdkProperties/GdkProperties 5
expected_severity failed
marker gdk_atom_name: doesnt match the expected string
comment The test should not intern a random atom and expect to always get
comment the same number back from the X server.
lsb_report_id 0139
resolution Test suite deficiency
quell
end
test /tests/functions/GdkProperties/GdkProperties 11
expected_severity failed
marker gdk_atom_intern: not a expected atom
comment The test should not intern a random atom and expect to always get
comment the same number back from the X server.
lsb_report_id 0139
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tests/functions/GtkTreeStore/GtkTreeStore 53
expected_severity failed
marker iter_valid = 1, should be 0
comment GtkTreeView never guarantees that certain operations do invalidate an iter.
comment It only guarantees that certain operations do not invalide an iter.
comment So checking an iter for being invalid is not a meaningful test.
lsb_report_id 0140
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/LI18NUX2K.L1/base/getwchar/T.getwchar 3
expected_severity failed
marker path tracing error: path counter 0, expected 1
lsb_report_id 0141
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tests/functions/GtkContainer/GtkContainer 65
expected_severity unreported
comment See also LSB Bugzilla #1551.
lsb_report_id 0142
resolution Known problem
#rejected
end

# LSB 3.1
test /tset/ANSI.os/genuts/free/T.free 1
expected_severity failed
marker failed to reuse freed memory in next 1000 malloc() calls
lsb_report_id 0145
resolution Test suite deficiency
quell
end

# LSB 3.1
test libstdc++.so.6 4003
expected_severity failed
marker 0x80ee24a078
lsb_report_id 0146
resolution Test suite deficiency
quell
end
#
test libstdc++.so.6 4010
expected_severity failed
marker 0x80ee246af8
lsb_report_id 0146
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/LSB.os/genuts/nftw/T.nftw 5
expected_severity failed
marker ftw(".", ..., 3) returned -1 instead of 0
marker function set by ftw() not called for
marker ./ftwD2/ftw_d.3/ftw_t.7
marker function set by ftw() not called for ./ftwD2/ftw_d.3
lsb_report_id 0147
resolution Test suite deficiency
quell
end

# LSB 3.0
test libstdc++.so.6 3079
expected_severity failed
marker _ZNKSt9exception4whatEv (expected) doesn't match _ZNKSt10bad_typeid4whatEv (found)
lsb_report_id 0148
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/POSIX.os/procenv/sysconf_X/T.sysconf_X 2
expected_severity failed
marker sysconf(_SC_XOPEN_VERSION)
marker got 600
lsb_report_id 0149
resolution Test suite deficiency
quell
end

# LSB 3.1
test /tset/CH05/crtclrmp/crtclrmp 11
expected_severity failed
marker Received error type BadMatch
marker Got BadMatch, Expecting BadValue
lsb_report_id 0150
comment Upstream Xorg has evidently changed an error value from BadValue to BadMatch. As noted in bug 1589, this is probably an unreasonable expectation from the test, and at any rate now differs from upstream's behavior. It's likely that, as distributions move to newer versions of Xorg, more of them will start seeing this.
comment See Bug #1589 in the LSB Bugzilla.
comment See also TestPilot 3.1.1: http://www.linux-foundation.org/en/TestPilot311#lsb-test-vsw4
end

# LSB 3.1
test /tset/CH10/crtimg/crtimg 1
expected_severity unresolved
marker XCreateImage() returned NULL
lsb_report_id 0151
comment Under certain circumstances, it's possible for XCreateImage to return NULL, but the test does not allow for this. A patch has been applied to fix both xts5 and vsw4 (see bug 1693), but some testers are still seeing this.
comment See Bug #1693 in the LSB Bugzilla.
end

# ---

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

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

test /tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5
expected_severity failed
marker pam_authenticate returned Authentication failure when expected to succeed
marker euid : 0
comment This test fails because Test Execution Framework hacks PAM in order to let vsx0 user do super-user's actions without asking for password. 
comment The details haven't been explored, but this failure doesn't appear if the test runned without DTK Manager.
resolution TEF's fault
quell
end

# ---

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


test /23_containers/bitset/cons/16020.cc 1
expected_severity warning
marker compilation failed
comment Test executable was not correctly compiled when the test was built.
comment (No compilation is done during the test phase so it cannot fail).
resolution False positive
quell
dup /23_containers/bitset/invalidation/1.cc 1
dup /23_containers/bitset/operations/13838.cc 1
dup /backward/11460.cc 1
dup /ext/enc_filebuf/char/13189.cc 1
dup /ext/enc_filebuf/wchar_t/13189.cc 1
dup /backward/strstream_members.cc 1
dup /23_containers/deque/invalidation/1.cc 1
dup /23_containers/deque/invalidation/2.cc 1
dup /23_containers/deque/invalidation/3.cc 1
dup /23_containers/deque/invalidation/4.cc 1
dup /23_containers/list/invalidation/1.cc 1
dup /23_containers/list/invalidation/2.cc 1
dup /23_containers/list/invalidation/3.cc 1
dup /23_containers/list/invalidation/4.cc 1
dup /23_containers/map/insert/16813.cc 1
dup /23_containers/map/invalidation/1.cc 1
dup /23_containers/map/invalidation/2.cc 1
dup /23_containers/multimap/invalidation/1.cc 1
dup /23_containers/multimap/invalidation/2.cc 1
dup /23_containers/multiset/invalidation/1.cc 1
dup /23_containers/multiset/invalidation/2.cc 1
dup /23_containers/set/invalidation/1.cc 1
dup /23_containers/set/invalidation/2.cc 1
dup /23_containers/vector/invalidation/1.cc 1
dup /23_containers/vector/invalidation/2.cc 1
dup /23_containers/vector/invalidation/3.cc 1
dup /23_containers/vector/invalidation/4.cc 1
end

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

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

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

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

test /tset/POSIX.os/ioprim/write/T.write 13
expected_severity failed
marker returned -1, expected > 0
marker errno was set to 11 (EAGAIN)
comment This problem was faced earlier.
comment See http://osdir.com/ml/linux.debian.ports.ia64/2005-10/msg00004.html
dup /tset/LSB.os/ioprim/writev_L/T.writev_L 13
end

test /tset/POSIX.os/procprim/exec/T.execl 30
expected_severity failed
resolution May be a known problem
comment See, http://bugs.linuxbase.org/show_bug.cgi?id=1827;
comment More details at http://lkml.org/lkml/2008/2/27/164;
comment Please, send this journal to linux@ispras.ru. We need more details on this problem but can't reproduce the bug. Thank you.
dup /tset/POSIX.os/procprim/exec/T.execle 30
dup /tset/POSIX.os/procprim/exec/T.execlp 30
dup /tset/POSIX.os/procprim/exec/T.execv 30
dup /tset/POSIX.os/procprim/exec/T.execve 30
dup /tset/POSIX.os/procprim/exec/T.execvp 30
dup /tset/POSIX.os/procprim/fork/T.fork 18
end

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

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

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

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


test /tset/Xlib13/allwevnts/Test 20
expected_severity failed
resolution Appears in multiple distros
comment Same failure was reported 2006-02-09 in Fedora Core 5 T2 under VMWare, 
comment see http://lists.freestandards.org/pipermail/lsb-desktop/2006-February/000345.html
dup /tset/Xlib13/allwevnts/Test 24
dup /tset/Xt11/tcalbrcrl/Test 1
dup /tset/Xt8/tmkgmreqt/Test 4
dup /tset/Xt8/tmkrsizrt/Test 4
dup /tset/Xlib17/gtdflt/Test 3
dup /tset/Xlib17/gtdflt/Test 5
end

test libX11.so.6 478
expected_severity failed
resolution The LSB disposition of this failure is not yet determined
comment http://www.linux-foundation.org/en/TestPilot31#lsblibchk
comment These tests are likely to fail on an X.org 7.0 or later release.
comment The problem is four interfaces that have moved from libX11 to libXau: XauDisposeAuth, XauFileName, XauGetBestAuthByAddr, XauReadAuth. As written, the LSB 3.1 spec still requires these to be present in libX11.
comment See bug 1330: http://bugs.linuxbase.org/show_bug.cgi?id=1330
dup libX11.so.6 479
dup libX11.so.6 480
dup libX11.so.6 481
end

test /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 5
expected_severity failed
resolution These failures occur with cpio 2.6. There is a patch to fix this problem.
comment http://www.linux-foundation.org/en/TestPilot31#cpio
comment These failures occur with cpio 2.6. They are the result of a build system glitch in cpio, where the build system fails to properly detect the presence of the setlocale() function and disables it.
comment There is a patch to cpio to fix this problem, follow the link above.
comment Also see Debian bug 381348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381348
dup /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 6
dup /tset/LI18NUX2K.L1/utils/cpio-fh/T.cpio-fh 7
end

test /tset/PTHR.os/procenv/ttyname_r/T.ttyname_r 2
expected_severity failed
resolution There are patches to glibc for Mandriva 2007.0, that could help.
comment relevant patches to glibc look to be be here: http://sourceware.org/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/ttyname_r.c.diff?r1=1.17&r2=1.18&cvsroot=glibc http://sourceware.org/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/ttyname.c.diff?r1=1.20&r2=1.21&cvsroot=glibc
comment See: http://www.linux-foundation.org/en/TestPilot31#lsb-runtime-test_on_Mandriva_2007.0.2C_Cooker
end

#############################
# Known problems revealed by the Desktop-t2c tests

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 46
expected_severity failed
resolution Known problem (waived)
marker g_main_context_check: sources with higher numerical priority than specified are being checked.
comment This failure occurs due to the following problem:<br/>
comment The "g_main_context_check" interface ignores it's "max_priority" parameter.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0004">here</a>.
quell
end

test /glib-t2c/tests/glib_hooks/glib_hooks 3
expected_severity unresolved
resolution Known problem
marker g_hook_free
marker unexpected signal 11 (SIGSEGV) received
comment This failure occurs due to the following problem:<br/>
comment Invocation of the interface "g_hook_free" fails in certain conditions.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0002">here</a>.
end

test /glib-t2c/tests/glib_unicode/glib_unicode 39
expected_severity unresolved
resolution Known problem
marker Child process calling 'g_utf8_strreverse' died unexpectedly.
comment This failure occurs due to the following problem:<br/>
comment Invocation of the interface "g_utf8_strreverse" crashes for certain input values.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0022">here</a>.
end

test /glib-t2c/tests/glib_automatic_string_completion/glib_automatic_string_completion 11
expected_severity unresolved
resolution Known problem
marker g_completion_complete_utf8
marker unexpected signal 11 (SIGSEGV) received
comment This failure occurs due to the following problem:<br/>
comment Invocation of the interface "g_completion_complete_utf8" with certain values causes an abnormal termination with SIGSEGV signal.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0019">here</a>.
end

test /atk-t2c/tests/AtkObject_relation/AtkObject_relation 6
expected_severity failed
resolution Known problem (waived)
marker atk_object_remove_relationship
marker Function shouldn't delete other relationships
comment This failure occurs due to the following problem:<br/>
comment atk_object_remove_relationship can remove more relationships than it should.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0568">here</a>.
quell
dup /atk-t2c/tests/AtkObject_relation/AtkObject_relation 7
end

test /atk-t2c/tests/AtkHyperlink/AtkHyperlink 19
expected_severity failed
resolution Known problem (waived)
marker Value of property should coincide with value returned by atk_hyperlink_get_start_index.
marker {start_index.05}
comment This failure occurs due to the following problem:<br/>
comment Incorrect registration of the "start-index" property for AtkHyperlink.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0572">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 36
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation "g_key_file_has_key".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0036">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 60
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_get_boolean".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0032">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 64
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_get_integer".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0056">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 76
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_get_locale_string_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0033">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 83
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_get_boolean_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0055">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 87
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_get_integer_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0034">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 88
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker get comment failed: expected value = "Fourth Comment", returned value = "Fourth Comment
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0025">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 89
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker get comment from above group failed: expected value = "Third Comment", returned value = "Third Comment
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0025">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 90
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker get comment from above first group failed: expected value = "First Comment", returned value = "First Comment
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0025">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 101
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_set_boolean".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0035">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 104
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation "g_key_file_set_integer".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0037">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 110
expected_severity failed
resolution Known problem (waived)
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation "g_key_file_set_locale_string_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0038">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 113
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation of the interface "g_key_file_set_boolean_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0057">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 116
expected_severity failed
resolution Known problem (waived)
marker Error reported in glib_key_parser.c
marker If group_name is NULL
comment This failure occurs due to the following problem:<br/>
comment Inconsistency between standard and implementation "g_key_file_set_integer_list".<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0039">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 117
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker set comment = "comment 1" get comment = "comment 1
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0025">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 118
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker set comment = "comment 2" get comment = "#comment 2"
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_set_comment" interface prepends '#' character to the comment.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0026">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 119
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: g_key_file_new.01
marker set comment = "comment 3" get comment = "comment 3
comment This failure occurs due to the following problem:<br/>
comment The "g_key_file_get_comment" interface returns comment with unexpected new line symbol at the end.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0025">here</a>.
quell
end

test /glib-t2c/tests/glib_key_parser/glib_key_parser 125
expected_severity failed
resolution Known problem (waived)
marker Checked requirements: 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:<br/>
comment Invocation of the interface "g_key_file_remove_comment" does not remove comment in specific case.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0027">here</a>.
quell
end

test /atk-t2c/tests/AtkUtils/AtkUtils 5
expected_severity failed
resolution Known problem (waived)
marker should return 0 on failure.
comment This failure occurs due to the following problem:<br/>
comment atk_add_global_event_listener, atk_add_key_event_listener return incorrect value in case of error.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0579">here</a>.
quell
dup /atk-t2c/tests/AtkUtils/AtkUtils 8
end

test /atk-t2c/tests/AtkStateSet/AtkStateSet 24
expected_severity failed
resolution Known problem (waived)
marker When called for empty sets, the function should return NULL.
marker But it returned
comment This failure occurs due to the following problem:<br/>
comment atk_state_set_or_sets returns an empty set rather than NULL.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0574">here</a>.
quell
end

test /atk-t2c/tests/AtkObject_signals/AtkObject_signals 16
expected_severity failed
resolution Known problem (waived)
marker The signal "property-change" should be emitted when an object's property value changes.
comment This failure occurs due to the following problem:<br/>
comment "property-change" signal is not always emitted when the value of the "accessible-role" property changes.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0570">here</a>.
quell
end

test /atk-t2c/tests/AtkObject_properties/AtkObject_properties 4
expected_severity failed
resolution Known problem (waived)
marker Initial value of the role is
marker Value of the property should be 0 just after creation of an object.
comment This failure occurs due to the following problem:<br/>
comment "accessible-role" - invalid default value.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0569">here</a>.
quell
end

test /atk-t2c/tests/AtkRelationSet/AtkRelationSet 10
expected_severity failed
resolution Known problem (waived)
marker should not add a relation to the set if the relation is already present in it.
comment This failure occurs due to the following problem:<br/>
comment atk_relation_set_add always adds relation to the set.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0573">here</a>.
quell
end

test /glib-t2c/tests/glib_thread_pools/glib_thread_pools 13
expected_severity unresolved
resolution Known problem
marker Checked requirements: g_thread_pool_free.01
marker Checked requirements: g_thread_pool_free.04.02
marker Checked requirements: g_thread_pool_free.03
marker Checked requirements: g_thread_pool_free.02.01
marker Error reported in glib_thread_pools.c
comment This failure occurs due to the following problem:<br/>
comment Invocation of the interface "g_thread_pool_free" with certain values causes an error.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0024">here</a>.
end

test /gmodule-t2c/tests/gmodule/gmodule 11
expected_severity failed
resolution Known problem (waived)
marker gmodule-t2c/testdata/gmodule/open/la1/test.la
comment This failure occurs due to the following problem:<br/>
comment g_module_open fails to open modules with ".la" extension.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0575">here</a>.
quell
end

test /gmodule-t2c/tests/gmodule/gmodule 23
expected_severity failed
resolution Known problem (waived)
marker Error occurs in g_module_open, but g_module_error doesn't reveal it.
comment This failure occurs due to the following problem:<br/>
comment g_module_error returns NULL after g_module_open has failed to open a module with ".la" extension.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0576">here</a>.
quell
end

test /atk-t2c/tests/AtkObject_properties/AtkObject_properties 16
expected_severity failed
resolution Known problem (waived)
marker Type of property should be gdouble.
comment This failure occurs due to the following problem:<br/>
comment Spurious gdouble in "accesible-value" property of an AtkObject.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0596">here</a>.
quell
end

test /glib-t2c/tests/glib_memchunks/glib_memchunks 1
expected_severity failed
resolution Known problem (waived)
comment Memory chunks are deprecated since glib version 2.10.<br/>
quell
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 2
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 3
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 4
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 5
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 6
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 7
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 8
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 9
dup /glib-t2c/tests/glib_memchunks/glib_memchunks 10
end

test /fontconfig-t2c/tests/FcPattern/FcPattern 57
expected_severity unresolved
resolution Known problem
#marker Abnormal child process termination
comment This failure occurs due to the following problem:<br/>
comment Crash after FcPatternAdd is called several times.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0601">here</a>.
end

test /fontconfig-t2c/tests/FcFontSet/FcFontSet 11
expected_severity unresolved
resolution Known problem
marker FcFontSetSort
comment This failure may occur in fontconfig versions older that 2.4. FcFontSetSort() causes segmentation fault.<br/>
comment The reason is probably incorrect handling of csp parameter of FcFontSetSort() when csp is NULL.<br/>
end

test /glib-t2c/tests/glib_random/glib_random 9
expected_severity failed
resolution FIP
comment There is no criteria out there that can guarantee that the numbers from a sequence are uniformly distributed random values.<br/>
comment There is always probability for any criterion to return wrong result.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_random/glib_random 10
dup /glib-t2c/tests/glib_random/glib_random 11
dup /glib-t2c/tests/glib_random/glib_random 12
dup /glib-t2c/tests/glib_random/glib_random 13
dup /glib-t2c/tests/glib_random/glib_random 14
dup /glib-t2c/tests/glib_random/glib_random 15
dup /glib-t2c/tests/glib_random/glib_random 16
dup /glib-t2c/tests/glib_random/glib_random 17
dup /glib-t2c/tests/glib_random/glib_random 18
dup /glib-t2c/tests/glib_random/glib_random 19
dup /glib-t2c/tests/glib_random/glib_random 20
dup /glib-t2c/tests/glib_random/glib_random 21
dup /glib-t2c/tests/glib_random/glib_random 22
dup /glib-t2c/tests/glib_random/glib_random 23
end

test /glib-t2c/tests/glib_caches/glib_caches 7
expected_severity failed
resolution Known problem
marker g_cache_value_foreach.01
comment g_cache_value_foreach is deprecated since glib version 2.10.<br/>
end

test /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 6
expected_severity unresolved
resolution Known problem
marker unexpected signal 11 (SIGSEGV) received
comment This failure occurs due to the following problem:<br/>
comment Calling FcDirScan causes segmentation fault.<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0607">here</a>.
end

test /fontconfig-t2c/tests/FcFreeTypeFileDir/FcFreeTypeFileDir 7
expected_severity failed
resolution Known problem (waived)
marker FcDirSave
comment This failure occurs due to the following:<br/>
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.<br/>
#comment Detailed description of this problem is available <a href="">here</a>.
quell
end

test /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 7
expected_severity unresolved
resolution FIP
#marker unexpected signal 1 (SIGHUP) received
comment This failure may occur if gdb is set up incorrectly (e.g. 32-bit gdb on a 64-bit machine or vice versa). If the tests were executed in a chroot environment, there can be something wrong with this environment as well.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 9
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 5
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 6
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 8
end

test /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 9
expected_severity failed
resolution FIP
#marker unexpected signal 1 (SIGHUP) received
comment This failure may occur if gdb is set up incorrectly (e.g. 32-bit gdb on a 64-bit machine or vice versa). If the tests were executed in a chroot environment, there can be something wrong with this environment as well.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 5
expected_severity time expired
resolution FIP
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.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 6
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 7
dup /glib-t2c/tests/glib_output_and_debugging/glib_output_and_debugging 8
end

test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 4
expected_severity failed
resolution FIP
marker try_iconv(): unable to create an iconv-based converter
comment It seems that iconv() itself fails to perform required operations on this system.<br/>
comment The problem is probably not in GLib.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 5
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 6
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 7
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 27
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 28
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 29
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 32
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 33
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 34
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 37
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 43
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 49
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 52
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 53
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 54
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 55
end

test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 9
expected_severity unresolved
resolution FIP
marker try_iconv(): unable to create an iconv-based converter
comment It seems that iconv() itself fails to perform required operations on this system.<br/>
comment The problem is probably not in GLib.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 10
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 11
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 12
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 56
end

test /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 58
expected_severity unresolved
resolution FIP
marker Standard iconv() error
comment It seems that iconv() itself fails to perform required operations on this system.<br/>
comment The problem is probably not in GLib.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_character_set_conversion/glib_character_set_conversion 59
end


test /glib-t2c/tests/glib_AsyncQueue/glib_AsyncQueue 5
expected_severity time expired
resolution Known problem
marker pop_test(): after g_cond_signal()
comment This problem was detected on Mandriva 2008 Free and Fedora Core 8.<br/>
comment The main thread of the test hangs in g_cond_wait(). Meanwhile, the other thread calls g_cond_signal() to wake up the main thread but it seems to have no effect.<br/>
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 58 
expected_severity failed
resolution FIP
marker g_timeout_add.01
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 7 
expected_severity failed
resolution FIP
marker g_main_loop_run.02
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 17 
expected_severity unresolved
resolution FIP
marker Unable to initialize
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
dup /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 18
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 57 
expected_severity failed
resolution FIP
marker g_timeout_source_new
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 87 
expected_severity failed
resolution FIP
marker g_child_watch_source_new.01
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_main_event_loop/glib_main_event_loop 74 
expected_severity failed
resolution FIP
marker g_idle_source_new
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_threads/glib_threads 31 
expected_severity failed
resolution FIP
marker g_static_rw_lock_reader_lock.01
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_threads/glib_threads 26 
expected_severity failed
resolution FIP
marker g_static_rec_mutex_lock_full.01
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test /glib-t2c/tests/glib_thread_pools/glib_thread_pools 11 
expected_severity failed
resolution FIP
marker g_thread_pool_unprocessed.01
comment This test may fail on slow or heavily loaded systems. The internal timeouts used by the test had probably expired before the required processing was finished.<br/>
comment This test needs to be investigated manually.
quell
end

test xdg-desktop-icon 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-desktop-menu 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-email 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-icon-resource 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-mime 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-open 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

test xdg-screensaver 1
expected_severity failed
resolution Trial Use Module
comment This failure does not affect the distribution compliance to LSB 3.2 because XDG is a Trial Use Module.
quell
end

# --- Gdk-pixbuf ---
test /gdk-pixbuf-t2c/tests/InlineData/InlineData 17
expected_severity failed
resolution Known problem
marker #error MY_IMAGE_RUN_LENGTH_DECODE
comment This failure occurs due to the following problem:<br/>
comment gdk_pixdata_to_csource does not always add a macro for rle stream decoding to the code<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0615">here</a>.
end

test /gdk-pixbuf-t2c/tests/SubPixbuf/SubPixbuf 2
expected_severity failed
resolution Known problem
marker gdk_pixbuf_saturate_and_pixelate
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_saturate_and_pixelate may corrupt memory<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0640">here</a>.
end

test /gdk-pixbuf-t2c/tests/Scaling/Scaling 24
expected_severity failed
resolution Known problem
marker GDK_INTERP_HYPER
comment This failure occurs due to the following problem:<br/>
comment Images change when scaled 1:1 with GDK_INTERP_HYPER filter<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0641">here</a>.
dup /gdk-pixbuf-t2c/tests/Scaling/Scaling 49
end

test /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 8
expected_severity failed
resolution Known problem
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_format_get_license returns NULL for any of the loaders<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0642">here</a>.
dup /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 9
dup /gdk-pixbuf-t2c/tests/ModuleInterface/ModuleInterface 10
dup /gdk-pixbuf-t2c/tests/ModuleInterface_external/ModuleInterface_external 3
end

test /gdk-pixbuf-t2c/tests/Animation/Animation 8
expected_severity failed
resolution Known problem
marker GDK_PIXBUF_ERROR_CORRUPT_IMAGE
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf loader 'ani' does not always set error on failure<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0626">here</a>.
end

test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 35
expected_severity failed
resolution Known problem
marker area_updated
comment This failure occurs due to the following problem:<br/>
comment "area-updated" signal is emitted with incorrect parameters<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0659">here</a>.
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 42
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 43
end

test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 48
expected_severity failed
resolution Known problem
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_loader_set_size does not always set image size correctly<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0660">here</a>.
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 49
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 50
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 51
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 52
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 53
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 33
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 35
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 36
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 37
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 43
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 44
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 51
dup /gdk-pixbuf-t2c/tests/FileLoading/FileLoading 52
end

test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 34
expected_severity failed
resolution Known problem
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_loader_get_pixbuf returns different results if gdk_pixbuf_loader_set_size has been called<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0657">here</a>.
end

test /gdk-pixbuf-t2c/tests/Scaling/Scaling 69
expected_severity failed
resolution Known problem
marker gdk_pixbuf_composite_color
comment This failure occurs due to the following problem:<br/>
comment The gdk_pixbuf_composite_color function uses wrong checkboard offset<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0654">here</a>.
dup /gdk-pixbuf-t2c/tests/Scaling/Scaling 70
end

test /gdk-pixbuf-t2c/tests/Utils/Utils 13
expected_severity failed
resolution Known problem
marker gdk_pixbuf_saturate_and_pixelate
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_saturate_and_pixelate changes not only saturation but also hue of the colour<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.ru/results/report?num=S0656">here</a>.
dup /gdk-pixbuf-t2c/tests/Utils/Utils 14
quell
end

test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 44
expected_severity failed
resolution Known problem
marker gdk_pixbuf_animation_iter_on_currently_loading_frame
comment This failure occurs due to the following problem:<br/>
comment gdk_pixbuf_animation_iter_on_currently_loading_frame returns FALSE while the contents of the frame are still subject to change<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0643">here</a>.
end

test /gdk-pixbuf-t2c/tests/FileSaving/FileSaving 8
expected_severity failed
resolution Known problem
comment This failure occurs due to the following problem:<br/>
comment Incorrect handling of "tEXt::key" parameters<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0661">here</a>.
dup /gdk-pixbuf-t2c/tests/Structure/Structure 7
end

test /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 20
expected_severity failed
resolution Known problem
marker gdk_pixbuf_loader_close
comment This failure occurs due to the following problem:<br/>
comment The relationship between the return value and the set error is unclear in the description of gdk_pixbuf_loader_close<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=S0663">here</a>.
quell
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 21
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 22
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 23
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 24
dup /gdk-pixbuf-t2c/tests/GdkPixbufLoader/GdkPixbufLoader 25
end

test /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 15
expected_severity failed
resolution Known problem
marker G_TYPE_CHECK_INSTANCE_TYPE
marker Warning is not emitted
comment This failure occurs due to the following problem:<br/>
comment The G_TYPE_CHECK_INSTANCE_CAST() macro does not emit a warning if an instance structure is not of the expected type<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0074">here</a>.
dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 16
dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 17
dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 18
dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 19
dup /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance 20
end

test /gobject-t2c/tests/gobject_gtype_class/gobject_gtype_class 9
expected_severity failed
resolution Known problem
marker G_TYPE_CHECK_CLASS_TYPE
marker warning was not emitted
comment This failure occurs due to the following problem:<br/>
comment The G_TYPE_CHECK_CLASS_TYPE() macro does not emit a warning if a class structure is not of the expected type<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0078">here</a>.
dup /gobject-t2c/tests/gobject_gtype_class/gobject_gtype_class 11
dup /gobject-t2c/tests/gobject_gtype_class/gobject_gtype_class 12
end

test /gobject-t2c/tests/gobject_param_spec/gobject_param_spec 9
expected_severity failed
resolution Known problem
marker Integer-2
comment This failure occurs due to the following problem:<br/>
comment Interface g_param_spec_internal does not set property name according to the specification<br/>
comment Detailed description of this problem is available <a href="http://linuxtesting.org/results/report?num=D0073">here</a>.
end

test /gobject-t2c/tests/gobject_signals/gobject_signals 34
expected_severity failed
resolution Known problem
marker g-signal-name-signal
comment The cause of this failure is probably the same as for the inconsistency in the implementation of g_param_spec_internal
comment described <a href="http://linuxtesting.org/results/report?num=D0073">here</a>.
comment The symptoms are very much alike.
end
