diff options
| author | Dylan Baker <dylan@pnwbakers.com> | 2018-01-22 17:22:10 -0800 |
|---|---|---|
| committer | Fabian Bieler <fabianbieler@fastmail.fm> | 2018-02-05 19:44:17 +0100 |
| commit | 14e2ba8a7da047f6394120913ff668680af3871b (patch) | |
| tree | 77f9c87033bf00e86b57b4a22afb9b4d3fb42633 | |
| parent | 997f73ea2f1343c5c7b05c7c91c10f69404a0fc4 (diff) | |
tests/fbo-storage-formats: Make subtest names predictable
Currently the name of the subtest relies on checking the GL state of the
command to know whether the framebuffer is completely or incomplete.
That is a problem for enumerating subtests, we would need to know ahead
of time whether the framebuffer is complete or not.
Instead print the completeness of the test apart from the subtest name,
and name the subtest name just the format name. This also makes the name
the same when the test fails and when in passes.
Signed-off-by: Dylan Baker <dylan.c.baker@intel.com>
Reviewed-by: Fabian Bieler <fabianbieler@fastmail.fm>
| -rw-r--r-- | tests/fbo/fbo-storage-formats.c | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/tests/fbo/fbo-storage-formats.c b/tests/fbo/fbo-storage-formats.c index 91b80e09d..9cf8c675a 100644 --- a/tests/fbo/fbo-storage-formats.c +++ b/tests/fbo/fbo-storage-formats.c @@ -200,11 +200,10 @@ test(void) pass = GL_FALSE; } else { GLenum status = glCheckFramebufferStatus(GL_FRAMEBUFFER); - piglit_report_subtest_result(PIGLIT_PASS, - "%s (%s)", - name, - (status == GL_FRAMEBUFFER_COMPLETE ? - "complete" : "incomplete")); + printf("%s is %s\n", + name, + (status == GL_FRAMEBUFFER_COMPLETE ? "complete" : "incomplete")); + piglit_report_subtest_result(PIGLIT_PASS, "%s", name); } } |