|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 0566 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 0566.
Report 0566 Actions
Problem Report Number 0566 Submitter's Classification Test Suite problem State Resolved Resolution Rejected (REJ) Problem Resolution ID REJ.X.0170 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published null Product Standard Commands and Utilities V3 (UNIX 98) Certification Program The Open Brand certification program Test Suite VSC version 5.0.1 Test Identification XOPEN.cmd/unlink 1027, 1028, 1029, 1030, 1032 Problem Summary PG4C.00107 This IR claims that diagnostic error messages are not required when a file operand fails to be processed. Problem Text
This Interpretation Request is for the following assertions:
unlink 1027, 1028, 1029, 1030, 1032
These tests failed because output is expected on stderr when
the exit status is >0. This is not an XPG5 requirement. Page
766 states:
"STDERR Used only for diagnostic messages"
Notice that this section makes no requirements for producing
diagnostic messages, only where they will be directed to if
produced.
On Page 767 it states:
"Exit Status The following exit values are returned:
0 Successful completion.
>0 An error occurred."
No requirement has been made here for diagnostic messages to
be produced when exit status is >0.
Test Output
***********************************************************************
/tset/XOPEN.cmd/unlink/unlink.ex 1 Failed
Test Information:
Assertion #1027 (D):
"." wasn't found in standard error
***********************************************************************
***********************************************************************
/tset/XOPEN.cmd/unlink/unlink.ex 1 Failed
Test Information:
Assertion #1028 (A):
"." wasn't found in standard error
***********************************************************************
***********************************************************************
/tset/XOPEN.cmd/unlink/unlink.ex 1 Failed
Test Information:
Assertion #1029 (A):
"." wasn't found in standard error
***********************************************************************
***********************************************************************
/tset/XOPEN.cmd/unlink/unlink.ex 1 Failed
Test Information:
Assertion #1030 (A):
"." wasn't found in standard error
***********************************************************************
***********************************************************************
/tset/XOPEN.cmd/unlink/unlink.ex 1 Failed
Test Information:
Assertion #1032 (A):
"." wasn't found in standard error
***********************************************************************
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.
It is correct to say that the STDERR section makes no requirements on
when diagnostic error output is produced. The requirement is derived
from a different section.
Section 1.9 of the Command and Utilities standard states
under the Consequences of Errors section:
The following apply to each utility, unless otherwise stated:
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.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Rejected (REJ) Review Conclusion
This request is refused.
Problem Reporting System Options:
- View Report 0566
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority