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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0612 Actions

    Problem Report Number 0612
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0216
    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/fg 27
    Problem Summary PG4C.00060 This test may fail if a shell refuses to exit when it has stopped jobs.
    Problem Text
    This timeout is happening because the expect script does not dispose of
    the process it started. The ExitSh statement in 27_1.exp tries sending
    two successive "exit"s to the shell and each time the shell responds
    that there are stopped processes. Some platforms have shells that will
    terminate if there are stopped processes when two successive "exit"s are
    entered but this is not required to be compliant to the XPG4 standard.

    The following is part of the output of expect output with the "-d"
    option that demonstrates that the fg command is working properly when
    job control is disabled and that both "exit"s produce the
    warning about stopped jobs:

    send: sending "fg %1\r" to { 4 }
    expect: does "PS1 fg %1\r\nfg: job control disabled\r\nPS1 "...

    send: sending "echo $? > fg_27.out\r" to { 4 }
    expect: does "echo $? > fg_27.out\r\nPS1 "...

    send: sending "exit\r" to { 4 }
    expect: does "exit\r\nexit: there are stopped jobs\r\nPS1 "...
    expect: timed out

    send: sending "exit\r" to { 4 }
    expect: does "exit\r\nexit: there are stopped jobs\r\n"...
    expect: does "PS1 " (spawn_id 4) match regular expression "..*"? yes
    expect: does "" (spawn_id 4) match regular expression "..*"? no
    expect: timed out
    expect_after: unexpected timeout
    Test Output
    Assertion #27 (C): fg exits with error if job control is disabled
    Expected exit code = 0; Received 1
    Standard error isn't empty
    Contents of out.stderr:
    expect_after: unexpected timeout

    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.

    XCU section 2.14.7 states

    The exit utility causes the shell to exit with the
    exit status specified by the unsigned decimal integer
    n.

    The clearly states that tyhe exit command should cause the shell
    to exit.

    The expect ExitSh() code is not issuing the exit command twice to
    get around warnings about background jobs. It is attempting to
    give the shell a second chance to synchronize with the test
    script and exit if the first exit attempt fails. This is purely
    a timing issue.

    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