Report 0822 Actions
Problem Report Number |
0822 |
Submitter's Classification |
Specification problem |
State |
Resolved |
Resolution |
Test Suite Deficiency (TSD) |
Problem Resolution ID |
TSD.X.0337 |
Raised |
1970-01-01 08:00 |
Updated |
2003-03-13 08:00 |
Published |
1996-03-19 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 |
POSIX.cmd/read 18 |
Problem Summary |
TSD4C.00174 The request claims that trying to assign values to readonly environment variables via the read command is not a mandated error. |
Problem Text |
The request claims that trying to assign values to readonly environment variables via the read command is not a mandated error. Test purpose read, assertion 18 is testing for non-required XPG4 behavior. The assertion is testing the effect of using a readonly variable in a read statement. The assertion is expecting failure in specific manner. However, XPG4 V2 XCU read section, pages 601-603, does not mention readonly variables at all. In particular the spec does not state that using readonly variables in a read statement is an error. Thus the testcase cannot assume that the exit status should be >0 or that processing of other variables on the read statement will be completed. This assertion needs to be removed and an interpretation submitted to the 1003.2 working group to remove this grey area.
|
Test Output |
*********************************************************************** /tset/POSIX.cmd/read/read.ex 1 Failed Test Information: Assertion #18 (A): second variable set to '', expecting '2' ***********************************************************************
|
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. We believe the test is correct. Although the read utility does not specifically refer to readonly variables, the default Consequences of Errors states the requirements when the requested action cannot be performed on an operand, in this case, a readonly variable. The standard states on page 17, If the requested action cannot be performed on an operand representing a file, directory, user, process, etc., the utility will issue a diagnostic message to standard error and continue processing the next operand in sequence, but the final exit status is returned as non-zero. It is clearly not possible to perform a write operation onto a readonly variable. As a result, the test correctly expects the behavior described above.
|
Review Type |
Expert Group Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
The Base WG response for this item is: req.4.C.00330: The specification is correct. However, since the "Consequences of Errors" section for read is defined as "Default", and this states that any changes to the environment are unspecified, the test suite cannot test that the second value is assigned to the second variable. It can only test that the assignment to the readonly variable fails in the appropriate manner. The confusion arises because read exists solely to modify the environment.
|
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:
|