Bug 49321 - shadertoy failure
Summary: shadertoy failure
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 8.0
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-30 22:05 UTC by Erno Kuusela
Modified: 2012-08-08 16:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Erno Kuusela 2012-04-30 22:05:41 UTC
Full report @ http://groups.google.com/group/webgl-driver-testing/browse_thread/thread/14e726ff2da20438

Partial paste from above:


This run was on Ubuntu 10.10 amd64 with self compiled 
Mesa 3.0.2 (+deps, like libdrm 2.4.33 and llvm 3.0), 
Firefox nightly 15.0~a1~hg20120428r92608-0ubuntu1~umd1~lucid 
from http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu 
and Linux 3.1.0. 

Also I notice about half of 
the shaders at  http://www.iquilezles.org/apps/shadertoy/ fail 
(eg. Motion Blur shows just two brown rectangles, Flower 
a flashing green box) 

WebGL Conformance Test Runner 
Version 1.0.1 
Results: (8827 of 8863 passed) 
WebGL Conformance Test Results 
Version 1.0.1 
------------------- 
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20120425 Firefox/15.0a1 
WebGL VENDOR: Mozilla 
WebGL VERSION: WebGL 1.0 
WebGL RENDERER: Mozilla 
Unmasked VENDOR: undefined 
Unmasked RENDERER: undefined 
WebGL R/G/B/A/Depth/Stencil bits (default config): 8/8/8/8/24/0 
------------------- 
Test Summary (8863 total tests): 
Tests PASSED: 8827 
Tests FAILED: 36 
Tests TIMED OUT: 0
Comment 1 Erno Kuusela 2012-05-01 11:46:08 UTC
Typo there in Mesa version, meant 8.0.2.
Comment 2 Andreas Boll 2012-08-08 16:54:14 UTC
(In reply to comment #0)
> Full report @
> http://groups.google.com/group/webgl-driver-testing/browse_thread/thread/14e726ff2da20438
> 
> Partial paste from above:
> 
> 
> This run was on Ubuntu 10.10 amd64 with self compiled 
> Mesa 3.0.2 (+deps, like libdrm 2.4.33 and llvm 3.0), 
> Firefox nightly 15.0~a1~hg20120428r92608-0ubuntu1~umd1~lucid 
> from http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu 
> and Linux 3.1.0. 
> 
> Also I notice about half of 
> the shaders at  http://www.iquilezles.org/apps/shadertoy/ fail 
> (eg. Motion Blur shows just two brown rectangles, Flower 
> a flashing green box) 
> 
> WebGL Conformance Test Runner 
> Version 1.0.1 
> Results: (8827 of 8863 passed) 
> WebGL Conformance Test Results 
> Version 1.0.1 
> ------------------- 
> User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20120425
> Firefox/15.0a1 
> WebGL VENDOR: Mozilla 
> WebGL VERSION: WebGL 1.0 
> WebGL RENDERER: Mozilla 
> Unmasked VENDOR: undefined 
> Unmasked RENDERER: undefined 
> WebGL R/G/B/A/Depth/Stencil bits (default config): 8/8/8/8/24/0 
> ------------------- 
> Test Summary (8863 total tests): 
> Tests PASSED: 8827 
> Tests FAILED: 36 
> Tests TIMED OUT: 0


By now there is only 1 test page of the khronos WebGL conformance test failing with the r600g driver.
This issue is tracked at Bug 44912

So this report should only track the shadertoy failure.
Comment 3 Andreas Boll 2012-08-08 16:59:10 UTC
(In reply to comment #0)
> Full report @
> http://groups.google.com/group/webgl-driver-testing/browse_thread/thread/14e726ff2da20438
> 
> Partial paste from above:
> 
> 
> This run was on Ubuntu 10.10 amd64 with self compiled 
> Mesa 3.0.2 (+deps, like libdrm 2.4.33 and llvm 3.0), 
> Firefox nightly 15.0~a1~hg20120428r92608-0ubuntu1~umd1~lucid 
> from http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu 
> and Linux 3.1.0. 
> 
> Also I notice about half of 
> the shaders at  http://www.iquilezles.org/apps/shadertoy/ fail 
> (eg. Motion Blur shows just two brown rectangles, Flower 
> a flashing green box) 
> 

with current firefox nightly 20120808
and current mesa 8.1-devel (git-be42a45) this site works for me.


Feel free to reopen this report if the issues persist.


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.