diff options
author | Tobias Thierer <tobiast@google.com> | 2017-02-17 16:52:34 +0000 |
---|---|---|
committer | Tobias Thierer <tobiast@google.com> | 2017-02-17 17:11:58 +0000 |
commit | 5be2d77fc1556b0623f9edf9e2df738871caf49f (patch) | |
tree | d2485404295195090f2ac6d95c3798ded59f765d /annotations/generate_annotated_java_files.py | |
parent | b2af2e6d63267a4ab475fd288e6a93e3a183b59b (diff) |
Delete flaky OldSystemTest.test_gc()
This integration test was asserting that running a GC would free memory.
This test has gone through several iterations but has proven flaky due
to not enough memory being available to allocate, small allocations to
immediately showing up through Runtime.freeMemory(), or other
possibilities such as a separate thread potentially allocating objects
in the background.
Since documented guarantees around System.gc() are very weak, the test
is not worth the hassle. This CL removes it.
To ensure that System.gc() results in a GC in the first place (under
specific conditions that are internally known but not guaranteed in
documentation), PhantomReferenceTest was expanded to test interaction
with System.gc() / System.runFinalization().
Bug: 34964016
Test: PhantomReferenceTest
Change-Id: I14a8b41e82294523f325e0c69ddacb4bf04076b3
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions