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>
This commit is contained in:
Daniel Vetter 2012-03-22 12:27:43 +01:00
parent 16c4f52782
commit 9e531888ed
3 changed files with 3 additions and 6 deletions

View File

@ -191,8 +191,7 @@ int main(int argc, char **argv)
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");
}
printf("Using %d 1MiB buffers\n", count);

View File

@ -137,8 +137,7 @@ int main(int argc, char **argv)
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");
}
printf("Using %d 1MiB buffers\n", count);

View File

@ -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);