The lsb-cmdchk test suite verifies that all the commands required by
the LSB specification are present. It does not check the behaviour of
those commands.
The libchk test suite is used to check if the runtime libraries
contain all of the interfaces with correct versions as specified by the
LSB specification.
Click on lines in the table to see the details about each problem.
Test Name
Severity
Resolution
/tset/ANSI.os/maths/pow/T.pow 4
Warning (quelled)
Insignificant
Messages from the test
pow(0.0, -1.0) gave RETURN VALUES: expected: -inf, observed: inf Bit Representation: expected value: \000\000\000\000\000\000\360\377 Bit Representation: observed value: \000\000\000\000\000\000\360\177
Comment:
Both -inf and +inf are equally artificial results, Linux libc picks this one.
/tset/ANSI.os/streamio/fopen/T.fopen 28
Warning (quelled)
Insignificant
Messages from the test
fopen() succeeded when FOPEN_MAX streams were already open
Comment:
FOPEN_MAX is just an advisory limit, there is probably no real limit except memory.
/tset/ANSI.os/streamio/remove_X/T.remove_X 1
Warning (quelled)
Feature
Messages from the test
remove("remove_X-t.1") did not give correct results RETURN VALUES: expected: -1, observed: 0 ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
Linux allows to remove a running executable file without any side effects.
/tset/ANSI.os/streamio/tmpfile/T.tmpfile 2
Warning (quelled)
Feature
Messages from the test
Note: There is a known issue with this test, see POSIX interpretation 1003.1-1990 #74 Note: This test is waived for LSB testing, please see the waivers database tmpfile() did not creat file with mode 0666 when umask was set to 0, found 0600
Comment:
Not a bug but feature. Linux tmpfile() creates files with access rights 0600
which is more secure than POSIX mandated 0666.
/tset/POSIX.os/dataform/tar/T.tar 12
FIP (quelled)
Correct
Messages from the test
create utility exited with code 1
Comment:
This test tries to call tar with a file with too long name (>100 chars).
The tar utility can either skip the file, or fail completely; both results
are correct.
/tset/POSIX.os/devclass/c_iflag/T.c_iflag 19
Warning (quelled)
Normal
Messages from the test
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/c_lflag/T.c_lflag 6
Warning (quelled)
Normal
Messages from the test
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/i_ctty/T.i_ctty 7
Unresolved
Messages from the test
child process timed out
/tset/POSIX.os/devclass/tcdrain/T.tcdrain 2
Warning (quelled)
Normal
Messages from the test
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/devclass/tcsetattr/T.tcsetattr 8
Warning (quelled)
Normal
Messages from the test
This test will not pass when using pseudo ttys
Comment:
This is a normal result unless a hardware terminal is used (which is very rare).
/tset/POSIX.os/files/access_X/T.access_X 1
Warning (quelled)
Feature
Messages from the test
access("access_X-t.1", W_OK) did not give correct results RETURN VALUES: expected: -1, observed: 0 ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
On Linux, running executable files are normally accessible.
/tset/POSIX.os/files/rename_X/T.rename_X 1
Warning (quelled)
Feature
Messages from the test
rename("rename_X-t.1a", "rename_X-t.1b") did not give correct results RETURN VALUES: expected: -1, observed: 0 ERRNO VALUES: expected: 26 (ETXTBSY), observed: 0 (NO ERROR)
Comment:
Not a bug but feature. On Linux, running executable files are normally accessible.
sysconf(_SC_XOPEN_ENH_I18N) returned 1 - indicating the feature group is fully supported sysconf(_SC_XOPEN_CRYPT) returned 1 - indicating the feature group is supported sysconf(_SC_XOPEN_SHM) returned 1 - indicating the feature group is supported sysconf(_SC_XOPEN_LEGACY) returned 1 - indicating the feature group is fully supported
system name - Linux node name - futuro release - 2.6.18-5-486 version - #1 Mon Dec 24 16:04:42 UTC 2007 machine - i686
/tset/POSIX.os/procprim/kill_X/T.kill_X 1
Warning (quelled)
Insignificant
Messages from the test
process calling kill() did not receive signal 10
Comment:
The Linux implementation of kill() sends the signal to everyone except its own process,
which is also logical.
/tset/LI18NUX2K.L1/utils/localedef/T.localedef 3
Warning (quelled)
Waived
Messages from the test
* When the locale specification
exceeded implementation limits or the coded character set or sets used
were not supported by the implementation, and no locale was created,
verify the exit value is 2.
created locale unexpectedly This test should not create locale and exit code code sould be 2. eixt code of localedef is 0 if exit code is more than 3, please check directory if user 'vsx0' has write permission of the locale directory
*) This test result is waived now.
Comment:
This test is waived by the LSB committee.
/tset/LI18NUX2K.L1/utils/diff/T.diff 2
Failed
Messages from the test
* When -b option is specified, verify this utility interprets whitespace character according to the current locale.
Can't interprets white space characters according to the current locale.
/tset/LI18NUX2K.L1/utils/fold/T.fold 1
Failed
Messages from the test
* When this utility folds the lines without -b option, verify each line is not folded in the middle of character.
Some characters are not wrapped on the assigned width.
/tset/LI18NUX2K.L1/utils/fold/T.fold 2
Failed
Messages from the test
* When this utility folds the lines with -b option, verify each line is not folded in the middle of character.
Some characters are not wrapped on the assigned width.
/tset/LI18NUX2K.L1/utils/fold/T.fold 3
Failed
Messages from the test
* When this utility folds the lines
with -s option, verify this utility interprets blank characters
according to the current locale.
Some blank character is not interpreted.
/tset/LI18NUX2K.L1/utils/join/T.join 3
Failed
Messages from the test
* When -t option is specified,
verify this utility uses given character as a separator even if the
character is multibyte character.
This utility does not join the files.
/tset/LI18NUX2K.L1/utils/join/T.join 4
Failed
Messages from the test
* When -t option is not specified, verify blank characters according to the current locale are used as input field separators.
This utility does not join the files.
/tset/LI18NUX2K.L1/utils/pr/T.pr 1
Failed
Messages from the test
* When -w option is specified,
verify this utility truncates the lines to make the length of the lines
be less than or equal to the assigned width.
Can't truncates the input lines correctly.
/tset/LI18NUX2K.L1/utils/pr/T.pr 3
Failed
Messages from the test
* When -n option is specified,
verify this utility uses the given character as the separator between
line number and first column.
Can't interpret character as the separator between line number and first column.
/tset/LI18NUX2K.L1/utils/pr/T.pr 4
Failed
Messages from the test
* When -s option is specified, verify this utility uses the given character as the separator during the columns.
Can't interpret character as the separator during the columns.
/tset/LI18NUX2K.L1/utils/pr/T.pr 5
Failed
Messages from the test
* When -i option is specified,
verify this utility uses the given character as the character which
multiple space characters is replaced with. The replaced space
characters are to the next tab stop.
Can't replace the taget spaces with the character correctry.
/tset/LI18NUX2K.L1/utils/pr/T.pr 6
Failed
Messages from the test
* When -e option is specified,
verify this utility uses the given character as the character which is
replaced with multiple space characters. The number of space characters
is defined so that next character stands at tab_stop.
Can't replace the character with the spaces correctry.
/tset/LI18NUX2K.L1/utils/sort/T.sort 8
Failed
Messages from the test
* When -t option is specified,
verify this utility use a character as a field separator even if the
character is a multibyte character.
Can't handle field separator written in a multibyte chaaracter.
