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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2571 Actions

    Problem Report Number 2571
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1334
    Raised 2011-12-23 18:00
    Updated 2012-01-10 12:10
    Published 2012-01-10 12:10
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.3.3
    Test Identification POSIX.shell/shell/sh_05.ex 352
    Specification Commands and Utilities Issue 4 Version 2
    Location in Spec Section 2.6.3 in page 36.
    Problem Summary The test is wrong to expect $((echo sh_352.24) ) to be treated as a
    command substitution.
    Problem Text This unit /tset/POSIX.shell/shell/sh_05.ex #352 failed in our USS.
    It failed in following command:
    /vsc> echo $((echo sh_352.24) )
    FSUM7729 missing closing ")"

    The expect result is a string line "sh_352.24".
    This unit treats these expressions to be "command substitution".
    We think this is incorret.
    Our USS thinks these are Arithmetic Expansion.
    Because there is a statement in the page 37 of C436 book.

    ***********************************************************************
    If the command substitution consists of a single subshell, such as:
    $( (command))
    a portable application must separate the $( and ( into two tokens (that
    is, separate them with white space). This is required to avoid any
    ambiguities with arithmetic expansion.
    ***********************************************************************

    As we see, there is no blank between $( and ( , so this should not be a
    command substitution, it should be a Arithmetic expansion. And if it
    is a Arithmetic expansion, there should be no blank between the
    first ")" and the second ")". This a syntax error.

    Another command in the same unit has the similar problem.

    /vsc> echo $((echo sh_352.25a);(echo sh_352.25b))
    FSUM7729 missing closing ")"

    So we think we could apply a TSD for this issue. We need your
    permission.
    Test Output 10|0 /tset/POSIX.shell/shell/sh_05.ex 06:20:01|TC Start, scenario ref
    1-0, ICs: {352}
    15|0 3.8 1|TCM Start
    400|0 352 1 06:20:02|IC Start
    200|0 67 06:20:02|TP Start
    520|0 67 66097 1 1|Assertion #352 (A): All characters within the
    parentheses of the command substitution expression constitute the command
    520|0 67 66097 2 1|Expected exit code = 0; Received 1
    520|0 67 66097 2 2|Standard output isn't the same as file 'sh_352.eso'
    520|0 67 66097 2 3|diff of "out.stdout" and "sh_352.eso":
    520|0 67 66097 2 4|*** out.stdout Fri Dec 23 06:20:04 2011
    520|0 67 66097 2 5|--- sh_352.eso Fri Dec 23 06:20:04 2011
    520|0 67 66097 2 6|***************
    520|0 67 66097 2 7|*** 23,25 ****
    520|0 67 66097 2 8|--- 23,30 ----
    520|0 67 66097 2 9| sh_352.21 bcd abc
    520|0 67 66097 2 10| sh_352.22 99
    520|0 67 66097 2 11| sh_352.23
    520|0 67 66097 2 12|+ sh_352.24
    520|0 67 66097 2 13|+ sh_352.25a sh_352.25b
    520|0 67 66097 2 14|+ sh_352.26
    520|0 67 66097 2 15|+ sh_352.27 ) ) )
    520|0 67 66097 2 16|+ sh_352.28 )
    520|0 67 66097 2 17|Standard error isn't empty
    520|0 67 66097 2 18|Contents of out.stderr:
    520|0 67 66097 2 19|sh_352.sh 39: FSUM7729 missing closing ")"
    220|0 67 1 06:20:04|FAIL
    410|0 352 1 06:20:04|IC End
    80|0 0 06:20:05|TC End, scenario ref 1-0

    Review Information

    Review Type TSMA Review
    Start Date 2011-12-23 18:00
    Last Updated 2012-01-03 09:36
    Completed 2012-01-03 09:36
    Status Complete
    Review Recommendation Test Suite Deficiency (TSD)
    Review Response This is accepted as a fault in the test suite.

    Review Type SA Review
    Start Date 2012-01-03 17:36
    Last Updated 2012-01-10 12:00
    Completed 2012-01-10 12:00
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion This is accepted as a fault in the test suite.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority