Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1548 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1548.

Report 1548 Actions

    Problem Report Number 1548
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0830
    Raised 2000-08-27 08:00
    Updated 2003-03-13 08:00
    Published 2000-09-18 08:00
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.0.4
    Test Identification CAPIbase/close 3
    Problem Summary TSD4U.00291 The test should calculate the time to allow for close() to complete from the stream module close time (obtained using I_GETCLTIME)
    Problem Text
    This test does the following:

    Open master/slave ptys
    write data onto the slave pty
    set completion alarm
    close the slave pty
    read the master pty
    close the master pty

    However, the close of the slave pty waits because data is
    still on the STREAM. This causes the alarm to step in and
    end the test. This expected behavior for the slave pty,
    page 135 of the XSH5 states the following:

    "... If O_NONBLOCK is not set and there have been no signals
    posted for the STREAM, and if there is data on the module's
    write queue, close() waits for unspecified time (for each
    module and driver) for any output to drain before
    dismantling the STREAM."

    The test writes data onto the stream and then tries to close
    the slave. The slave side is not open with O_NONBLOCK and
    there are no signals pending for test 3. From the statement
    above this close is allowed to take an unspecified time, so
    However, the close of the slave pty waits because data is
    still on the STREAM. This causes the alarm to step in and
    end the test. This expected behavior for the slave pty,
    page 135 of the XSH5 states the following:

    "... If O_NONBLOCK is not set and there have been no signals
    posted for the STREAM, and if there is data on the module's
    write queue, close() waits for unspecified time (for each
    module and driver) for any output to drain before
    dismantling the STREAM."

    The test writes data onto the stream and then tries to close
    the slave. The slave side is not open with O_NONBLOCK and
    there are no signals pending for test 3. From the statement
    above this close is allowed to take an unspecified time, so
    it is allowed for the slave's close to wait forever. A pty
    is supposed act exactly like a tty (page 26 of the XBD5).
    The close on the send tty waits indefinitely for the
    receiving tty to read the data on the buffer.

    The initial consultant response to this was one of
    agreement. He stated that test 3 did not use the stream
    module close time as the delimiter for the time needed by the
    stream to dismantle procedure.

    Test Output
    TEST CASE: close

    TEST PURPOSE #3
    The last successful call to int close(int fildes) for
    fildes when fildes is associated with a STREAM,
    O_NONBLOCK is not set for fildes, and no signals are
    posted for the STREAM shall wait for each module and
    driver with data on it's write queue to drain its
    output before dismantling the STREAM.
    PREP: Open master pseudo tty
    PREP: Determine if pseudo tty is a stream
    PREP: Open slave pseudo tty
    PREP: Ignore any signals
    PREP: Push modules on the STREAM
    PREP: Write data into STREAM
    PREP: Close end of STREAM
    ERROR: Alarm expired awaiting completion
    3 UNRESOLVED

    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.

    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:

     

    Back   

Contact the Certification Authority