isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-11 22:10:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
189068d465
mutter/cogl/tests/conform/test-conform-main.c

148 lines
4.9 KiB
C
Raw Normal View History

Don't use config.h in clutter and cogl In cogl use cogl-config.h and in clutter use clutter-build-config.h. We can't use clutter-config.h in clutter because its already used and installed. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-05 14:21:51 +00:00
#include "cogl-config.h"
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
#include <cogl/cogl.h>
#include <glib.h>
#include <locale.h>
#include <stdlib.h>
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
#include <string.h>
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
cogl: Add missing function declarations In plenty of places a non-static function was defined but didn't have the corresponding declaration. Fix this by adding them, or alternatively making them static.
2019-01-20 10:41:48 +00:00
#include "test-declarations.h"
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
#include "test-utils.h"
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
/* A bit of sugar for adding new conformance tests */
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
#define ADD_TEST(FUNC, REQUIREMENTS, KNOWN_FAIL_REQUIREMENTS) \
G_STMT_START { \
if (strcmp (#FUNC, argv[1]) == 0) \
{ \
cogl tests: Normally skip tests that are not expected to succeed If a test is not expected to succeed, then running it could be considered to be a waste of resources, particularly if the failure might manifest as an indefinite hang (see cogl!11), or if the test is likely to dump core and trigger "expensive" crash-reporting mechanisms like systemd-coredump, corekeeper, abrt or apport. Skip the tests that are expected to fail. They can still be requested via an environment variable, which can be set after fixing a bug to check which tests are now passing. Originally cogl!15, adapted for mutter's fork of cogl to use gboolean instead of CoglBool. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1272 Signed-off-by: Simon McVittie <smcv@debian.org>
2020-05-27 14:16:25 +00:00
if (test_utils_init (REQUIREMENTS, KNOWN_FAIL_REQUIREMENTS) \
|| g_getenv ("COGL_TEST_TRY_EVERYTHING") != NULL) \
{ \
FUNC (); \
test_utils_fini (); \
exit (0); \
} \
else \
{ \
exit (1); \
} \
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
} \
} G_STMT_END
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
#define UNPORTED_TEST(FUNC)
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
int
main (int argc, char **argv)
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
{
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
int i;
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
if (argc != 2)
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
{
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
g_printerr ("usage %s UNIT_TEST\n", argv[0]);
exit (1);
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
}
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
/* Just for convenience in case people try passing the wrapper
* filenames for the UNIT_TEST argument we normalize '-' characters
* to '_' characters... */
for (i = 0; argv[1][i]; i++)
{
if (argv[1][i] == '-')
argv[1][i] = '_';
}
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
/* This file is run through a sed script during the make step so the
* lines containing the tests need to be formatted on a single line
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
* each.
*/
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_object);
UNPORTED_TEST (test_fixed);
UNPORTED_TEST (test_materials);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_pipeline_user_matrix, 0, 0);
ADD_TEST (test_blend_strings, 0, 0);
conform: Add color attribute based blending test This adds a test to make sure that if the same pipeline is used to draw two primitives, one which doesn't need blending because it has an opaque color associated, and another using a color attribute that requires blending then Cogl should recognize that it needs to enable blending for the second primitive even though the pipeline hasn't changed. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit c15d91f1c6293bebd4494d1e20586121483cddef)
2013-05-22 18:49:05 +00:00
ADD_TEST (test_blend, 0, 0);
cogl test-premult: Don't free texture data until CoglBitmap is freed According to the cogl_bitmap_new_for_data documentation, the data is not copied, so the application must keep the buffer alive for the lifetime of the CoglBitmap. Freeing it too early led to a use-after-free in the cogl unit tests. With that fixed, the test passes, so remove the known failure annotation. This AddressSanitizer trace is from the original cogl, but the bug and fix apply equally to mutter's fork of cogl: ==6223==ERROR: AddressSanitizer: heap-use-after-free on address 0x62100001a500 at pc 0x7f3e2d4e7f4e bp 0x7ffcd9c41f30 sp 0x7ffcd9c416e0 READ of size 4096 at 0x62100001a500 thread T0 #0 0x7f3e2d4e7f4d (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x96f4d) #1 0x7f3e260c7f6b in util_copy_box ../src/gallium/auxiliary/util/u_surface.c:131 #2 0x7f3e268c6c10 in u_default_texture_subdata ../src/gallium/auxiliary/util/u_transfer.c:67 #3 0x7f3e26486459 in st_TexSubImage ../src/mesa/state_tracker/st_cb_texture.c:1480 #4 0x7f3e26487029 in st_TexImage ../src/mesa/state_tracker/st_cb_texture.c:1709 #5 0x7f3e26487029 in st_TexImage ../src/mesa/state_tracker/st_cb_texture.c:1691 #6 0x7f3e2644bdba in teximage ../src/mesa/main/teximage.c:3105 #7 0x7f3e2644bdba in teximage_err ../src/mesa/main/teximage.c:3132 #8 0x7f3e2644d84f in _mesa_TexImage2D ../src/mesa/main/teximage.c:3170 #9 0x7f3e2cd1f7df in _cogl_texture_driver_upload_to_gl driver/gl/gl/cogl-texture-driver-gl.c:347 #10 0x7f3e2ccd441b in allocate_from_bitmap driver/gl/cogl-texture-2d-gl.c:255 #11 0x7f3e2ccd441b in _cogl_texture_2d_gl_allocate driver/gl/cogl-texture-2d-gl.c:462 #12 0x7f3e2ce3a6c0 in cogl_texture_allocate cogl/cogl-texture.c:1398 #13 0x7f3e2ce3e116 in _cogl_texture_pre_paint cogl/cogl-texture.c:359 #14 0x7f3e2cdee177 in _cogl_pipeline_layer_pre_paint cogl/cogl-pipeline-layer.c:864 #15 0x7f3e2cd574af in _cogl_rectangles_validate_layer_cb cogl/cogl-primitives.c:542 #16 0x7f3e2cdd742f in cogl_pipeline_foreach_layer cogl/cogl-pipeline.c:735 #17 0x7f3e2cd5c8b0 in _cogl_framebuffer_draw_multitextured_rectangles cogl/cogl-primitives.c:658 #18 0x7f3e2cd60152 in cogl_rectangle cogl/cogl-primitives.c:858 #19 0x5570a71ed6a0 in check_texture tests/conform/test-premult.c:103 #20 0x5570a71ed946 in test_premult tests/conform/test-premult.c:159 #21 0x5570a71df0d6 in main tests/conform/test-conform-main.c:58 #22 0x7f3e2bcd809a in __libc_start_main ../csu/libc-start.c:308 #23 0x5570a71e0869 in _start (/home/smcv/src/debian/cogl/tests/conform/.libs/test-conformance+0x33869) 0x62100001a500 is located 0 bytes inside of 4096-byte region [0x62100001a500,0x62100001b500) freed by thread T0 here: #0 0x7f3e2d5581d7 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x1071d7) #1 0x5570a71ed58b in make_texture tests/conform/test-premult.c:69 previously allocated by thread T0 here: #0 0x7f3e2d558588 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x107588) #1 0x7f3e2d384500 in g_malloc ../../../glib/gmem.c:99 This was originally cogl!12. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1274 Signed-off-by: Simon McVittie <smcv@debian.org>
2019-08-25 15:44:07 +00:00
ADD_TEST (test_premult, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_readpixels);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_depth_test, 0, 0);
tests: flag backface culling failure without NPOT support This marks that test-backface-culling is currently known to fail without NPOT texture support. This allows us do a 1.13 snapshot release before we find a fix for this.
2013-01-21 15:41:16 +00:00
ADD_TEST (test_backface_culling, 0, TEST_REQUIREMENT_NPOT);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_layer_remove, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_sparse_pipeline, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
texture-2d-slice: Fix the foreach_sub_texture_in_region implementation There were a few problems with the sub texture iterating code of sliced textures which were causing some conformance tests to fail when NPOT textures are disabled: • The spans are stored in un-normalized coordinates and the coordinates passed to the foreach function are normalized. The function was trying to un-normalize them before passing them to the span iterator code but it was using the wrong factor which was causing it to actually doubley normalize them. • The shim function to renormalize the coordinates before passing them to the callback was renormalizing the sub-texture coordinates instead of the virtual coordinates. The sub-texture coordinates are already in the right scale for whatever is the underlying texture so we don't need to touch them. Instead we need to normalize the virtual coordinates because these are coming from the un-normalized coordinates that we passed to the span iterating code. • The normalize factors passed to the span iterating were always 1. The code uses this normalizing factor to round the incoming coordinates to the nearest multiple of a full texture. It divides the coordinates by the factor rather than multiplying so it looks like we should be passing the virtual texture size here. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit c9773566b0ec0a17b34c440090529de8cff9609e)
2012-12-10 15:47:45 +00:00
ADD_TEST (test_npot_texture, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_multitexture);
UNPORTED_TEST (test_texture_mipmaps);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_sub_texture, 0, 0);
Fix handling of binding errors when uploading a full texture Both the texture drivers weren't handling errors correctly when a CoglPixelBuffer was used to set the contents of an entire texture. This was causing it to hit an assertion failure in the pixel buffer tests. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 888733d3c3b24080d2f136cedb3876a41312e4cf)
2012-11-27 20:07:47 +00:00
ADD_TEST (test_pixel_buffer_map, 0, 0);
ADD_TEST (test_pixel_buffer_set_data, 0, 0);
Simplify test-pixel-buffer test-pixel-buffer previously had two tests, one to check filling the pixel buffer by mapping it and another to fill it by just setting the data. These tests were set up in a kind of confusing way where it would try to paint both steps and then validate them together using colors looked up from a table. This patch separates out the two tests and gets rid of the tables which hopefully makes them a bit easier to follow. The contents of the bitmap are now set to an image with has a different colour for each of its four quadrants instead of just a single colour in the hope that this will be a bit more of an extensive test. The old code had a third test that was commented out. This test has been removed. The textures are now created using cogl_texture_2d_new_* which means they won't be in the atlas. This exposes a bug where setting the entire contents of the texture won't handle errors properly and it will hit an assertion. The previous code using the atlas would end up only setting a sub-region of the larger atlas texture so the bug wouldn't be hit. To make sure we still test this code path there is now a third test which explicitly sets a sub-region of the texture using the bitmap. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 8beb3a4cc20f539a50645166485b95e8e5b25779)
2012-11-27 20:01:05 +00:00
ADD_TEST (test_pixel_buffer_sub_region, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_texture_rectangle);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_wrap_modes, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_texture_pixmap_x11);
texture-2d-slice: Fix the foreach_sub_texture_in_region implementation There were a few problems with the sub texture iterating code of sliced textures which were causing some conformance tests to fail when NPOT textures are disabled: • The spans are stored in un-normalized coordinates and the coordinates passed to the foreach function are normalized. The function was trying to un-normalize them before passing them to the span iterator code but it was using the wrong factor which was causing it to actually doubley normalize them. • The shim function to renormalize the coordinates before passing them to the callback was renormalizing the sub-texture coordinates instead of the virtual coordinates. The sub-texture coordinates are already in the right scale for whatever is the underlying texture so we don't need to touch them. Instead we need to normalize the virtual coordinates because these are coming from the un-normalized coordinates that we passed to the span iterating code. • The normalize factors passed to the span iterating were always 1. The code uses this normalizing factor to round the incoming coordinates to the nearest multiple of a full texture. It divides the coordinates by the factor rather than multiplying so it looks like we should be passing the virtual texture size here. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit c9773566b0ec0a17b34c440090529de8cff9609e)
2012-12-10 15:47:45 +00:00
ADD_TEST (test_texture_get_set_data, 0, 0);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_atlas_migration, 0, 0);
conform: Mark XFAIL tests Bisection would be useful.
2015-07-23 11:59:55 +00:00
ADD_TEST (test_read_texture_formats, 0, TEST_KNOWN_FAILURE);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_write_texture_formats, 0, 0);
Add a conformance test using alpha textures This adds a conformance test with an alpha-component texture. The texture is rendered using a pipeline with the same layer combine mode as cogl-pango. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 05190519bad4519e66cbdb5326943c832d15a841)
2012-11-19 17:28:53 +00:00
ADD_TEST (test_alpha_textures, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_vertex_buffer_contiguous);
UNPORTED_TEST (test_vertex_buffer_interleved);
UNPORTED_TEST (test_vertex_buffer_mutability);
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_primitive, 0, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_just_vertex_shader, TEST_REQUIREMENT_GLSL, 0);
ADD_TEST (test_pipeline_uniforms, TEST_REQUIREMENT_GLSL, 0);
ADD_TEST (test_snippets, TEST_REQUIREMENT_GLSL, 0);
ADD_TEST (test_custom_attributes, TEST_REQUIREMENT_GLSL, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_offscreen, 0, 0);
cogl/journal: Don't sometimes hold a ref on the framebuffer d42f1873fcd0876244eb8468d72ce35459ba94ca introduced a semi circular reference between the CoglFramebuffer, and CoglJournal, where CoglJournal would keep a reference on the CoglFramebuffer when there were any entries in the journal log. To avoid risking leaking these objects indefinitely, when freeing objects without doing anything that triggered a flush, CoglFramebuffer had a "filter" on cogl_object_unref() calls, which knew about under what conditions CoglJournal had a reference to it. When it could detect that there were only the journal itself holding such a reference, it'd flush the journal, effectively releasing the reference the journal held, thus freeing itself, as well as the journal. When CoglFramebuffer was ported to be implemented using GObject instead of CoglObject, this "filter" was missed, causing not only awkward but infrequent leaks, but also situations where we'd flush journals when only the journal itself held the last reference to the framebuffer, meaning the journal would free the framebuffer, thus itself, in the middle of flushing, causing memory corruption and crashes. A way to detect this, by asserting on CoglObject reference count during flush, is by adding the `g_assert()` as described below, which will assert instead cause memory corruption. void _cogl_journal_flush (CoglJournal *journal { ... _cogl_journal_discard (journal); + g_assert (journal->_parent.ref_count > 0); ... } Fix this by making CoglFramebuffer the owner of the journal, which it already was, and remove any circle referencing that was there before, as it is not needed given that the CoglFramebuffer pointer is guaranteed to be valid for the lifetime of CoglJournal as the framebuffer is the owner of the journal. However, to not miss flushing before tearing down, which is important as this flushes painting calls to the driver that is important for e.g. using the result of those journal entries, flush the journal the first time cogl_framebuffer_dispose() is called, before doing anything else. This also adds a test case. Without having broken the circular reference, the test would fail on g_assert_null (offscreen), as it would have been "leaked" at this point, but the actual memory corruption would be a result of the `cogl_texture_get_data()` call, which flushes the framebuffer, and causes the 'mid-flush' destruction of the journal described above. Note that the texture keeps track of dependent framebuffers, but it does not hold any references to them. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1474 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1735>
2021-02-18 14:46:28 +00:00
ADD_TEST (test_journal_unref_flush, 0, 0);
tests: Mark test_framebuffer_get_bits as only working on GL It looks like it's not meant to be valid to create a framebuffer with an alpha-only texture as a render target on GLES. Since the following Mesa commit, this requirement is now enforced so that the test_framebuffer_get_bits test fails: http://cgit.freedesktop.org/mesa/mesa/commit/?id=cf300eaa Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit cfb0859cab843b000f4baa3ca155a245730edcfa)
2013-01-21 18:39:55 +00:00
ADD_TEST (test_framebuffer_get_bits,
TEST_REQUIREMENT_OFFSCREEN | TEST_REQUIREMENT_GL,
0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_point_size, 0, 0);
Add support for per-vertex point sizes This adds a new function to enable per-vertex point size on a pipeline. This can be set with cogl_pipeline_set_per_vertex_point_size(). Once enabled the point size can be set either by drawing with an attribute named 'cogl_point_size_in' or by writing to the 'cogl_point_size_out' builtin from a snippet. There is a feature flag which must be checked for before using per-vertex point sizes. This will only be set on GL >= 2.0 or on GLES 2.0. GL will only let you set a per-vertex point size from GLSL by writing to gl_PointSize. This is only available in GL2 and not in the older GLSL extensions. The per-vertex point size has its own pipeline state flag so that it can be part of the state that affects vertex shader generation. Having to enable the per vertex point size with a separate function is a bit awkward. Ideally it would work like the color attribute where you can just set it for every vertex in your primitive with cogl_pipeline_set_color or set it per-vertex by just using the attribute. This is harder to get working with the point size because we need to generate a different vertex shader depending on what attributes are bound. I think if we wanted to make this work transparently we would still want to internally have a pipeline property describing whether the shader was generated with per-vertex support so that it would work with the shader cache correctly. Potentially we could make the per-vertex property internal and automatically make a weak pipeline whenever the attribute is bound. However we would then also need to automatically detect when an application is writing to cogl_point_size_out from a snippet. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 8495d9c1c15ce389885a9356d965eabd97758115) Conflicts: cogl/cogl-context.c cogl/cogl-pipeline-private.h cogl/cogl-pipeline.c cogl/cogl-private.h cogl/driver/gl/cogl-pipeline-progend-fixed.c cogl/driver/gl/gl/cogl-pipeline-progend-fixed-arbfp.c
2012-11-08 16:56:02 +00:00
ADD_TEST (test_point_size_attribute,
TEST_REQUIREMENT_PER_VERTEX_POINT_SIZE, 0);
ADD_TEST (test_point_size_attribute_snippet,
TEST_REQUIREMENT_PER_VERTEX_POINT_SIZE |
TEST_REQUIREMENT_GLSL, 0);
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
ADD_TEST (test_point_sprite,
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
TEST_REQUIREMENT_POINT_SPRITE,
0);
Split test-point-sprite into two, one without checking orientation There is currently a known bug where when rendering offscreen point sprites will be rendered upside-down. For that reason test-point-sprite is marked as a known failure because it checks the orientation of the point sprites and the conformance test suite is rendered to offscreen buffers by default. However this doesn't help to catch more general failures that stop the point sprites being rendered at all. To fix this the test-point-sprite test has been split into two tests, one which verifies the orientation and one which does not. The two tests are in the same source file and internally share the same static function but pass a flag to specify whether to check the orientation. If the orientation should be ignored then it will create a 2x1 texture instead of a 2x2 texture so that it will appear the same regardless of whether it is upside-down. The checks for the colors have been altered accordingly. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 51b7fdbe17f300cf2edf42c2ca740ad748c9fd78)
2012-07-02 13:50:54 +00:00
ADD_TEST (test_point_sprite_orientation,
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
TEST_REQUIREMENT_POINT_SPRITE,
TEST_KNOWN_FAILURE);
Add a conformance test for using cogl_point_coord in a shader This adds a modification to the test-point-sprite test which uses a shader snippet which directly references cogl_point_coord instead of relying on cogl_pipeline_set_layer_point_sprite_coords_enabled to replace the texture coordinates with the point coords. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 5ea57b14f5ec7d52ae378f4ca64574ef56342f56)
2013-08-29 13:14:35 +00:00
ADD_TEST (test_point_sprite_glsl,
TEST_REQUIREMENT_POINT_SPRITE |
TEST_REQUIREMENT_GLSL,
0);
Add a conformance test for point sizes This tries rendering some points at various sizes and checks that they are the expected size and make a rectangle shape. This is currently failing when the GLSL vertend is used because it flushes the point size in the wrong place. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-03-06 23:14:27 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_alpha_test, 0, 0);
Add a simple conformance test for alpha testing This adds a simple test which sets an alpha test on a pipeline and then renders a texture. It then verifies that the transparent parts of the texture aren't drawn. This is currently failing with the GL3 driver because GL3 requires the alpha test to be implemented in GLSL but the generated alpha test uniform is only updated for the GLES2 driver. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 4ec04507bfaf2d61707dccfb59ac7326962ee741)
2012-10-01 13:46:24 +00:00
tests: Differentiate between known failures and missing requirements Previously when make test is run it would say ‘fail’ in lower case letters for both tests that are known bugs we need to fix and for drivers that can't run the test. This makes it too easy to lose track of bugs. To fix this, the ADD_TEST macro has now been changed to take two sets of flags instead of just one. The first specifies the requirements for the test to run at all. The second specifies the set of flags required to run without any known failures. The table in the test report now says ‘n/a’ instead of ‘fail’ for tests that don't match the feature requirements. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 723f8d4402e7b2ef3a71f51bb29b10d1c0ec8d81)
2012-11-09 16:47:01 +00:00
ADD_TEST (test_map_buffer_range, TEST_REQUIREMENT_MAP_WRITE, 0);
Add a test case for cogl_buffer_map_range This adds a small test case which maps a sub region of a small attribute buffer and replaces the texture coordinates of one of the vertices. The vertices are then drawn and the correct colours are checked. There is now a new test requirement for the COGL_FEATURE_ID_MAP_BUFFER_FOR_WRITE feature which this test requires. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 22183265b021dd038338b4398056c0a1eae77edb)
2012-10-17 20:40:26 +00:00
journal: Dirty the modelview matrix state when flushing The journal manually flushes its own modelview matrix state so it needs to mark the state as dirty so that if a primitive is drawn with the same matrix state as the last primitive it will correctly reflush it. https://bugzilla.gnome.org/show_bug.cgi?id=693612 Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit c7290c994c742456ff0977cb394c289afb377049)
2013-02-18 18:21:39 +00:00
ADD_TEST (test_primitive_and_journal, 0, 0);
Add a test to check interleaving primitives and the journal This adds a conformance test which draws a rectangle using the journal in-between two rectangles drawn with primitives without changing any other state. Currently this is failing because the modelview matrix state is not correctly flushed. The journal also flushes in own clip state so the test additionally puts everything in a clip and verifies that that worked. This is not currently broken but we might as well test it. https://bugzilla.gnome.org/show_bug.cgi?id=693612 Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit b703f9a1a98894a12021cbdd632e1d59214e612f)
2013-02-18 18:13:01 +00:00
Prune redundant pipeline ancestry after adding a layer difference Adding a layer difference may mean the pipeline overrides all of the layers of its parent which might make the parent redundant so we should try to prune the hierarchy. This is particularly important for CoglGst because whenever a new frame is ready it tries to make a copy of the pipeline it last used and then replace all of the textures in the layers. Without this patch the new pipeline would keep the parent pipeline alive which means also keeping the old textures alive so all of the frames of the video would effectively be leaked. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 576c7b55aa835448c977f1d79d128dffd40e7cd8)
2013-03-09 20:00:53 +00:00
ADD_TEST (test_copy_replace_texture, 0, 0);
Add test to verify replacing a layer doesn't leak the pipeline parent The current recommendation for pipelines is that once they have been used for painting then they should be considered immutable. If you want to modify a pipeline you should instead make a copy and unref the original pipeline. Internally we try to check whether the modified copy replaces all of the properties of the parent and prune a redundant ancestor hierarchy. Pruning the hierarchy is particularly important if the pipelines contain textures because otherwise the textures may be leaked when the parent pipeline keeps a reference to it. This test verifies that usage pattern by creating a chain of pipeline copies each with their own replacement texture. Some user data is then set on the textures with a callback so that we can verify that once the original pipelines are destroyed then the textures are also destroyed. The test is currently failing because Cogl doesn't correctly prune ancestory for layer state authority. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 3fbec92acb90008492eb125025f92b42d6e07930)
2013-03-09 19:43:46 +00:00
pipeline-cache: Use a special trimmed down pipeline for the key When a pipeline is added to the cache, a normal copy would previously be made to use as the key in the hash table. This copy keeps a reference to the real pipeline which means all of the resources it contains are retained forever, even if they aren't necessary to generate the hash. This patch changes it to create a trimmed down copy that only has the state necessary to generate the hash. A new function called _cogl_pipeline_deep_copy is added which makes a new pipeline that is directly a child of the root pipeline. It then copies over the pertinent state from the original pipeline. The pipeline state is copied using the existing _cogl_pipeline_copy_differences function. There was no equivalent function for the layer state so I have added one. That way the pipeline key doesn't have the texture data state and it doesn't hold a reference to the original pipeline so it should be much cheaper to keep around. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit e27e01c1215e7e7c7c0183ded11dd769bb112c5c)
2013-03-26 11:17:55 +00:00
ADD_TEST (test_pipeline_cache_unrefs_texture, 0, 0);
conform: check we invalidate ancestor cached state In the cases where we cache vertex state with an ancestor pipeline (whose vertex processing state is equivalent) we need to invalidate that state if that ancestor is later modified. This conformance test checks this case but currently fails because we only notify the progend directly associated with the pipeline being changed. In this case the pipeline can be using a different progend to the ancestor which it is caching state with so when the ancestor is changed it needs to notify all the progends that they may need to clear their private state. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit e112af5f770d6c46688fdcb5ba38b75ca0778891)
2013-09-26 11:02:21 +00:00
ADD_TEST (test_pipeline_shader_state, TEST_REQUIREMENT_GLSL, 0);
Conformance test to check whether the pipeline cache holds textures Currently when a unique pipeline is created and added to the pipeline cache that pipeline will live forever which includes keeping a reference to any large resources that the pipeline has such as textures. These textures don't actually need to be kept for the pipeline to be used as a key in the hash table so ideally we wouldn't do this. This test case tries rendering with a pipeline that has textures and then checks whether the textures are successfully destroyed after the pipeline is unreffed. The test is currently marked as a known failure because the pipeline cache will prevent them from being destroyed. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 0056f805dadd46b966d57f66b02890b8c29971ac)
2013-03-26 12:08:12 +00:00
Adds cogl_framebuffer_draw_[*_]rectangle functions This adds experimental 2.0 api replacements for the cogl_rectangle[_*] functions that don't depend on having a current pipeline set on the context via cogl_{set,push}_source() or having a current framebuffer set on the context via cogl_push_framebuffer(). The aim for 2.0 is to switch away from having a statefull context that affects drawing to having framebuffer drawing apis that are explicitly passed a framebuffer and pipeline. To test this change several of the conformance tests were updated to use this api instead of cogl_rectangle and cogl_rectangle_with_texture_coords. Since it's quite laborious going through all of the conformance tests the opportunity was taken to make other clean ups in the conformance tests to replace other uses of 1.x api with experimental 2.0 api so long as that didn't affect what was being tested.
2012-03-16 19:54:13 +00:00
UNPORTED_TEST (test_viewport);
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
tests: Add a test for the RGB <-> HSL functions Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 32d67c2bf40641b2d1d30fa2d994013c3e6ce5bc)
2013-05-14 20:26:30 +00:00
ADD_TEST (test_color_hsl, 0, 0);
Add a basic conformance test for eulers and quaternions This adds some preliminary testing for eulers and quaternions. It mostly just tests the cogl_matrix_init_from_{quaternion,euler} functions as well as applying a euler or quaternion transformation to a framebuffer's modelview matrix. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit a32eb76e16d7d76af2fe8a6ba9151d8826b58864)
2012-05-17 21:30:37 +00:00
Add fence API cogl_framebuffer_add_fence creates a synchronisation fence, which will invoke a user-specified callback when the GPU has finished executing all commands provided to it up to that point in time. Support is currently provided for GL 3.x's GL_ARB_sync extension, and EGL's EGL_KHR_fence_sync (when used with OpenGL ES). Signed-off-by: Daniel Stone <daniel@fooishbar.org> Reviewed-by: Neil Roberts <neil@linux.intel.com> Reviewed-by: Robert Bragg <robert@linux.intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=691752 (cherry picked from commit e6d37470da9294adc1554c0a8c91aa2af560ed9f)
2013-01-11 01:13:34 +00:00
ADD_TEST (test_fence, TEST_REQUIREMENT_FENCE, 0);
Fix freeing an atlas texture that hasn't been allocated The free function for atlas textures was previously always assuming that there will be a valid sub_texture pointer but this might not be the case if the texture was never successfully allocated. This was causing Cogl to crash if the application tries to make a texture that can not fit in the atlas using the automagic texture API. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit a7a8b7aefc8cb03fe8b716bee06b3449a7dba85f)
2013-06-11 14:57:38 +00:00
ADD_TEST (test_texture_no_allocate, 0, 0);
Add test that Cogl doesn't crash when freeing unallocated texture It looks like Cogl doesn't currently clean up an unallocated atlas texture properly so if it fails to allocate it. It will then crash when it is freed. This adds a conformance test to verify that all of the various texture types can be freed without allocating them. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit bfada22d9a7f60baad5ae5615e45f10327e23e36)
2013-06-11 14:57:37 +00:00
Add support for RG textures This adds COGL_PIXEL_FORMAT_RG_88 and COGL_TEXTURE_COMPONENTS_RG in order to support two-component textures. The RG components for a texture is only supported if COGL_FEATURE_ID_TEXTURE_RG is advertised. This is only available on GL 3, GL 2 with the GL_ARB_texture_rg extension or GLES with the GL_EXT_texture_rg extension. The RG pixel format is always supported for images because Cogl can easily do the conversion if an application uses this format to upload to a texture with a different format. If an application tries to create an RG texture when the feature isn't supported then it will raise an error when the texture is allocated. https://bugzilla.gnome.org/show_bug.cgi?id=712830 Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit 568677ab3bcb62ababad1623be0d6b9b117d0a26) Conflicts: cogl/cogl-bitmap-packing.h cogl/cogl-types.h cogl/driver/gl/gl/cogl-driver-gl.c tests/conform/test-read-texture-formats.c tests/conform/test-write-texture-formats.c
2014-01-14 15:52:45 +00:00
ADD_TEST (test_texture_rg, TEST_REQUIREMENT_TEXTURE_RG, 0);
tests: Improve thoroughness and reporting of make test This patch reworks our conformance testing framework because it seems that glib's gtesting framework isn't really well suited to our use case. For example we weren't able to test windows builds given the way we were using it and also for each test we'd like to repeat the test with several different environments so we can test important driver and feature combinations. This patch instead switches away to a simplified but custom approach for running our unit tests. We hope that having a more bespoke setup will enable us to easily extend it to focus on the details important to us. Notable changes with this new approach are: We can now run 'make test' for our mingw windows builds. We've got rid of all the test-*report* make rules and we're just left with 'make test' 'make test' now runs each test several times with different driver and feature combinations checking the result for each run. 'make test' will then output a concise table of all of the results. The combinations tested are: - OpenGL Fixed Function - OpenGL ARBfp - OpenGL GLSL - OpenGL No NPOT texture support - OpenGLES 2.0 - OpenGLES 2.0 No NPOT texture support Reviewed-by: Neil Roberts <neil@linux.intel.com>
2012-02-23 12:30:51 +00:00
g_printerr ("Unknown test name \"%s\"\n", argv[1]);
return 1;
Starts porting Cogl conformance tests from Clutter This makes a start on porting the Cogl conformance tests that currently still live in the Clutter repository to be standalone Cogl tests that no longer require a ClutterStage. The main thing is that this commit brings in is the basic testing infrastructure we need, so now we can port more and more tests incrementally. Since the test suite wants a way to synchronize X requests/replies and we can't simply call XSynchronize in the test-utils code before we know if we are really running on X this adds a check for an environment variable named "COGL_X11_SYNC" in cogl-xlib-renderer.c and if it's set it forces XSynchronize (dpy, TRUE) to be called. By default the conformance tests are run off screen. This makes the tests run much faster and they also don't interfere with other work you may want to do by constantly stealing focus. CoglOnscreen framebuffers obviously don't get tested this way so it's important that the tests also get run on screen every once in a while, especially if changes are being made to CoglFramebuffer related code. On screen testing can be enabled by setting COGL_TEST_ONSCREEN=1 in your environment.
2011-05-05 22:34:38 +00:00
}
Reference in New Issue Copy Permalink