| 4c8cbbd148b3478a597ac6bc95c17115fdd865a8 |
|
05-Oct-2014 |
Mathieu Chartier <mathieuc@google.com> |
Fix RuntimeTest.freeMemory
Previously the test asserted that freeMemory > 0, but it can be 0 if
the heap is full. Now we check that it is non negative.
Bug: 17448025
Change-Id: If8198e8f76543caea665caf77a37ac33dda38517
|
| d3b74a8affe39699df64469c955d0e925e1566fb |
|
03-Oct-2014 |
Narayan Kamath <narayan@google.com> |
Delete RuntimeTest.test_gc.
This test is flaky (see below), and it's not testing anything useful.
- the value returned by totalMemory() can increase if the heap expands
- similar issue with freeMemory(), which is only measured against the
current heap size
- the test assumes that there aren't any other threads in the process
allocating objects.
bug: 17663212
Change-Id: I43fb4c2d4412033cd01bb3a533a34e47905ff229
|
| e5f353301f2882776155fd1673c61a289d5eeaa1 |
|
12-Sep-2014 |
Mathieu Chartier <mathieuc@google.com> |
Delete RuntimeTest freeMemory test
Test was flaky due to bad assumptions, Runtime.freeMemory is already
tested by test_memory, test_gc.
Bug: 17448025
(cherry picked from commit e2233ca92da0339686da18db4a1e27b9a4c76b91)
Change-Id: I88d09ee5cd1c4e34c97814afd2cbadc870222738
|
| e2233ca92da0339686da18db4a1e27b9a4c76b91 |
|
12-Sep-2014 |
Mathieu Chartier <mathieuc@google.com> |
Delete RuntimeTest freeMemory test
Test was flaky due to bad assumptions, Runtime.freeMemory is already
tested by test_memory, test_gc.
Bug: 17448025
Change-Id: I62a8e0240a8a8a95dcb9a8a2423bb57dfcff3c1a
|
| f54d81e0e2d97798b928ba32f5edab5519622f28 |
|
10-Jun-2014 |
Neil Fuller <nfuller@google.com> |
Tests for Runtime.*Memory()
The docs describe a condition we do not test for.
The freeMemory / totalMemory tests have been consolidated
into a single test and joined by an additional assertion for
maxMemory().
The test for freeMemory from OldRuntimeTest has been tidied
up and moved to RuntimeTest.
Bug: 15507122
Change-Id: I4343215fb7f6b441613e25d3844d67812f5b5e94
|
| ab762bb740405d0fefcccf4a0899a234f995be13 |
|
15-Nov-2013 |
Narayan Kamath <narayan@google.com> |
Move tests from tests/api to harmony-tests. (Take 2)
This reverts commit d5e281743e55e1daa297fd8043b2d9b6e8e1bed2.
The makefile issue that caused the original build break
has been resolved.
|
| d5e281743e55e1daa297fd8043b2d9b6e8e1bed2 |
|
15-Nov-2013 |
Narayan Kamath <narayan@google.com> |
Revert "Move tests from tests/api to harmony-tests."
This reverts commit 81bf28ad31131815d0a36a43a0eca3c29aefdfcd.
Breaks build
Change-Id: I3f1562921ffe8fdbec36971dd65db398c27c92db
|
| 81bf28ad31131815d0a36a43a0eca3c29aefdfcd |
|
15-Nov-2013 |
Narayan Kamath <narayan@google.com> |
Move tests from tests/api to harmony-tests.
The vast majority of cleaned up harmony tests
are now in harmony-tests/src/test/org/apache/harmony/tests/
Change-Id: I56c2e484ff434b5618cf6751d602ae9f0db96b30
|