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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1002 Actions

    Problem Report Number 1002
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0517
    Raised 2000-10-04 08:00
    Updated 2003-03-13 08:00
    Published 2000-10-20 08:00
    Product Standard Commands and Utilities V3 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.1.1
    Test Identification POSIX.upe/newgrp 2
    Problem Summary TSD4C.00235 The test may fail on fast machines, due to an "expect" script problem
    Problem Text
    The code for POSIX.upe/newgrp Assertion #2 contains the following
    expect code:

    cat > expect_scr << EOF
    spawn -noecho sh
    expect
    send "$VSC_ROOT/Bin/ga04 newgrp $othergrp\r"
    expect
    send "id -gn > $resultfile\r"
    expect
    send "exit 0\r"
    expect eof
    exit
    EOF

    expect -f expect_scr > /dev/null 2>&1

    The "expect" lines after each send search for no pattern, giving them
    the effect of a "sleep 10", the default timeout for the expect
    command.

    When this code is run on a faster machine, the test fails because
    the second "send" line (send "id -gn > $resultfile\r") sends to the
    wrong process, it does not send to the child of the ga04 command which
    is running with the new group id.

    When the "expect" line between the first and second "send" is removed,
    the test passes. An "expect" line is not required after "send" in
    order for the script to run properly. The test with the second
    "expect" line removed also passes on the slower machines where the
    original code also passes.

    By making the expect timeout as high as 60, on a machine where the
    original code passes, it will fail.

    This timeout effect can also be seen by running the test through the
    expect interpreter (expect -i). When the lines of the script are
    run through the interpreter, even on a machine where the test passes,
    the script is slowed so much, it will fail.

    A suggest fix is to remove the "expect" line between the first and
    second "send" so the code will look as follows:

    cat > expect_scr << EOF
    spawn -noecho sh
    expect
    send "$VSC_ROOT/Bin/ga04 newgrp $othergrp\r"
    send "id -gn > $resultfile\r"
    expect
    send "exit 0\r"
    expect eof
    exit
    EOF

    expect -f expect_scr > /dev/null 2>&1


    Test Output
    ***********************************************************************
    /tset/POSIX.upe/newgrp/newgrp.ex 1 Failed


    Test Information:
    Assertion #2 (C):
    After exec() of newgrp, group was "vscg0", expected group of
    <LC> "vscg1".

    ***********************************************************************

    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.

    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