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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0560 Actions

    Problem Report Number 0560
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0164
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Commands and Utilities V3 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.0.1
    Test Identification POSIX.cmd/ed 198
    Problem Summary PG4C.00114 This request correctly claims that the test may hang intermittently on implementations with an ed command that does not exit when it reads an EOF.
    Problem Text
    This IR refers to Consultant's responses in PG4C.00111 and
    PG4C.00099.

    from PG4C.00111:

    The submitter is partially correct, The send command referenced
    should really be an expect command. But this does not causes the
    test to hang or to fail.

    This test error causes the two send commands

    send "Talk with M Hermite: he never evokes a concrete image; yet"
    send "Q\n"

    to erroneously send the string

    Talk with M Hermite: he never evokes a concrete image; yetQ\n

    to ed. On proper implementations ed will see this string as an
    error and echo

    ?

    rather than exiting as desired. ed will then wait for further
    input to be sent. But there is no further input. The rest of
    the expect program is as follows

    Our response:

    This does cause the test to hang on our implementation and making
    the change DOES allow the proper completion of the test. The
    assumption made that ? will be returned for any ed commands not
    documented in the XPG spec is incorrect. This is not a XPG
    requirement and implementations may have additional commands available
    to users. Also, if the test was expecting an error from this
    then the expected exit status is incorrect, from the tp198 code:

    if [ $CT_EXIT_VALUE -ne 0 ]; then
    SetResult $TET_FAIL "Expected exit code = 0; Received $CT_EXIT_VALUE"
    else
    SetResult $TET_PASS
    fi

    But on page 300 of XPG5 XCU it states:

    "EXIT STATUS
    The following exit values are returned:
    0 Successful completion without any file or command errors
    >0 An error occurred."

    So the expected exit status would >0 rather the 0 as coded in the
    test.

    from PG4C.00111:

    As stated in PG4C.00098, the SIGHUP generated by the close should
    cause ed to exit and the test to pass.

    Our response:

    The consultants agreed in PG4C.00099, that expect doesn't send
    a SIGHUP as documented. From PG4C.00099:

    The submitter is correct. Although the documentation states that
    the close command sneds a SIGHUP, the Expect version used in the
    VSC release does not do this.

    As the following demonstrates, our ed does respond to SIGHUP

    $ ps -ef | grep vsc | grep -v ksh | grep -v grep | grep -v ps
    vsc0 8418 10718 0 10:39:07 lft0 0:01 sh -- /tsuites/VSC5.0.1/tet_tmp_di
    r/10718a/ed/ed_04.sh 198
    vsc0 9644 12264 0 10:39:16 lft0 0:00 expect -f ed_in_198_1
    vsc0 10718 11798 0 10:39:01 lft0 0:00 tcc -bec -s /tmp/vscrun.11798 vsc
    ed
    vsc0 10918 9644 0 10:39:16 pts/3 0:00 ed ed_out_198_1
    vsc0 12264 8418 0 10:39:16 lft0 0:00 sh -- /tsuites/VSC5.0.1/tet_tmp_di
    r/10718a/ed/ed_04.sh 198
    $ kill -s HUP 10918
    $ ps -ef | grep vsc | grep -v ksh | grep -v grep | grep -v ps
    $ grep PASS ~/results/0040bec/journal
    220|0 1 0 10:39:03|PASS
    220|1 1 0 10:42:26|PASS
    220|2 1 0 10:42:33|PASS

    And finally manually entering the expect sequence shows that our
    ed returns the proper responses:

    $ ed ed_out_198_1
    161
    1s/with/to/
    w
    159
    1s/to/with/
    q
    ?
    1p
    Talk with M Hermite: he never evokes a concrete image; yet
    Q
    $ print $?
    0

    Test Output
    No output, tests hangs

    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 submitter is correct. Although the documentation states that
    the close command sends a SIGHUP, the Expect version used in the
    VSC release does not do this.

    However, either patch 4.1.6A or 5.0.1A provides a workaround for
    this failure. We reccommend that the implementation be required
    to apply this patch prior to making a single branding run.

    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