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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0096 Actions

    Problem Report Number 0096
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0096
    Raised 1993-10-08 08:00
    Updated 2003-03-13 08:00
    Published 1993-10-15 08:00
    Product Standard X Window System Applications Interface
    Certification Program The Open Brand certification program
    Test Suite VSW version 4.1.1
    Test Identification CH08/cnfgrrqst/cnfgrrqst 1 3 6
    Problem Summary TSD4.096 These fails occur only in the network case, not in the local case. All fails are due to the fact that the routine winh_harvest(), inside the file xtest/src/lib/winh.c, doesn't do any retry after XPen...
    Problem Text
    These fails occur only in the network case, not in the local case.
    All fails are due to the fact that the routine winh_harvest(),
    inside the file xtest/src/lib/winh.c, doesn't do any retry after
    XPending returns 0.
    When XPending returns 0, this only means that the client has not received
    a given event so far.
    Instead, the suite assumes that the client has not received,
    and WILL NOT receive, the event.
    We have experimented that the server actually SENDS the event, and the
    client RECEIVES it, but it
    arrives AFTER win_harvest (and the subsequent
    XPending) is called.
    A proof of this is that if we spend a little time before calling
    win_harvest() (e.g. by inserting a printf), the event is correctly found.

    We believe that the loop starting at the first instruction of
    win_harvest(), which is

    while (XPending(display) > 0) {

    should be modified and a wait condition (with a reasonable number of
    retries) should be inserted.
    Test Output
    Test-Set Name: /tset/CH08/cnfgrrqst/cnfgrrqst
    ---------------------------------------------

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

    Test-Set Started: 22:11:22

    Test Results:

    ************************************************************************
    /tset/CH08/cnfgrrqst/cnfgrrqst 1 Failed


    Test Agency: Olivetti System Tested: i486-5020-EVC
    Test Date: Aug 25, 1993 Page 239 of 427




    X/OPEN Window Management Verification Suite Release 4.1.1
    Test-Set Summary Test-Set Summary



    Test Description:
    When a ConfigureRequest event is generated, then all
    clients having set SubstructureRedirectMask event mask bits
    on the parent of the window for which the configure request
    was issued are delivered a ConfigureRequest event.

    Test Strategy:
    Create clients client2 and client3.
    Build and create window hierarchy.
    Create inferiors with override-redirect set to True.
    Select for ConfigureRequest events using SubstructureRedirectMask.
    Select for no events with client3.
    Raise lowest window to top.
    Verify that no events were delivered.
    Verify that no events were delivered to client3.
    Lower window back to original placement.
    Set the override-redirect flag on inferiors to False.
    Attempt to raise lowest window to top.
    Initialize for expected events.
    Verify that a ConfigureRequest event is delivered.
    Verify that no events are delivered to client3.
    Verify members of event structure.
    Verify that no events were delivered to client3.

    Test Information:
    Expected ConfigureRequest event on window 0x400003 from client 0x80bdc70
    Event delivery not as expected
    ************************************************************************

    ************************************************************************
    /tset/CH08/cnfgrrqst/cnfgrrqst 3 Failed

    Test Description:
    When a ConfigureRequest event is delivered and a sibling
    attribute was specified in the protocol request issued on
    the child window, then above is set to the value of the
    sibling attribute specified in the protocol request.

    Test Strategy:
    Create clients client2 and client3.
    Build and create window hierarchy.
    Select for ConfigureRequest events using SubstructureRedirectMask.
    Select for no events with client3.
    Raise lowest window to just below the top window.
    Initialize for expected events.
    Verify that a ConfigureRequest event is delivered.
    Verify that no events are delivered to client3.
    Verify members of event structure.
    Verify that no events were delivered to client3.

    Test Information:
    Expected ConfigureRequest event on window 0x400008 from client 0x80bdc70
    Event delivery not as expected


    Test Agency: Olivetti System Tested: i486-5020-EVC
    Test Date: Aug 25, 1993 Page 240 of 427




    X/OPEN Window Management Verification Suite Release 4.1.1
    Test-Set Summary Test-Set Summary


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

    ************************************************************************
    /tset/CH08/cnfgrrqst/cnfgrrqst 6 Failed

    Test Description:
    When a ConfigureRequest event is delivered and a stack-mode
    attribute was not specified in the protocol request issued
    on the child window, then detail is set to None.

    Test Strategy:
    Create clients client2 and client3.
    Build and create window hierarchy.
    Select for ConfigureRequest events using SubstructureRedirectMask.
    Select for no events with client3.
    Attempt to change window's border width.
    Initialize for expected events.
    Verify that a ConfigureRequest event is delivered.
    Verify that no events are delivered to client3.
    Verify members of event structure.
    Verify that no events were delivered to client3.

    Test Information:
    Expected ConfigureRequest event on window 0x40000d from client 0x80bdc70
    Event delivery not as expected
    ************************************************************************

    Test-Set Ended: 22:11:47

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

    7 Tests Executed
    3 Tests Failed
    4 Tests Not In Use


    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 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