| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
In order to run under memfault, the framework is first extended to handle
running concurrent tests - i.e. multi-threading. (Not that this is a
requirement for memfault, instead it shares a common goal of storing
per-test data). To that end all the global data is moved into a per-test
context and the targets are adjusted to avoid overlap on shared, global
resources (such as output files and frame buffers). In order to preserve
the simplicity of the standard draw routines, the context is not passed
explicitly as a parameter to the routines, but is instead attached to the
cairo_t via the user_data.
For the masochist, to enable the tests to be run across multiple threads
simply set the environment variable CAIRO_TEST_NUM_THREADS to the desired
number.
In the long run, we can hope the need for memfault (runtime testing of
error paths) will be mitigated by static analysis. A promising candidate
for this task would appear to be http://hal.cs.berkeley.edu/cil/.
|
|
Ensure that the failure path also calls cairo_test_fini().
|
|
Without this, any tests that were using cairo_test_init rather than
cairo_test would end up leaking a FILE* for the log file. So this
keeps valgrind much more happy with the test suite.
|
|
As suggested by Behdad Esfahbod, we can not use the cairo_test() framework
when it is getting in the way. The test itself doesn't depend on any
particular backend.
http://lists.freedesktop.org/archives/cairo/2006-December/008809.html
|
|
The blurb for the fill-degenerate-sort-order, fill-missed-stop and
in-fill-empty-trapezoid tests changed to this one:
http://www.opensource.org/licenses/mit-license.php
c.f. http://lists.freedesktop.org/archives/cairo/2006-December/008806.html
|
|
trapezoids.
cairo_in_fill() may report true if a query point lands on an edge of an
empty trapezoid.
|
