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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0604 Actions

    Problem Report Number 0604
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0208
    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.cmd/mailx_01.ex 42
    Problem Summary PG4C.00068 This test may fail due to a timeout problem with an expect script.
    Problem Text
    This test may fail due to a timeout problem with an expect script.

    This test case assertion consistently times out because a '\r' is
    not being sent before the 'ExpectShPrompt' in the first expect script,
    42_1.exp, in the test. The second script, 42_2.exp, sends a '~q\r' and
    then sends '\r' again before the 'ExpectShPrompt' and this portion of
    the test succeeds, consistently.

    Because a second '\r' is not sent in the 42_1.exp script the
    expected sequence, '\r\nPS1 ' is never seen.
    Test Output
    POSIX.cmd/test/test.ex 04:40:40|TC Start, scenario ref 100-1
    TP Start
    1 1|Assertion #42 (C): PAGER is a command to use when numbe
    1 2| <LC> r of lines is greater than crt
    1 11|-- Testing Print
    1 12|Expected exit code = 0; Received 1
    1 13|Standard error isn't empty
    1 14|Contents of out.stderr:
    1 15|expect_after: unexpected timeout
    1 16|-- Testing print
    1 17|Expected exit code = 0; Received 1
    1 18|Standard error isn't empty
    1 19|Contents of out.stderr:
    1 20|expect_after: unexpected timeout
    1 21|-- Testing Type
    1 22|Expected exit code = 0; Received 1
    1 23|Standard error isn't empty
    1 24|Contents of out.stderr:
    1 25|expect_after: unexpected timeout
    1 26|-- Testing type
    1 27|Expected exit code = 0; Received 1
    1 28|Standard error isn't empty
    1 29|Contents of out.stderr:
    1 30|expect_after: unexpected timeout
    1 31|-- Testing dp
    1 32|Expected exit code = 0; Received 1
    1 33|Standard error isn't empty
    1 34|Contents of out.stderr:
    1 35|expect_after: unexpected timeout
    1 36|-- Testing dt
    1 37|Expected exit code = 0; Received 1
    1 38|Standard error isn't empty
    1 39|Contents of out.stderr:
    1 40|expect_after: unexpected timeout
    1 41|-- Testing delete
    1 42|Expected exit code = 0; Received 1
    1 43|Standard error isn't empty
    1 44|Contents of out.stderr:
    1 45|expect_after: unexpected timeout
    1 46|-- Testing next
    1 47|Expected exit code = 0; Received 1
    1 48|Standard error isn't empty
    1 49|Contents of out.stderr:
    1 50|expect_after: unexpected timeout
    1 51|-- Testing undelete
    1 52|Expected exit code = 0; Received 1
    1 53|Standard error isn't empty
    1 54|Contents of out.stderr:
    1 55|expect_after: unexpected timeout
    1 56|-- Testing ~p
    9|FAIL
    29|IC End

    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.

    Please note: there are 2 ExpectShPrompt calls in the first test
    script. The following assumes you are referring to the second of
    these calls.

    The code under discussion in the first expect script runs mailx,
    issues some commands, then exits mailx and returns to the shell.
    The shell should immediately issue a prompt.

    As the test is written the ExpectShPrompt call waits timeout
    seconds (the default vaule is 10) for this prompt to appear. We
    believe it is reasonable to expect the prompt within this time
    and the test should work as is.

    If the timeframe is not sufficient increasing the value of
    timeout in ~vsc/Src/ImplSpec may allow the test to pass. If this
    does not work then the test is failing for some other reason.

    We agree that the second expect script in this series is written
    slightly different. It exits mailx, then discards all output,
    which should include the first prompt issued on return to the
    shell. Then it issues a return to get a second, expected shell
    prompt.

    This does not mean the return is necessary. We believe this
    second script would work just as well if second script were
    changed from

    send "~q\r"
    DiscardAllOutput
    send "\r"
    ExpectShPrompt

    to

    send "~p\r"
    ExecNap
    expect "$env(EXP_UTIL_STR)"
    send "~q\r"
    ExpectShPrompt

    Although it is difficult to tell, this request should have been
    filed as an SR rather than an IR. If further discussion of this
    issue is necessary please file a SR which includes a uuencoded
    copy of the output and the journal from the command

    vscrun -trace mailx 42

    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