| 112d339673c379b71a989bd33b73648aafe58ce1 |
|
25-Mar-2011 |
Jesse Wilson <jessewilson@google.com> |
Fix MemoryFile's output stream to advance.
Previously it was not useful.
Change-Id: I0bcc06b65bab33a38a0b0148c020509076a51b1c
http://code.google.com/p/android/issues/detail?id=11415
/frameworks/base/core/tests/coretests/src/android/os/MemoryFileTest.java
|
| a006b47298539d89dc7a06b54c070cb3e986352a |
|
14-Apr-2010 |
Bjorn Bringert <bringert@android.com> |
New API and implementation of DB and memory-backed FDs
This depends on a kernel patch that implements read(2)
in the ashmem driver.
Bug http://b/issue?id=2595601
Change-Id: Ie3b10aa471aada21812b35e63954c1b2f0a7b042
/frameworks/base/core/tests/coretests/src/android/os/MemoryFileTest.java
|
| e1e37c632c2deb68f13c92f402c62daaca21afb1 |
|
16-Mar-2010 |
Brett Chabot <brettchabot@android.com> |
Remove flaky test MemoryFileTest:testPurge from large suite.
Bug 2203775
Change-Id: I4709c0910384f1f2313dc67bfe6e163beaa990e6
/frameworks/base/core/tests/coretests/src/android/os/MemoryFileTest.java
|
| 1017a134c19b3d296c7c05cf640db4b08816d090 |
|
17-Feb-2010 |
Bjorn Bringert <bringert@android.com> |
Clean up after failed MemoryFileTest.testPurge()
MemoryFileTest.testPurge() can fail if the process runs
out of file descriptors before the kernel starts purging ashmem areas.
Before, there was no finally block to close the open ashmem
file descriptions, which caused random other tests to fail.
I also changed the size of the memory areas to 10MB, which
should cause it to run out of memory before it runs out of file
descriptors. It now fails with this instead:
java.io.IOException
at android.os.MemoryFile.native_pin(Native Method)
at android.os.MemoryFile.allowPurging(MemoryFile.java:189)
at android.os.MemoryFileTest.testPurge(MemoryFileTest.java:53)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:430)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)
I'm not sure why, but it could be that the kernel is purging the just
allocated area instead of an old one. That seems like bug.
See http://b/issue?id=2203775
Change-Id: Ia7930a714378474dd4c2c6709da40c08e715ab6f
/frameworks/base/core/tests/coretests/src/android/os/MemoryFileTest.java
|
| 1a44d5dcabc18cd5ef111f732ccff91683a1a093 |
|
13-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test cleanup: moving test files from AndroidTests closer to their sources.
Most of these are file moves; a couple notable exceptions are the changes due to the move, and fixing up test code:
- database/DatabaseCursorTest.java
- database/DatabaseStatementTest.java
- net/UriTest.java
/frameworks/base/core/tests/coretests/src/android/os/MemoryFileTest.java
|