Some apitrace-tests updates

[Carl Worth]

Hi José,

I've just pushed a series of apitrace-tests updates to my personal
repository. (I pushed to the master branch and deleted all other stale
branches).

I've included the git log of the new commits below.

One of these commits ("Fix test to correctly use cmake...") is a change
to the cmake build stuff and is essential for me to be able to run all
existing tests.

The others are just test-specific updates to the trim-range test and the
trim_stress test. These should all be non-controversial I think.

-Carl

PS. Again, I'm experimenting with patch-submission approaches. (This
time emailing the commit messages and otherwise just pushing a branch to
my personal repository.) Let me know what you would prefer. and I'll be
more than happy to accommodate.

-- 
carl.d.worth at intel.com

commit 76f19b07ffbb25eb0649cd280d33e2f12a2d4e88
Author: Carl Worth <cworth at cworth.org>
Date:   Mon Jan 28 23:05:26 2013 +1100

    trim_stress: Only look at files matching [0-9]*.png when counting references
    
    If there are any differences from a previous run, there will be
    several additional image files left around, (.thumb.png, etc.). And we
    don't want to count those.

commit a82026739339af67b07181a703a86db1066fcfb8
Author: Carl Worth <cworth at cworth.org>
Date:   Mon Jan 28 22:04:56 2013 +1100

    trim_stress: Also test any traces in the directory trim_stress/local
    
    This is useful for performing testing on traces that are too large to
    be considered for include in git, or for traces that cannot be shared
    due to proprietary contents.

commit 2a1850bdef1124d2cadcdcda84a33f72c8b611a7
Author: Carl Worth <cworth at cworth.org>
Date:   Mon Jan 28 22:04:01 2013 +1100

    trim_stress: Fail test at first frame which doesn't match reference
    
    When stress-testing large traces, it's inefficient to work through the
    entire trace before reporting an error that occurred in one of the
    first frames.
    
    Instead, check each frame one at a time immediately as each rendered
    frame becomes available. Then fail the test at the first mismatched
    frame.

commit 90e11658816b9b9e6498dffee0aa0283d9b9ebba
Author: Carl Worth <cworth at cworth.org>
Date:   Mon Jan 28 21:55:12 2013 +1100

    Fix test to correctly use cmake feature to find python executable
    
    On my system, at least, there was no ${python} variable set, so the
    tests for PIL were incorrectly failing, (such that many tests were not
    being run at all).

commit 01cf8a24459c0436a4f6a40fe88e57bdff417e7d
Author: Carl Worth <cworth at cworth.org>
Date:   Tue Aug 21 15:55:16 2012 -0700

    trim-range: Stress the call-set parser just a tiny bit more.
    
    We specify an equivalent range, but in a slightly more complex way for
    better testing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20130128/1128002a/attachment.pgp>