trim_stress: Fail test at first frame which doesn't match reference
authorCarl Worth <cworth@cworth.org>
Mon, 28 Jan 2013 11:04:01 +0000 (22:04 +1100)
committerJosé Fonseca <jfonseca@vmware.com>
Wed, 6 Feb 2013 15:47:48 +0000 (15:47 +0000)
commitd9b3a939cfe3e981c2d936ff3c9e788b0e571419
tree10f884a8509e5df922c2eb65988dfe0b386e6500
parent2234d55c7f6c9309d12c3a2a948a1b7f0e94b81a
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.
trim_stress/README.markdown
trim_stress_driver.py