|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2494 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 2494.
Report 2494 Actions
Problem Report Number 2494 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1295 Raised 2005-12-13 16:08 Updated 2005-12-14 22:51 Published 2005-12-14 22:51 Product Standard Commands and Utilities V4 (UNIX 03) Certification Program The Open Brand certification program Test Suite VSC version 5.2.7 Test Identification POSIX.upe/file[1] Specification Shell and Utilities Issue 6 Problem Summary This test may fail on non-ASCII implementations because of a hard-
coded ASCII character.Problem Text This test may fail on non-ASCII implementations because of a hard-
coded ASCII character.
This test has a dependancy on the ASCII encoding for the '_' character
(octal 137). The script has the following statement:
-------mfile_type----------
0 d1 =10 Message: %d
0 d1 =0x10 Message: %d
0 d1 =010 Message: %d
0 s string_type Message: %s
0 s octal\137string\137type Message: %s
0 s esc\\\a\bchar\f\n\rstring\t\v\ type Message: %s
0 u1 =10 Message: %u
---------------------------------
-------file.sh Line 382----------
echo "octal_string_type" > file_1_octal_string_type.tmp
---------------------------------
-------file.sh Line 610----------
# Test with the octal string type field.
file -m mfile_type file_1_octal_string_type.tmp > $CT_STDOUT 2>
$CT_STDERR
CT_EXIT_VALUE=$?
# Verify the exit status is zero.
# Verify the standard output contains the string:
# "file_1_octal_string_type.tmp: Message: octal_string_type".
if [ $CT_EXIT_VALUE -ne 0 ]; then
SetResult $TET_FAIL "Expected exit code = 0; Received
$CT_EXIT_VALUE"
else
SetResult $TET_PASS
fi
grep -e "file_1_octal_string_type.tmp: Message: octal_string_type"
$CT_STDOUT > /dev/null
---------------------------------
octal 155 is the proper representation for the '_' character on our
implementation. This test has a hard-coded dependency for the value
of the '_' character.
mfile_type should be dynamically generated.
e.g. on an ASCII platform, mfile_type should be following:
-------mfile_type for ASCII------
0 d1 =10 Message: %d
0 d1 =0x10 Message: %d
0 d1 =010 Message: %d
0 s string_type Message: %s
0 s octal\137string\137type Message: %s
0 s esc\\\a\bchar\f\n\rstring\t\v\ type Message: %s
0 u1 =10 Message: %u
---------------------------------
on an EBCDIC platform,mfile_type should be following:
-------mfile_type for EBCDIC-----
0 d1 =10 Message: %d
0 d1 =0x10 Message: %d
0 d1 =010 Message: %d
0 s string_type Message: %s
0 s octal\155string\155type Message: %s
0 s esc\\\a\bchar\f\n\rstring\t\v\ type Message: %s
0 u1 =10 Message: %u
---------------------------------Test Output 400|1 1 1 01:10:17|IC Start
200|1 1 01:10:17|TP Start
520|1 1 50331702 1 1|Assertion #1 (C): file -m <magic file> testfile
520|1 1 50331702 4 1|"file_1_octal_string_type.tmp: Message:
octal_string_type" wasn't found in standard output
220|1 1 1 01:10:19|FAIL
410|1 1 1 01:10:19|IC EndReview Information
Review Type TSMA Review Start Date 2005-12-13 16:08 Last Updated 2005-12-13 17:12 Completed 2005-12-13 17:12 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 2005-12-13 17:12 Last Updated 2005-12-14 02:49 Completed 2005-12-14 02:49 Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion This Pr represents an agreed test suite deficiency
Problem Reporting System Options:
- View Report 2494
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority