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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0215 Actions

    Problem Report Number 0215
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0215
    Raised 1995-05-31 08:00
    Updated 2003-03-13 08:00
    Published 1995-06-05 08:00
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.3.5
    Test Identification POSIX.os/dataform/cpio&tar
    Problem Summary TSD4.215 These tests have ASCII dependencies making them difficult or impossible to run on platforms that do not use the ASCII character set. The format of the cpio and tar files are established to be ASCII an...
    Problem Text
    These tests have ASCII dependencies making them difficult or impossible
    to run on platforms that do not use the ASCII character set.

    The format of the cpio and tar files are established to be ASCII and our
    utilities expect this to be true. However, our native character set is
    EBCDIC so the tests fail be cause of one of the following reasons:

    - the suite creates an archive with header data consisting
    of EBCDIC characters which our utilities will not recognize,
    exiting with a non-zero return code.

    - one of our utilities creates an archive using ASCII data in
    the header but the suite does not recognize the data and
    signals a failure.

    The tests should be modified to ensure that the archives are created in
    the ASCII character set. Also, the tests should not assume that the
    native character set is ASCII. When reading archives created by
    utilities, the suite should allow for translation from ASCII to the
    native character set.

    We have done some work on our own trying to modify the cpio*.sh and
    tar*.sh scripts in TESTROOT/BIN to do this conversion ourselves. We
    have had success with cpio but not with tar because tar archives contain
    checksums fields. The checksums will not agree because the suite and
    our utilities are calculating cksums based on different character sets.
    In addition, we feel the scripts were intended to be simple wrappers and
    our changes are more significant than were expected. We believe the C
    code making up the tests tests should be changed to perform the
    conversions rather than changing the scripts.

    Currently, we are seeing failures or unresolved results in the following
    tests because of ASCII dependencies:

    POSIX.os/dataform/cpio 1,3-28
    POSIX.os/dataform/tar 1,5,7-11,13-16,18-23,24-29,31-34,36-38
    Test Output
    /tset/POSIX.os/dataform/cpio/T.cpio 1 Unresolved

    Test Description:
    For the XNFS specification:
    When an archive is restored by a process with appropriate
    privileges on to a remote file system and the server does not map
    the process's effective user ID, then the archive contents shall
    be restored with user and group IDs and permissions exactly as
    recorded on the medium.
    For the XSH specification:
    A process with appropriate permissions shall restore the ownership
    and permissions exactly as recorded on the medium.
    Posix Ref: Component Data Interchange Format Assertion 10.1-10(C)

    Test Information:
    deletion reason: format reading utility gave unexpected exit code 1

    /tset/POSIX.os/dataform/tar/T.tar 1 Unresolved

    Test Description:
    When the prefix is an empty string, then the pathname of the file is
    name.
    Posix Ref: Component TAR Assertion 10.1.1-15(A)

    Test Information:
    deletion reason: format reading utility gave unexpected exit code 1

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted as a test suite fault and it is recommended that
    it is treated as a test suite deficiency.

    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