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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0878 Actions

    Problem Report Number 0878
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0393
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1995-11-03 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.upe/vi/vi 12, 23, 27, 52
    Problem Summary TSD4C.00118 These tests may fail on non-ASCII implementations because control characters are not converted properly.
    Problem Text
    These tests may fail on non-ASCII implementations because control
    characters are not converted properly.

    Several vi tests are failing because the Lib/termin.exp script is not
    converting control characters to EBCDIC properly. The referenced
    tests are examples of the failures but we think there are more. The
    error message from termin.exp does not come out in the journal for
    some reason but when we ran test 12 interactively, we saw:

    $ printf "%s" "^F $VI_MARK" | termin -s vi -w20 vi_in_1
    termin: ConvertToControlCharacter: character(F) unknown

    This is because the code for ConvertToControlCharacter is incorrect.
    Here is a sample:

    case $character in {
    $ControlA { return "\x01" } $ControlB { return "\x02" }
    $ControlC { return "\x03" } $ControlD { return "\x37" }

    The global variables such as $ControlA are set by Lib/libexpect.exp:

    set ControlA "\x01"

    So in essence, Lib/termin.exp is doing:

    case $character in {
    "\x01" { return "\x01" } "\x02" { return "\x02" }
    "\x03" { return "\x03" } "\x04" { return "\x37" }

    but $character is the character "in the clear" (for instance, the
    letter "A"). We believe Lib/termin.exp should be changed to something
    like:

    case $character in {
    "A" { return "\x01" } "B" { return "\x02" }
    "C" { return "\x03" } "D" { return "\x37" }

    When we re-ran the tests with a corrected Lib/termin.exp, these vi
    tests were successful.
    Test Output
    Assertion #12 (C): -w option sets default window size for scrolling
    Expected exit code = 0; Received 2
    Standard error isn't empty
    Contents of out.stderr:
    Expecting line 19, was line not-found
    Command failed: 'checkline vi_in_1 "1 + 20 - 2"'

    Assertion #23 (C): COLUMNS environment variable specifies screen width
    Expected exit code = 0; Received 2
    Standard error isn't empty
    Contents of out.stderr:
    Expecting line 21, was line not-found
    Command failed: 'checkline vi_in_1 "22 - 1"'

    Assertion #27 (C): LINES environment variable specifies screen depth
    Expected exit code = 0; Received 2
    Standard error isn't empty
    Contents of out.stderr:
    Expecting line 8, was line not-found
    Command failed: 'checkline vi_in_1 "10 - 2"'

    Assertion #52 (C): refreshing when cursor near start of file
    Expected exit code = 0; Received 2
    Standard error isn't empty
    Contents of out.stderr:
    Standard output isn't the same as file 'vi_exp_1'
    diff of "out.stdout" and "vi_exp_1":
    *** out.stdout Thu Oct 26 15:20:13 1995
    --- vi_exp_1 Thu Oct 26 15:19:28 1995
    ***************
    *** 1,4 ****
    ! 01:
    02:
    03:
    04:
    --- 1,4 ----
    ! a01:
    02:
    03:
    04:

    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