diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-03-22 12:27:43 +0100 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-03-22 12:27:43 +0100 |
commit | 9e531888ed0c3e34303a67e324ea4ab29057c62b (patch) | |
tree | b85616d7bf2fe37f3ae62fa6a22addea427e06fe /tests/gem_tiled_fence_blits.c | |
parent | 16c4f52782e0df88f818dadd4586ea99ccf992d5 (diff) |
tests: don't just bail out when there's not enough RAM
... but actually run the test with reduced memory requirements,
as the messages claims. Additional print it to stdout, stderr
seems to imply FAIL in our QA's testing rig.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tests/gem_tiled_fence_blits.c')
-rw-r--r-- | tests/gem_tiled_fence_blits.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/tests/gem_tiled_fence_blits.c b/tests/gem_tiled_fence_blits.c index 9cc8e046..dc654793 100644 --- a/tests/gem_tiled_fence_blits.c +++ b/tests/gem_tiled_fence_blits.c @@ -112,8 +112,7 @@ int main(int argc, char **argv) count = 3 * gem_aperture_size(fd) / (1024*1024) / 2; if (count > intel_get_total_ram_mb() * 9 / 10) { count = intel_get_total_ram_mb() * 9 / 10; - fprintf(stderr, "not enough RAM to run test, reducing buffer count\n"); - return 77; + printf("not enough RAM to run test, reducing buffer count\n"); } count |= 1; printf("Using %d 1MiB buffers\n", count); |