[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] High number of failures in conformance suite

Thanks very much for the advice. We don't yet know for sure that the suite passes on Firefox yet. He didn't encounter the original issue within my framework in FF, so hasn't tested the conformance suite in FF yet.

I've just requested that he run the suite on Firefox, and send the text summary. Once I get that, I'll forward all the information on to the Chrome tracker (and the Firefox one if there are a lot of failures there as well).

Thanks again,

On Sun, Oct 7, 2012 at 10:31 AM, Florian Bösch <pyalot@gmail.com> wrote:
The card is not on the list of unsupported devices of Chrome and the OS is on the list of supported operating systems: http://support.google.com/chrome/bin/answer.py?hl=en&answer=1220892

There are lots of errors around texture functions and glsl. I don't see a clear pattern of where it fails other than some tendencies. I would post this information as is to the chrome issue list (http://code.google.com/p/chromium/issues/list) with a title like "webgl 657 conformance tests failed on OSX 10.6/GMA X3100"

There are 3 other issues where people have problems with the GMA X3100

I would mention in the ticket that the conformance works trough in Firefox. The best hope to get to the bottom of this issue would be for a chrome developer with OSX 10.6.8 and a GMA X3100 to try to replicate the issue. Note that one possible outcome of this may be that the X3100 (or its older 10.6 driver) will be blacklisted.

On Sun, Oct 7, 2012 at 4:11 PM, Colin Mackenzie <sinisterchipmunk@gmail.com> wrote:
I had him run the tests again locally and here's what he had to say:

I ran the test locally with the SimpleHTTPServer and the results seem exactly the same :

Tests PASSED: 3241
Tests FAILED: 657
Tests TIMED OUT: 31

Text summary of the tests : https://gist.github.com/3848167
Browser : Chrome 22.0.1229.79
OS : MacOS 10.6.8
GPU Model : GMA X3100
Driver Version : I really don't know about it. I just keep my system up to date. (Maybe these lines are useful ? "Fournisseur : Intel (0x8086) / Identifiant du périphérique : 0x2a02 / Identifiant de révision : 0x0003")



On Sat, Oct 6, 2012 at 5:41 AM, Florian Bösch <pyalot@gmail.com> wrote:
In order to be sure not to run into networking issues, the conformance tests should be run locally.

Once the test have run, there is a button to "display text summary" of the tests. Please collect the following from your user:
- text summary of the tests
- Browser/Version
- Operating System/Version
- GPU Model
- Driver Version

Make this information available here and we should be able to advise appropriate next steps.

On Sat, Oct 6, 2012 at 2:17 AM, Colin Mackenzie <sinisterchipmunk@gmail.com> wrote:
I apologize if this is the wrong forum for my question, and would appreciate being directed toward the proper destination if so.

I'm trying to track down an issue a user of my WebGL framework is experiencing, and in doing so, requested that he run the WebGL conformance suite v1.1. He's running Chrome 22 on Mac OS X 10.6.8 with Intel GMA X3100 graphics. Here's his summary:

    Tests PASSED: 3241
    Tests FAILED: 657
    Tests TIMED OUT: 31

See https://gist.github.com/3840329 for the complete test results.

I have not yet asked him to run the conformance tests in Firefox, because he has indicated that the original issue with my framework does not appear in FF.

Given the high number of failures, what should I advise him to do? Raise an issue with the browser vendor? Or, if this many failures are expected for his platform, should I ignore them and continue working to resolve the issue within my framework?

Not sure if it's helpful, but here's the issue as originally reported to the framework: https://github.com/sinisterchipmunk/jax/issues/63

Colin MacKenzie IV

Colin MacKenzie IV