If gtests are started with a small heap, this gtest fails:

```
thomas@mainframe:/shared/projects/openjdk/jdk-jdk/output-fastdebug$ ./hotspot/variant-server/libjvm/gtest/gtestLauncher -Xmx128m -jdk:./images/jdk --gtest_filter=CollectorPolicy.young_scaled_initial_ergo_vm
Note: Google Test filter = CollectorPolicy.young_scaled_initial_ergo_vm
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from CollectorPolicy
[ RUN ] CollectorPolicy.young_scaled_initial_ergo_vm
[0,118s][warning][gc,ergo] Inconsistency between generation sizes and heap size, resizing the generations to fit the heap.
/shared/projects/openjdk/jdk-jdk/source/test/hotspot/gtest/gc/shared/test_collectorPolicy.cpp:124: Failure
Expected equality of these values:
  expected
    Which is: 34930688
  NewSize
    Which is: 54525952
/shared/projects/openjdk/jdk-jdk/source/test/hotspot/gtest/gc/shared/test_collectorPolicy.cpp:80: Failure
Expected: checker->execute() doesn't generate new fatal failures in the current thread.
  Actual: it does.
[ FAILED ] CollectorPolicy.young_scaled_initial_ergo_vm (0 ms)
[----------] 1 test from CollectorPolicy (119 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (119 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] CollectorPolicy.young_scaled_initial_ergo_vm
```

It would be nice if the test would just be ignored if it cannot be run under these circumstances.