diff options
| author | Kenneth Graunke <kenneth@whitecape.org> | 2012-11-14 21:28:08 -0800 |
|---|---|---|
| committer | Kenneth Graunke <kenneth@whitecape.org> | 2013-01-03 13:40:41 -0800 |
| commit | 42a5b472c9f9fc7592b75b229495a77d3c8e4485 (patch) | |
| tree | bba481d1fba1e35249d05b6d40fe995ea3040daf /tests/glean/ttexture_srgb.cpp | |
| parent | 20ec126d4b0b2a7bcbc62c76ae9f780828994c04 (diff) | |
glean: Remove support for comparing result databases.
I suspect most people simply use piglit-summary-html.py to compare
results across test runs. Piglit also supports comparing more than two
test runs.
In some cases, Glean's code did offer more detailed information such as
image comparisons (although not all tests implemented such features).
However, I doubt anyone was using this: driver developers typically
analyze failures by hand, comparing not only image results, but also
shader code and hardware state.
Diffstat (limited to 'tests/glean/ttexture_srgb.cpp')
| -rw-r--r-- | tests/glean/ttexture_srgb.cpp | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/tests/glean/ttexture_srgb.cpp b/tests/glean/ttexture_srgb.cpp index a79019ca6..62688cb88 100644 --- a/tests/glean/ttexture_srgb.cpp +++ b/tests/glean/ttexture_srgb.cpp @@ -318,24 +318,6 @@ TextureSRGBTest::logOne(TextureSRGBResult &r) void -TextureSRGBTest::compareOne(TextureSRGBResult &oldR, - TextureSRGBResult &newR) -{ - comparePassFail(oldR, newR); - - if (newR.pass && oldR.pass == newR.pass) { - // XXX - } - else { - env->log << "\tNew: "; - env->log << (newR.pass ? "PASS" : "FAIL"); - env->log << "\tOld: "; - env->log << (oldR.pass ? "PASS" : "FAIL"); - } -} - - -void TextureSRGBResult::putresults(ostream &s) const { if (pass) { |