| Age | Commit message (Collapse) | Author |
|---|
|
Test written by Vadim Girlin <vadimgirlin@gmail.com>. I added
explanatory comments.
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
Add a test that creates two contexts and concurrently
compiles shader programs to test race conditions of
the shader compiler.
v3: (Tom Stellard)
- Report pass at the end of the tests
- Add as a concurrent test
v4: (Mathias Froehlich)
- Fix comment style
Signed-off-by: Mathias Froehlich <Mathias.Froehlich@web.de>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
Reviewed-By: Aaron Watry <awatry@gmail.com>
|
|
Reviewed-By: Aaron Watry <awatry@gmail.com>
|
|
Reviewed-By: Aaron Watry <awatry@gmail.com>
|
|
Optparse has been deprecated in favor of argparse upstream (PEP 389
http://www.python.org/dev/peps/pep-0389/), and since we are using
argparse already in the other modules, it makes sense to replace
optparse and use only one parsing method in all piglit.
V2: Dropped some unrelated code per Ken Graunke
Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
Less code, easier to read and more standard, and free help messages.
V2: Changed args.overwrite to 'store_true' per Ken Graunke
Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
Creates a smaller, simpler file that should be easier to maintain going
forward.
Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
An instance of core.Environment was being created, but never used.
Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
On Python 3.x this has the side-effect of returning a str instead of a bytes.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
Trivial: test expects `-use_fbo` option for testing FBO rasterization,
and not `-fbo`.
|
|
As suggested by Dylan Baker.
|
|
Based on the test cases for get_global_id
Reviewed-by: Tom Stellard <thomas.stellard at amd.com>
|
|
Several tests still had '%' in the test names, which Tom made an illegal
character a ways back.
Reviewed-by: Tom Stellard <thomas.stellard at amd.com>
|
|
If only one result file is specified, just print all the tests
followed by the outcome. For example:
fbo/FBO blit from missing attachment: pass
fbo/FBO blit to missing attachment: fail
fbo/fbo-1d: pass
fbo/fbo-3d: crash
[...]
If multiple result files are specified, we'll print pass/fail/etc
for each file. Example:
fbo/FBO blit from missing attachment: pass pass
fbo/FBO blit to missing attachment: fail pass
[...]
If -s (--summary) is specified, only print a summary of the number of
passes, fails, crashes, etc.
if -d (-diff) is specified with multipe result files, only print the
tests which had different outcomes. Good for spotting regressions.
v2: fix -l option issues
Reviewed-by: José Fonseca <jfonseca@vmware.com>
|
|
When doing a full piglit run it's helpful to have all the OpenGL
driver version/vendor/extension info. The piglit framework tries
to run glxinfo/wglinfo and include the output in the results file,
but sometimes those programs aren't installed.
Reviewed-by: José Fonseca <jfonseca@vmware.com>
Reviewed-by Tom Gall <tom.gall@linaro.org>
|
|
v3: Made more readable, report observed sample positions of failure.
|
|
From the description of glMapBuffer:
"A mapped data store must be unmapped with glUnmapBuffer before its
buffer object is used.
Otherwise an error will be generated by any GL command that
attempts to dereference the buffer object's data store."
|
|
Since we never bail on the first failure in this test, we can return
from the GetInternalformativ without buffer_size_in_elements ever
being touched, due to misc GL error (mesa_base_fbo_format fails),
this then causes us to loop a lot later and print error messages
than make piglit eat all the pies^WRAM.
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Pointed out by Chad Versace.
|
|
In Python 3.x the strerr is more verbose, and thus fails the equals
test.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
It is no longer supported in Python 3.x, but unpacking the tuple parameter
inside the function works just fine on both old and new Python versions.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
The old syntax is no longer supported in Python 3.x.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
The old syntax is no longer supported in Python 3.x.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
These warnings have become fatal errors in Python 3.x.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
Changes:
- SINGLE is removed, because its value was 0
- ALPHA is removed, because it becomes redundant with this change
- RGB asks for an RGB visual
- RGBA asks for an RGBA visual
- if RGB and RGBA are unset, it asks for a visual without RGB(A)
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
v2: fix glut
|
|
Fixes two trivial issues:
- on Windows large integers like 0xff000001 are not `int` objects, but
rather `long` objects, so accept both types.
- and the error message caused exception
TypeError: cannot concatenate 'str' and 'long' objects
|
|
By the looks of it "default" is not required to appear as last statement
in a switch expression, and c rules should be followed (which is probably
a mess to implement thanks to fallthrough).
Seems to fail with mesa glsl compiler (at least with tgsi translation).
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
|
|
They switched the default for imagefileio, so they renamed the option
(while leaving out support for the old option, making our tests fail).
This happened some time between our last ES2 drop, and ES3. Since the
current stuff still contains all the ES2 tests, we don't need support
for the old version.
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
|
|
v2: Fix "written" subtest (which was testing the wrong query).
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
In a loop, access past the end of a uniform array, to check
if stages after loop unrolling can handle the bad access.
Reproduces https://bugs.freedesktop.org/show_bug.cgi?id=59429
Signed-off-by: Frank Henigman <fjhenigman@google.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
GLSL ES 1.00 spec 4.5.3 page 36:
"The fragment language has no default precision qualifier for
floating point types."
Adding default precision for float in the fragment shader
so this sanity testcase doesn't error out.
mediump is choosen since according to 4.5.2 page 34:
"The fragment language requires any uses of lowp and mediump to
compile without error. Support for highp is optional."
Signed-off-by: Tom Gall <tom.gall@linaro.org>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
|
|
Commit 0fac0a6 (Modify tests for error checking on "flat" keyword to
match updated specs) adopted the GLSL 1.50 rules for "flat" varyings
for all desktop GL tests (the rationale was that this change likely
reflects a bug fix rather than a deliberate behavioural difference).
The GLSL 1.50 rules allow a vertex shader output to be a non-flat
integer provided that it isn't consumed by the fragment shader. In
particular, this means that a non-flat integer may be used with
transform feedback.
This test verifies that transform feedback works correctly for all
integral types, even if they are not declared as "flat".
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
And set the pixel unpack alignment to 1 so that we don't fail if
the window width isn't a multiple of four.
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
As it was, many of the generated / expected pixel values were all
zeros. Use better values that actually fit in the given datatype.
For example, we were trying to store "0x23 << (6 - j)" in a GLbyte.
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Before, the 96x96 window got bumped up to 116x96 by Windows and we
saw a "Got spurious window resize in automatic run" message and the
test reported "warn".
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Similar to arb_shader_texture_lod-texgrad, but using cube maps instead.
Given the somewhat undefined behavior of explicit gradients with cube
maps, the main purpose of the test is really to test that those work at
all, as there doesn't seem to be any other test covering this.
That said, drivers which simply drop explicit derivatives on the floor
(like softpipe) pass this perfectly as it simply compares implicit vs.
explicit behavior (which, given the fuzzy specification, might not be
really required to be the same here, though given the chosen values, that
is the major axis derivatives being zero, it might seem like a reasonable
assumption).
I guess something which would also test that the implementation is really
using explicit derivatives instead of implicit ones would also be desirable,
but I'll leave that for now, I couldn't really come up with something.
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
Fixes "invalid syntax" errors when running Piglit.
I could have sworn I tried running Piglit normally, but I must have made
last minute changes. Sorry for the trouble.
|
|
Commit f184de94 (shader_runner: Add lod_bias option to texparameter)
added support for testing the GL_TEXTURE_LOD_BIAS texture parameter to
shader_runner. However, this feature is only available in desktop GL.
This caused compile errors with GLES.
This patch ifdefs the feature out when building the GLES version of
shader_runner.
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
in addition to the counter-clockwise triangles.
Plus minor clean-ups.
Reviewed-by: José Fonseca <jfonseca@vmware.com>
|
|
__func__ is not available on MSVC.
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
|
