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

The Open Brand -- Problem Reporting and Interpretations System


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


Report 0836 Actions


    Problem Report Number 0836
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0351
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-02-05 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.4
    Test Identification XOPEN.cmd/sccs 1049 1051
    Problem Summary TSD4C.00160 The test may fail on implmentations on certain days and times because of a vague regular expression used by grep.
    Problem Text
    The test may fail on implmentations on certain days and times because
    of a vague regular expression used by grep.

    The tests in question test the following assertions:

    #1049:
    When the delget pseudo-utility is specified, then any -m, -p,
    -r, -s and -y options will be passed to delta and any
    -b, -c, -e, -k, -l, -s and -x options shall be passed to
    get.

    #1051:
    When the deledit pseudo-utility is specified, then any -m, -p,
    -r, -s and -y options will be passed to delta and any
    -b, -c, -k, -l, -s and -x options shall be passed to
    get.

    The two tests use similar strategies, which include creating several
    deltas to a file named sccs_in_4. At a certain point, each test
    executes the following code as part of the setup:

    test `grep -c "1.3" SCCS/p.sccs_in_4 ` -eq 1
    if [ $? -ne 0 ]; then
    SetResult $TET_UNRESOLVED "Command failed: 'test \`grep -c \"1.3\"
    SCCS/p.sccs_in_4 \` -eq 1'"
    return
    fi

    The code is identical in both tests, and is intended to ensure that the
    SID "1.3" occurs exactly once in the p-file. It is this setup step that
    failed on our system. Analysis showed that the reason was identical for
    both tests. The p-file for test 1049 is

    1.3 1.4 vsc0 96/01/30 13:06:24
    1.1 1.1.1.1 vsc0 96/01/30 13:06:24

    and for 1051 is

    1.3 1.4 vsc0 96/01/30 13:06:40
    1.1 1.1.1.1 vsc0 96/01/30 13:06:40

    In both cases the string "1.3" occurs exactly as required. However, the
    command

    grep -c "1.3" SCCS/p.sccs_in_4

    treats the '.' in "1.3" as a regular expression wild card, so that it
    also matches the "1/3" which is part of the date of 96/01/30. Thus
    "grep -c" returns 2, rather than 1. This error will occur on tests run
    on January 30 or 31, or November 30, or on any day at certain times
    (such as 11:30-11:39). This is clearly a Test Suite Defect.

    The test can be fixed by changing the greps to search for the string
    "1\.3". This is necessary both in the setup code and in tests that
    occur later on in the code for these two assertions, and it may be
    necessary in other places. (We haven't checked to see, for example, if
    there are any grep calls for the string "1.2".) When these changes are
    made the assertions pass on our systems even on the dates (and
    presumably the times) in question.
    Test Output
    -----------------start of test output------------------

    400|556 1049 1 06:33:14|IC Start
    200|556 1 06:33:14|TP Start
    520|556 1 6619 1 1|Assertion #1049 (C): Test delget pseudo-utility options
    520|556 1 6619 1 1|Command failed: 'test `grep -c "1.3" SCCS/p.sccs_in_4 ` -eq
    1'
    220|556 1 2 06:33:26|UNRESOLVED
    410|556 1049 1 06:33:26|IC End

    400|556 1051 1 06:33:29|IC Start
    200|556 1 06:33:29|TP Start
    520|556 1 6619 1 1|Assertion #1051 (C): Test deledit pseudo-utility options
    520|556 1 6619 1 1|Command failed: 'test `grep -c "1.3" SCCS/p.sccs_in_4 ` -eq
    1'
    220|556 1 2 06:33:41|UNRESOLVED
    410|556 1051 1 06:33:41|IC End

    ------------------end of test output-------------------

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a test suite deficiency in the test
    suite version(s) listed.

    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