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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0188 Actions

    Problem Report Number 0188
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0188
    Raised 1994-08-29 08:00
    Updated 2003-03-13 08:00
    Published 1994-09-14 08:00
    Product Standard Network File System
    Certification Program The Open Brand certification program
    Test Suite VSX4+XNFS version 4.3.4
    Test Identification XNFS.prtl/proto/nlm 13
    Problem Summary TSD4.188 I had sent a test error report in, err.4.3.4.006 and the response was "Changed genericcannolck() function to wait for NLM_GRANTED_MSG and send NLM_GRANTED_RES in reply." The original error report stat...
    Problem Text

    I had sent a test error report in, err.4.3.4.006 and the response was
    "Changed genericcannolck() function to wait for NLM_GRANTED_MSG and send
    NLM_GRANTED_RES in reply."

    The original error report stated the following:

    An ip trace taken when running the T.nlm test shows that test #12 sends a
    NLM_GRANTED_MSG when it completes. However, test #12 does not wait to receive
    this message. Thus, test #13 picks this message up. It is my opinion that
    test #12 is in error because it does not wait to receive this message.

    Let me explain my understanding of test #12. On the server side, a file lock
    is obtained. Then the client side tries to obtain a lock on the same file but
    receives a BLOCKED message as expected. Then it tries to cancel the lock
    request but it gets denied. Then the test cases sync up and the server testcase
    unlocks the lock and the client test exits. When the server testcase unlocks
    the lock, since there was an application blocked on the lock (since the cancel
    was denied) the sever will send a NLM_GRANTED. Since test12 dosen't wait for
    that response, test #13 sees it and generates an error.

    Test Output
    200|0 13 09:57:44|TP Start
    520|0 13 00009214 1 1|Expected callback NLM_LOCK_RES (12) received NLM_GRANTED_MS
    G (10).
    520|0 13 00009214 1 2|Expected callback NLM_UNLOCK_RES (14) received NLM_LOCK_RES
    (12).
    520|0 13 00009214 1 3|Expected callback NLM_LOCK_RES (12) received NLM_UNLOCK_RES
    (14).
    520|0 13 00009214 1 4|Expected callback NLM_UNLOCK_RES (14) received NLM_LOCK_RES
    (12).
    220|0 13 1 09:57:44|FAIL
    410|0 13 1 09:57:44|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted to be a test suite fault and it is recommended that a waiver
    be granted for 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