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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0183 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 0183.

Report 0183 Actions

    Problem Report Number 0183
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0183
    Raised 1994-08-10 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.2
    Test Identification POSIX.os/devclass/tcflow 14
    Problem Summary TSD4.183 This test case fails due to the problem in the previous test case (tcflow 13). It writes 37 bytes of data and stops output by tcflow(TCOOFF) on the terminal side. Usually, the bytes are queued in the ...
    Problem Text

    This test case fails due to the problem in the previous test case
    (tcflow 13). It writes 37 bytes of data and stops output by
    tcflow(TCOOFF) on the terminal side. Usually, the bytes are queued
    in the terminal device driver and the test case ends with this situation.

    When the test case tcflow 14 starts, it restarts output to the loop
    back device by issuing tcflow(TCOON) and flushes on both loop back
    and terminal devices. This tcflow(TCOON) call causes the queued
    data to be written to the terminal side, so when the child process
    reads from the loop back side, some data (written by the previous
    test) may be available for read(), depending on the device driver's
    writing timing.

    This test case, however, expects that the read() call will time out
    and returns with EINTR error because no data is available from loop
    back device. However, the test will always see the extra 37 bytes
    of data (written by the test case 13) due to the above reason, and
    will always fail.

    This test case passes if the test case 13 is not executed.

    Test Output
    /tset/POSIX.os/devclass/tcflow/T.tcflow 14 Failed

    Test Description:
    If general terminal interface supported:
    when tcflow() is called from a background process, that is not
    blocking or ignoring the SIGTTOU signal, and when fildes refers to
    a non-controlling terminal, the tcflow actions shall be performed.
    Posix Ref: Component TCFLOW Assertion 7.2.2.2-X3(C)

    Test Strategy:
    OPEN and initialise terminal file and loop back file
    For termio flag TOSTOP set and clear:
    For each action TCOON, TCOOFF, TCION, TCIOFF:
    RESTART output of data to loopback file using tcflow() using TCOON
    If action is TCOON:
    SET time out for WAITTIME
    SUSPEND output of data to loop back file using tcflow() using
    TCOOFF
    CREATE child process
    CHILD process:
    CREATE new background process group using setpgid(0, 0)
    SET signal action for SIGTTOU to signal catching function
    SET time out for WAITTIME/2
    CALL tcflow() for the current action
    VERIFY that SIGTTOU was received
    SET time out for WAITTIME
    WRITE data to loop back file using write()
    IF action is TCOOFF and terminal output is not buffered
    VERIFY write timed out
    ELSE
    VERIFY that write returned the size of data written
    SLEEP for a short interval to allow data to be available for
    reading
    SET time out for WAITTIME
    READ from terminal file using read()
    VERIFY that read did not time out
    If action is TCOOFF:
    VERIFY that read returned size of data written
    If action is TCOON:
    VERIFY that read did not return any data
    VERIFY that loop back start and stop characters were not read

    Test Information:
    tcflow(TCOOFF) action was not performed
    when TOSTOP bit was set

    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:

     

    Back   

Contact the Certification Authority