pathconf/fpathconf failing in some cases

Yitzchak Scott-Thoennes sthoenna@efn.org
Mon Sep 11 03:49:00 GMT 2006


The perl tests for pathconf/fpathconf are showing some failures
(perl translates -1 to undef, and the fpathconf calls are made on an
fd opened to the path mentioned in the following pathconf calls):

1..84
ok 1 - calling fpathconf(3, _PC_CHOWN_RESTRICTED)
not ok 2 - 	checking that the returned value is defined:
not ok 3 - 	checking that the returned value looks like a number
ok 4 - calling fpathconf(3, _PC_LINK_MAX)
ok 5 - 	checking that the returned value is defined: 8
ok 6 - 	checking that the returned value looks like a number
ok 7 - calling fpathconf(3, _PC_NAME_MAX)
ok 8 - 	checking that the returned value is defined: 260
ok 9 - 	checking that the returned value looks like a number
ok 10 - calling fpathconf(3, _PC_NO_TRUNC)
not ok 11 - 	checking that the returned value is defined:
not ok 12 - 	checking that the returned value looks like a number
ok 13 - calling fpathconf(3, _PC_PATH_MAX)
ok 14 - 	checking that the returned value is defined: 260
ok 15 - 	checking that the returned value looks like a number
ok 16 - calling pathconf(".", _PC_CHOWN_RESTRICTED)
not ok 17 - 	checking that the returned value is defined:
not ok 18 - 	checking that the returned value looks like a number
ok 19 - calling pathconf(".", _PC_LINK_MAX)
ok 20 - 	checking that the returned value is defined: 8
ok 21 - 	checking that the returned value looks like a number
ok 22 - calling pathconf(".", _PC_NAME_MAX)
ok 23 - 	checking that the returned value is defined: 260
ok 24 - 	checking that the returned value looks like a number
ok 25 - calling pathconf(".", _PC_NO_TRUNC)
not ok 26 - 	checking that the returned value is defined:
not ok 27 - 	checking that the returned value looks like a number
ok 28 - calling pathconf(".", _PC_PATH_MAX)
ok 29 - 	checking that the returned value is defined: 259
ok 30 - 	checking that the returned value looks like a number
ok 31 - calling fpathconf(3, _PC_MAX_CANON) (/dev/tty)
ok 32 - 	checking that the returned value is defined: 255
ok 33 - 	checking that the returned value looks like a number
ok 34 - calling fpathconf(3, _PC_MAX_INPUT) (/dev/tty)
ok 35 - 	checking that the returned value is defined: 255
ok 36 - 	checking that the returned value looks like a number
ok 37 - calling fpathconf(3, _PC_VDISABLE) (/dev/tty)
not ok 38 - 	checking that the returned value is defined:
not ok 39 - 	checking that the returned value looks like a number
ok 40 - calling pathconf(/dev/tty, _PC_MAX_CANON)
ok 41 - 	checking that the returned value is defined: 255
ok 42 - 	checking that the returned value looks like a number
ok 43 - calling pathconf(/dev/tty, _PC_MAX_INPUT)
ok 44 - 	checking that the returned value is defined: 255
ok 45 - 	checking that the returned value looks like a number
ok 46 - calling pathconf(/dev/tty, _PC_VDISABLE)
not ok 47 - 	checking that the returned value is defined:
not ok 48 - 	checking that the returned value looks like a number
ok 49 - calling fpathconf(4, _PC_PIPE_BUF) (fifo3748)
ok 50 - 	checking that the returned value is defined: 4096
ok 51 - 	checking that the returned value looks like a number
ok 52 - calling pathconf(fifo3748, _PC_PIPE_BUF)
ok 53 - 	checking that the returned value is defined: 4096
ok 54 - 	checking that the returned value looks like a number
ok 55 - calling sysconf(_SC_ARG_MAX)
ok 56 - 	checking that the returned value is defined or that errno is
clear: 1048576
ok 57 - 	checking that the returned value looks like a number
ok 58 - calling sysconf(_SC_CHILD_MAX)
ok 59 - 	checking that the returned value is defined or that errno is
clear: 63
ok 60 - 	checking that the returned value looks like a number
ok 61 - calling sysconf(_SC_CLK_TCK)
ok 62 - 	checking that the returned value is defined or that errno is
clear: 1000
ok 63 - 	checking that the returned value looks like a number
ok 64 - calling sysconf(_SC_JOB_CONTROL)
ok 65 - 	checking that the returned value is defined or that errno is
clear: 1
ok 66 - 	checking that the returned value looks like a number
ok 67 - calling sysconf(_SC_NGROUPS_MAX)
ok 68 - 	checking that the returned value is defined or that errno is
clear: 16
ok 69 - 	checking that the returned value looks like a number
ok 70 - calling sysconf(_SC_OPEN_MAX)
ok 71 - 	checking that the returned value is defined or that errno is
clear: 256
ok 72 - 	checking that the returned value looks like a number
ok 73 - calling sysconf(_SC_PAGESIZE)
ok 74 - 	checking that the returned value is defined or that errno is
clear: 65536
ok 75 - 	checking that the returned value looks like a number
ok 76 - calling sysconf(_SC_SAVED_IDS)
ok 77 - 	checking that the returned value is defined or that errno is
clear: 0 but true
ok 78 - 	checking that the returned value looks like a number
ok 79 - calling sysconf(_SC_TZNAME_MAX)
not ok 80 - 	checking that the returned value is defined or that errno is
clear:  Invalid argument
not ok 81 - 	checking that the returned value looks like a number
ok 82 - calling sysconf(_SC_VERSION)
ok 83 - 	checking that the returned value is defined or that errno is
clear: 199009
ok 84 - 	checking that the returned value looks like a number

If no one beats me to it, I'll try to translate these to C test cases in
the next day or so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cygcheck.out
Type: application/octet-stream
Size: 29273 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060911/10b98256/attachment.obj>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


More information about the Cygwin mailing list