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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1754 Actions

    Problem Report Number 1754
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0537
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 4.1.1
    Test Identification tset/CH06/drwrctngls 77 78
    Problem Summary PG4W.00046 The test fails because the difference between expected and actual pixelization exceeds limits specified for the test.
    Problem Text
    All failures are due to pixel checking. The component "X Window System
    Application Interface V2" is not responsible for these errors, which are
    caused by the X server, or, in some cases, by the lack of pixelization
    rules inside the specifications.
    Test Output

    Test 77: FAIL
    --- Running test with visual class PseudoColor, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0000.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0001.err for results
    --- Running test with visual class DirectColor, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0002.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0003.err for results
    --- Running test with visual class GrayScale, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0004.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0005.err for results
    --- Running test with visual class StaticColor, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0006.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0007.err for results
    --- Running test with visual class TrueColor, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0008.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0009.err for results
    --- Running test with visual class StaticGray, depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0010.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0011.err for results
    --- Running test with pixmap depth 1
    --- Running test with pixmap depth 8
    A total of 43 out of 9000 pixels were bad
    Pixel check failed. See file Err0012.err for results
    A total of 42 out of 9000 pixels were bad
    Pixel check failed. See file Err0013.err for results

    Test 78: FAIL
    --- Running test with visual class PseudoColor, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0014.err for results
    --- Running test with visual class DirectColor, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0015.err for results
    --- Running test with visual class GrayScale, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0016.err for results
    --- Running test with visual class StaticColor, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0017.err for results
    --- Running test with visual class TrueColor, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0018.err for results
    --- Running test with visual class StaticGray, depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0019.err for results
    --- Running test with pixmap depth 1
    --- Running test with pixmap depth 8
    A total of 19 out of 9000 pixels were bad
    Pixel check failed. See file Err0020.err for results


    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    - The tests which are failing are outside the set that are agreed to be
    overly restrictive in checking pixilization. Since the tests are not
    flawed, TSDs cannot be recommended (such waivers could be used by
    vendors branding the Display Component to justify server failures
    that should not be allowed).

    - While these failures may well be due to server problems, this
    cannot be clearly determined. Thus, while branding the Application
    Interface does not require a branded server, one sufficiently compliant
    that errors of this sort do not occur is a necessary part of the test
    environment. We suggest the submitter run the tests using a more
    compliant server in order to generate clean results for branding.

    Second Opinion
    --------------

    The submitter states that the pixelisation rules are not contained in the
    specification. Pixelisation rules are precisely defined in the X Window
    System by Scheiffler, Gettys and Newman and these rules are followed in the
    test suite. These rules have been accepted as part of the definition of
    the X Window system and are believed to have been accepted as part of the
    X/Open specification (though we can find no normative reference to this
    in the X/Open specification).

    Accepting the pixelisation differences requested above is not recommended.

    The other rationale supplied by the submitter relates to the fact that the
    problem is purely a server problem and is not related to the client. This
    may or may not be the case. It is possible that these pixelisation problems
    are caused by an error in the protocol request from the client. The VSX test
    suite does not attempt to distinguish between server and client side errors,
    since the only practical use of the X Window system is with both a client and
    a server. If the problem is purely server side, then we would suggest that
    the tests are re-run with a conforming server. It is only in this way that
    the source of the problem can be determined.

    We recommend that this waiver request is refused.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority