| d3b5f049d29413ce7dc5cc051e860e47fc515239 |
|
06-May-2014 |
Andreas Gampe <agampe@google.com> |
Revert "Libcore: Remove <> in CloseGuardMonitor test class"
Dalvik-dev has switched to Java 7 now, so diamonds are allowed now.
This reverts commit 307e642f661f73cf22fa689ee40181481768c400.
Change-Id: Ia1893bfea09aa2de65fed997bc3e5e3805d92387
|
| 307e642f661f73cf22fa689ee40181481768c400 |
|
03-May-2014 |
Andreas Gampe <agampe@google.com> |
Libcore: Remove <> in CloseGuardMonitor test class
Regrettably we're stuck with Java 1.6 in some branches, which will
not accept the diamond operator.
Change-Id: Iab1bd30bdcd70e312c2809a42d2339e0503a3250
|
| a6f350c645dbb66d68cc2b03afb8f2eeaa88fbba |
|
28-Feb-2014 |
Paul Duffin <paulduffin@google.com> |
Improve detection of CloseGuard protected resource leakage
* Add CloseGuardMonitor to intercept and collate CloseGuard reports and if
necessary throw an exception listing the resource leaks.
* Add ResourceLeakageDetector to abstract away the CloseGuardMonitor which will
not work on RI.
* Add AbstractResourceLeakageDetectorTestCase as a base class for tests
that need to detect resource leaks, in future this could be handled by
modifications to Cts and Vogar test runners.
* Remove CloseGuardTester and its sole usage in ProcessBuilderTest.
* Remove CloseGuardGuard from within URLConnectionTest
* Change ZipFileTest, ProcessBuilderTest, URLConnectionTest to use new
mechanism, fix issues that are identified and do some cleanup/remove
duplicated code.
Bug: https://code.google.com/p/android/issues/detail?id=66383
Change-Id: Id026dbb6bc66091a15f07329e6371cd0d1f32cf5
|