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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1660 Actions

    Problem Report Number 1660
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0054
    Raised 2003-02-25 08:00
    Updated 2003-03-13 08:00
    Published 2003-03-05 08:00
    Expiry Date 2004-03-04
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.1.2
    Test Identification CAPI.os/genuts/nftw 25
    Problem Summary MSF4U.00015 The test fails when run in the normal order, but passes when run first.
    Problem Text
    This test passes if run standalone, looks like a test harness problem. Following is the pass result.

    10|0 /tset/CAPI.os/genuts/nftw/T.nftw 14:34:11|TC Start, scenario ref 1-0, ICs: {25}
    15|0 3.4-lite 1|TCM Start
    400|0 25 1 14:34:11|IC Start
    200|0 25 14:34:11|TP Start
    520|0 25 00010016 1 1|PREP: Prepare path names
    520|0 25 00010016 1 2|TEST: The function nftw should return with value set by fn
    520|0 25 00010016 1 3|INFO: Call to fn() at ../tmp/data/dirh
    520|0 25 00010016 1 4|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1
    520|0 25 00010016 1 5|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1/dir_left.2
    520|0 25 00010016 1 6|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1/dir_left.2/left.3
    520|0 25 00010016 1 7|INFO: fn() returning non-zero after traversal of 4 objects
    220|0 25 0 14:34:13|PASS
    410|0 25 1 14:34:13|IC End
    80|0 0 14:34:13|TC End, scenario ref 1-0
    900|14:34:13|TCC End

    Test Output
    400|0 25 1 13:33:41|IC Start
    200|0 25 13:33:41|TP Start
    520|0 25 00000568 1 1|PREP: Prepare path names
    520|0 25 00000568 1 2|TEST: The function nftw should return with value set by fn
    520|0 25 00000568 1 3|INFO: Call to fn() at ../tmp/data/dirh
    520|0 25 00000568 1 4|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1
    520|0 25 00000568 1 5|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1/dir_left.2
    520|0 25 00000568 1 6|INFO: Call to fn() at ../tmp/data/dirh/dir_left.1/dir_left.2/left.3
    520|0 25 00000568 1 7|INFO: fn() returning non-zero after traversal of 4 objects
    520|0 25 00000568 1 8|INFO: Call to fn() at ../tmp/data/dirh/dir_right.1
    520|0 25 00000568 1 9|INFO: Call to fn() at ../tmp/data/dirh/dir_right.1/dir_right.2
    520|0 25 00000568 1 10|INFO: Call to fn() at ../tmp/data/dirh/dir_right.1/dir_right.2/right.3
    520|0 25 00000568 1 11|INFO: fn() returning non-zero after traversal of 7 objects
    520|0 25 00000568 1 12|ERROR: nftw() did not return immediately on non-zero fn() return
    220|0 25 1 13:33:42|FAIL
    410|0 25 1 13:33:42|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The submitter's rationale for claiming that this failure is caused
    by a test suite fault is rather weak. It is based on an assumption
    that because the test passes when run on its own, something that the
    test suite does in the earlier tests must be causing the failure.

    It is true that something in the earlier tests must indirectly be
    affecting the behaviour of the nftw() call made in test 25. However,
    it may be that the sequence of API calls made in those tests has
    triggered a subtle implementation fault which is the direct cause
    of the failure.

    Looking at the "INFO" lines in the test output, it seems to me that
    an implementation fault is more likely to be the direct cause than
    a test suite fault, since they clearly show that nftw() made further
    calls to the fn() callback function after an fn() call had returned
    a non-zero value.

    In my view a sufficient case has not been made to justify granting
    a TSD. However, if the submitter is willing, a temporary waiver
    for a minor system fault could be granted, thus allowing time for
    the cause of the failure to be investigated without holding up the
    product registration.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Minor System Fault (MSF)
    Review Conclusion
    A Temporary Waiver is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority