Created attachment 22117 [details]
OSD: Fedora release 9 (Sulphur)
Xserver_stable: (server-1.6-branch) 251d0d8090322b2c9dc0c8b7bef001f338d19433
Bug detailed description:
On 915 or 945 machines, run the test case of fbo in glean cases then you will find "rendering to depth texture failed".
3. run the glean cases.
Created attachment 22118 [details]
Created attachment 22119 [details]
test result of fbo
(In reply to comment #3)
But I find it failed from 20080826, the day GL_EXT_framebuffer_object was supported. Before that it was not supported.
OK, we don't really expect bug reports for always-failing testcases at this point -- our priority is regressions and improving issues that are impacting applications.
This was a bug in the testcase when handling an unsupported framebuffer in a previous test. Yet another reason why you should never build tests that test more than one thing at a time.
Author: Eric Anholt <email@example.com>
Date: Fri Sep 24 11:28:49 2010 -0700
glean/tfbo: Properly clean up when the driver reports unsupported.
Fixes spurious test failures on the intel driver.
It still fails on Pineview now with the same error info as following.
libGL: OpenDriver: trying /opt/X11R7/lib/dri/i915_dri.so
GL_EXT_framebuffer_object is supported
GL_ARB_framebuffer_object is not supported
depth = 0, stencil = 1
(0, 0) = [0.000000, 0.000000, 0.000000], is expected to be[1.000000, 0.000000, 0.000000]
FAILURE: Render to single texture failed (at tfbo.cpp:850)
mode = 2
depth = 1, stencil = 0
(14, 0) = [0.749020, 0.749020, 0.749020], is expected to be[1.000000, 1.000000, 1.000000]
FAILURE: Render to depth texture failed (at tfbo.cpp:1155)
fbo: FAIL rgba8, db, z24, s8, win+pmap, id 33
6 tests passed, 2 tests failed.
Kernel: (drm-intel-next) 608ca70d22c0ea0d52aa71f52b8e326055c274d1
some more info is I tested it with both the glean source contained in piglit test and the glean source from glean.git.sourceforge.net.
-- 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/672.