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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2499 Actions

    Problem Report Number 2499
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0677
    Raised 2006-02-03 02:11
    Updated 2006-02-08 01:59
    Published 2006-02-08 01:59
    Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSART version 1.1.5
    Test Identification POSIX_art.os/timers/clock_settime 1, 2
    Specification Base Definitions Issue 6
    Problem Summary clock_settime 1, 2 do not check correct return value to determine success
    Problem Text The problem with these assertions is the value used to determine whether
    the thread join was successful.

    The code from the assertions has:

    retval = vrtx_pthread_join(thr_main, &retval2);
    if ( retval2 != (void *)0 )
    {
    if ( retval2 == (void *) 1 )
    {
    in_rpt("Thread exited with error", (int) retval2);
    xx_rpt(DELETION);
    DBUG_VOID_RETURN
    }
    else if ( retval2 == (void *) 2 )
    {
    in_rpt("Thread exited with error", (int) retval2);
    xx_rpt(FAILURE);
    DBUG_VOID_RETURN
    }
    }

    It should be checking retval to determine if vrtx_pthread_join() was
    successful, not retval2.

    If this is changed so that retval is checked, the assertions pass.
    Test Output ****************************************************************************************************************
    /tset/POSIX_art.os/timers/clock_settime/T.clock_settime 1
    Failed

    Test Description:
    If {_POSIX_CLOCK_SELECTION} is defined:
    When clock_id is CLOCK_REALTIME, then the new value
    of the clock shall be used to determine the time at
    which the system shall awaken a thread blocked on
    an absolute clock_nanosleep() call based upon the
    CLOCK_REALTIME clock.

    Test Strategy:
    Error: requested file not found in archive

    /export/test/TET3.3h/vsx/MAN/tset/POSIX_art.os/timers/clock_settime/L.clock_settime_s

    Test Information:
    The sleep time should be the difference of the setted absolute
    time and
    current time, plus the time the clock
    set back, expect at least 6, got 0
    Thread exited with error


    ****************************************************************************************************************


    ****************************************************************************************************************
    /tset/POSIX_art.os/timers/clock_settime/T.clock_settime 2
    Failed

    Test Description:
    If {_POSIX_CLOCK_SELECTION} is defined:
    When clock_id is CLOCK_REALTIME, then
    clock_settime(clock_id, tp) has no effect on a
    thread blocked on a relative clock_nanosleep()
    call.

    Test Strategy:
    Error: requested file not found in archive

    /export/test/TET3.3h/vsx/MAN/tset/POSIX_art.os/timers/clock_settime/L.clock_settime_s

    Test Information:
    Test Information:
    The sleep time should be the difference of the setted absolute
    time and
    current time, plus the time the clock
    set back, expect at least -4, got -5
    Thread exited with error


    ****************************************************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date 2006-02-03 02:11
    Last Updated 2006-02-07 01:32
    Completed 2006-02-07 01:32
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response It seems this test is failing for some reason
    that is not clear from the test output. More information is needed and
    it would appear to be better handled by a support route at this point.

    Would seem that the PR should be rejected and the customer advised to
    try the support route.

    Review Type SA Review
    Start Date 2006-02-07 01:32
    Last Updated 2006-02-07 01:56
    Completed 2006-02-07 01:56
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The PR as submitted does not provide sufficient information to
    diagnose the nature of the problem. Further investigation is required
    and a support request should be used as the means of progressing the
    issue. When the nature of the problem is better understood then if
    appropriate another PR can be raised.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority