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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0805 Actions

    Problem Report Number 0805
    Submitter's Classification Specification problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0320
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-10-01 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.5
    Test Identification XOPEN.cmd/sccs 1008
    Problem Summary TSD4C.00191 This test may fail on implementations because tmp/ is never referenced when "sccs get tmp/" becomes "get SCCS/s.tmp/".
    Problem Text
    The test failed because of an alternate interpretation of a gray area in the
    specification of the command sccs.

    We believe parts of the GA12--Pathname Resolution--requirement that
    refer to resolution of directory name arguments should not be applied to
    the command sccs. These are the parts tested by GA62 and GA63.

    The "CAE Specification, Commands and Utilities Issue 4, Version 2" document,
    pages 619-622, specifies the syntax for sccs as

    sccs [-r] [-d path] [-p path] command [options...] [operands...]

    and includes the following description:

    The sccs utility invokes the specified command with the specified
    options and operands. By default, each of the operands is modified
    by prefixing it with the string SCCS/s..

    The specification does not specify that each operand must be a pathname.
    Thus it is possible for an implementation to exhibit the following
    behaviors and still conforms to the letter of the sccs specification.

    Suppose "mydir" is a directory in the current working directory and it
    contains SCCS file(s). Further suppose that there is no directory named
    "SCCS" in the current working directory. Then:

    a) The command 'sccs get mydir' modifies the operand to "SCCS/s.mydir"
    and passes it to the SCCS command 'get'. Since there is no
    SCCS file with pathname SCCS/s.mydir, the 'get' command writes
    an error message to stderr and exits with nonzero exit value.

    b) The command 'sccs get mydir/' modifies the operand to
    "mydir/SCCS/s." and passes it to the SCCS command 'get'. Since
    there is no SCCS file with that pathname, the 'get' command writes
    an error message to stderr and exits with nonzero exit value.

    c) The command 'sccs get mydir//' modifies the operand to
    "mydir//SCCS/s." and passes it to the SCCS command 'get'. Since
    there is no SCCS file with that pathname, the 'get' command writes
    an error message to stderr and exits with nonzero exit value.
    Test Output
    Assertion #1008 (C): GA12: pathname resolution
    test for ga62 failed
    Command line had unexpected exit value (1)
    'tmp/' was not affected by the command line.
    test for ga63 failed
    Command line had unexpected exit value (1)
    Assertion Result: FAIL

    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