HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


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


Report 0613 Actions


    Problem Report Number 0613
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0217
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.5
    Test Identification POSIX.upe/ex 536
    Problem Summary PG4C.00059 The test fails because expect issues input too fast for ex to processes it.
    Problem Text
    The test uses the termin script to cause expect to do 80 sends
    to the pseudoterminal in a tight loop. On our system the
    rapid-fire write()s cause a problem in the terminal-reading code
    of ex, on very rare occasions. The result is that some
    characters are lost and there is an additional line break.

    When the steps of the test are executed by hand or when the test case
    code is altered to call termin.tcl with the "-s" flag so it
    sleeps between sends, the result is always UNTESTED.

    This POSIX.upe test is supposed to test for proper interactive
    behavior of the utility. It is not appropriate for the test to
    fail because of a stress test of the terminal interface, a
    condition that does not arise in interactive use and that is
    beyond the scope of the shell and tools standard in any case.
    Programs that run vi ("ex -v") at high speed must be prepared to
    accommodate the limitations of the terminal interface.

    The test could be made reliable by calling termin.tcl with the
    "-s" flag. If this were made the default for termin.tcl, the
    fix would prevent annoying sporadic failures in other tests as
    well.

    A permanent fix that might not have as great an impact on the
    test suite run time would be to add configurable padding to the
    expect 'send' directive. It might default to 10 milliseconds and
    be configurable in increments of 10 milliseconds.
    Test Output
    /tset/POSIX.upe/ex/ex_08.ex 1 Failed


    Test Information:
    Assertion #536 (D): specification of the wrapmargin option
    Command failed: '[ "`grep -c 'a a a' ex_data_1`" -eq 2 ]'

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    The statement that the test issues 80 rapid fire writes to the
    pseudoterminal in a tight loop is unlikely. The SendString()
    loop stops after every input string and does a DiscardAllOutput().
    This function waits for output caused by recent input to stop,
    then waits an additional amount of time before sending the next
    input string.

    In this particular case, termin is sending a single character of input,
    waiting for the input to be echoed, pausing some more, then moving on
    to the next character. We estimate the pauses generate input at a slower
    rate than a person would. No characters should be lost.

    The statement that the tests pass when the -s flag is used is curious
    since the -s flag has no effect on termin execution in VSC 4.1.5. As
    the submitter recommends, the semantics specified by -s in VSC 4.1.4
    are always used in 4.1.5. There is no way to turn the intra string
    delay off. The delay is configurable.

    The analysis above would only seem valid if the test were run in an
    unpatched VSC 4.1.4 or a misconfigured VSC 4.1.5 hierarchy.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority