"OldCtsTestCaseList.mk" did not exist on "2b32e8ecc8946a64fb6ffc91c7a3f7acc482f0f7"
am 1c4cf1f3: am 62190192: am d8d381f7: Merge "Issue 186618:run cts...
Jeff Sharkey authored
am 1c4cf1f3: am 62190192: am d8d381f7: Merge "Issue 186618:run cts com.android.cts.appsecurity.DocumentsTest--testTree--fail5.1_r2 [root cause]in testTree method, the second writeFully(...) task may be executed in the AsyncTask after readFully(...) task, or they may b

* commit '1c4cf1f3':
  Issue 186618:run cts com.android.cts.appsecurity.DocumentsTest--testTree--fail5.1_r2 [root cause]in testTree method, the second writeFully(...) task may be executed in the AsyncTask after readFully(...) task, or they may be executed at the same time. Since the read and write operation is not protected by synchronized. Two tasks running on different thread my access doc.contents at the same time, and may lead to a null pointer crash [changesY] using AsyncTask.SERIAL_EXECUTOR instead of AsyncTask.THREAD_POOL_EXECUTOR
2b32e8ec