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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2005 Actions

    Problem Report Number 2005
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0591
    Raised 1997-09-04 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Transport Service XTI
    Certification Program The Open Brand certification program
    Test Suite VST version 4.1.4
    Test Identification XTI.os/common/sync 3
    Problem Summary PGT4R.020 The test T.sync 3 is reporting a 'Unresolved' result due to an error in the DTET2 test-suite harness. The problem is that there is no function prototype in scope for inet_ntoa() when it is invoked i...
    Problem Text

    The test T.sync 3 is reporting a 'Unresolved' result due to an
    error in the DTET2 test-suite harness.
    The problem is that there is no function prototype in scope for
    inet_ntoa() when it is invoked in tstcmenv.c. inet_ntoa() returns
    a 64-bit pointer but due to the lack of a prototype the compiler
    assumes a default return of a 32-bit int, resulting in a
    SIG_SEGV error that prevents the test being run.

    The function prototype for inet_notoa() is in
    /usr/include/arpa/inet.h, however tstcmenv.c does not include
    this, it includes socket.h instead:

    #ifdef __hpux
    #include <sys/socket.h>
    #else
    #include <arpa/inet.h>
    #endif

    The file tstcmenv.c should be including arpa/inet.h. When
    it is modified to do so the test T.sync 3 succeeds.

    Test Output

    Output to console:

    tetxresd (xresd.c, 201): client connection closed (sysid = 0, pid = 3803: MTCM)
    tetsyncd (syncd.c, 225): client connection closed (sysid = 0, pid = 3803: MTCM)
    tetxresd (xresd.c, 201): client connection closed (sysid = 0, pid = 3804: MTCM)
    tetsyncd (syncd.c, 225): client connection closed (sysid = 0, pid = 3804: MTCM)



    Formatted test report:


    Test-Set Name: /tset/XTI.os/common/sync/T.sync
    ----------------------------------------------

    Test-Set Results:
    ----------------

    Test-Set Started: 14:50:03
    *** TCM/API Message: system 1: tet_msync() failed, syncptno = 0, request timed out after waittime of 100 seconds ***
    *** TCM/API Message: system 1: system = 0, state = NOT-SYNCED ***

    Test Results:

    ************************************************************************
    /tset/XTI.os/common/sync/T.sync 3 Unresolved

    Test Description:
    When fd is a file descriptor which is not closed on a call to exec()
    and the original file descriptor in the calling process refers to a
    transport endpoint, then a call to t_sync( fd) returns the current
    state of the transport endpoint associated with fd and converts the
    uninitialised file descriptor into an initialised transport endpoint.
    Testing Requirement(s):
    Test for each state that can be associated with the transport
    endpoint and test for the case that the state of the transport
    endpoint has been changed between the call to exec() and the call
    to t_sync().

    Test Information:
    child process was terminated by signal 11 (SIGSEGV)
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()
    getsv_m() failed in provsetup()

    Test Information From Slave:
    getsv_s() failed to read instructions from master
    ************************************************************************

    Test-Set Ended: 14:52:35

    Test-Set Results Summary:
    ------------------------

    1 Tests Executed
    1 Tests Unresolved


    Area Name: XTI.os/common
    ------------------------

    Area Started: 14:50:03

    Test Set Failed FIP Uninit'ed Untested Unreported
    Executed Warnings Unreslved Unsupported NotInUse
    TOTAL 1 0 0 0 1 0 0 0 0 0

    Area Ended: 14:52:35


    Failed Unresolved Uninitiated Unsupported

    sync 3

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The DTET2 harness is not a part of the test suite and it is the responsibility
    of those executing the test suite to correct any faults in the harness that
    are causing problems in the tests. The code highlighted above was included
    in order to resolve differences between systems at the time that DTET2 was
    written and is no longer necessary because these operating systems have now
    aligned to the XNET specifications. An alternative solution would be to use
    the more recent TETWare distribution which avoids these problems.

    IT is recommended that this request is refused.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused, we recommend the workaround suggested above.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority