Created attachment 126626 [details] Results summary Webglc execution is suffering several failures during execution.(Google Chrome). Having about 1425 failures from 22644 available tests. Google chrome is sending the message "Rats! WebGL hit a snag." Software configuration: OS: Ubuntu 16.04 Kernel: 4.7.2 from kernel.org Graphic stack: Component : drm tag : libdrm-2.4.68 Component : mesa tag : mesa-12.0.1 Component : xf86-video-intel tag : 2.99.917-701-g205146b Component : libva tag : libva-1.7.2.pre1 Component : intel-driver tag : 1.7.2.pre1 Component : cairo tag : 1.15.2 Component : xserver tag : xorg-server-1.18.3 Component : macros tag : util-macros-1.19.0-2-gd7acec2 Component : intel-gpu-tools tag : intel-gpu-tools-1.16 Execution: 1.-Download google chrome latest stable version 2.-Open Google chrome with the following command line in terminal " google-chrome --enable-webgl --ignore-gpu-blacklist" 3.-On the browser click over "run test" button Expected result: The tests should run smoothly without pauses or error messages on the status bar. Actual result: As it is described before the browser sends a lot of failures on results html and is constantly sending "Rats! WebGL hit a snag." Attaching logs and results
Created attachment 126627 [details] Dmesg
Forgot to include the website: www.khronos.org/registry/webgl/conformance-suites/1.0.3/webgl-conformance-tests.html
(In reply to Elio from comment #2) > Forgot to include the website: > > www.khronos.org/registry/webgl/conformance-suites/1.0.3/webgl-conformance- > tests.html Some time ago we had a similar bug, but for 1.0.2 conformance test. At that time only two were failing, and after triaging them, the problem were related to Chromium exposing shaders with version #130 instead of #100 (the one used in opengl ES 1.0, that is the one used on WebGL 1.0). More details here: https://bugs.freedesktop.org/show_bug.cgi?id=62510#c8 Probably it would be worth to check if Chromium keeps doing that version error.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1538.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.