|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 0180 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 0180.
Report 0180 Actions
Problem Report Number 0180 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0180 Raised 1994-08-04 08:00 Updated 2003-03-13 08:00 Published 1994-08-15 08:00 Product Standard Internationalised System Calls and Libraries (XPG4) Certification Program The Open Brand certification program Test Suite VSX4 version 4.3.4 Test Identification POSIX.os/ioprim/write 12,13 Linked Problem Reports TSD.159, TSD.160, (in, old, system) Problem Summary TSD4.180 Test 12 fails due to the incorrect assumption as to when a write to a pipe will continue after being blocked. On our system a blocked write will not continue until the amount of data in the pipe drops... Problem Text
Test 12 fails due to the incorrect assumption as to when a write to
a pipe will continue after being blocked. On our system a blocked
write will not continue until the amount of data in the pipe drops below
a low water mark. This test fails because the amount of data in the
pipe never falls below this low water mark. Specifically, the test
fills the pipe and then attempts to write an additional number of
bytes to the pipe expecting the write to block. This succeeds. The
child then reads data and expects the write to continue, however,
at this point, the writer does not wake up because the low water mark
has not been reached. The parent process hangs and times out resulting
in the EINTR errno.
Test 13 then becomes unreported as a consequence of test 12 failing:
POSIX.os/ioprim/write test 13 should have initialized testfail to zero
at the beginning of the test. The problem is that when test #12 failed
the variable "testfail" is NOT zero. If test 13 does not reinitialize
"testfail" to zero, test 13 inherits the non-zero value from test 12
and therefore, test 13 is marked "UNREPORTED" at the end of the test.Test Output
************************************************************************
/tset/POSIX.os/ioprim/write/T.write 12 Failed
Test Description:
For the XNFS specification:
Not in use.
For the XSH specification:
When writing {PIPE_BUF} or fewer bytes to a pipe or FIFO for which
the O_NONBLOCK is clear, the calling process will block until
space is available to complete the write operation
Posix Ref: Component WRITE Assertion 6.4.2.2-20(A)
Posix Ref: Component PATHCONF Assertion 5.7.1.2-40(A)
Test Strategy:
REPEAT for FIFO and pipe:
WRITE to FIFO/pipe until no more data can be transferred
CREATE process pair
PARENT process:
WRITE pipe_buf bytes to FIFO/pipe
CHILD process:
SLEEP for WAITTIME/2
READ pipe_buf bytes from FIFO/pipe
PARENT process:
VERIFY that write() returns pipe_buf bytes
Test Information:
write() returned -1, expected 16384
errno was set to 4 (EINTR)
write() returned -1, expected 16384
errno was set to 4 (EINTR)
************************************************************************
************************************************************************
/tset/POSIX.os/ioprim/write/T.write 13 UNREPORTED
Test Description:
For the XNFS specification:
Not in use.
For the XSH specification:
When the file's type is a pipe or a FIFO, the O_NONBLOCK flag is
set, nbyte is greater than {PIPE_BUF} bytes, and at least one byte
can be written, then a call to write() transfers what it can and
returns the number of bytes written.
In XPG3 mode, write() may also return -1, set errno to EAGAIN and
transfer no data.
Posix Ref: Component WRITE Assertion 6.4.2.2-21(C)
Posix Ref: Component PATHCONF Assertion 5.7.1.2-40(A)
Test Information:
************************************************************************Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
This is accepted as a fault in the test suite and it is recommended that
a waiver is granted on the grounds of a test suite deficiency.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion
This is an agreed Test Suite Deficiency.
Problem Reporting System Options:
- View Report 0180
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority