685b1b82264a18a27a3c5b0a3e73061e3bbb2e24 |
|
10-Jun-2017 |
Neil Fuller <nfuller@google.com> |
Suppress tests that allocate significant heap Suppress tests that allocate significant heap. On Fugu devices this causes later tests that create a lot of garbage to be closer to the maximum heap size and frequently "stop the world" to recover heap. No tests actually run out of heap, but the frequency of the GC affects the time it takes for the tests to run and tips tests over the 5 minute default. Tests suppressed: android.icu.dev.test.format.NumberRegressionTests#Test4212072 android.icu.dev.test.format.TimeUnitTest#TestBritishShortHourFallback Tests that generate a lot of garbage and slow down substantially when there isn't a lot of free heap: android.icu.dev.test.translit.TransliteratorTest#TestSourceTargetSet2 android.icu.dev.test.util.Trie2Test#TestRanges Bug: 62374714 Test: run cts -m CtsIcuTestCases on a Fugu Change-Id: I317b48b7c46c3934bd2b4835f7362f8d28009d78
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/format/TimeUnitTest.java
|
f86f25d102340da66b9c7cb6b2d5ecdc0de43ecf |
|
08-Dec-2016 |
Fredrik Roubert <roubert@google.com> |
Integrate ICU4J 58.1 with Android patches into android_icu4j. Bug: 31328818 Test: CtsIcuTestCases Test: CtsLibcoreOjTestCases Test: CtsLibcoreTestCases Change-Id: Ifd74d26625c7e8c9bb76e88cf419029241117282
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/format/TimeUnitTest.java
|
3a45e58d9461ee00f295ca8a6a29ef0860559e7e |
|
14-Mar-2016 |
Paul Duffin <paulduffin@google.com> |
Added support for running repackaged Android ICU4J tests using JUnit Adds JUnit integration classes under android_icu4j/runner that bridges between ICU4J's custom testing framework and JUnit. These classes were copied from cts/tests/tests/icu to here, moved into a new package (to remove cts and ensure that they do not clash with original classes in cts) and then made standalone so that they didn't depend on CTS. The intent is that the original classes will be removed and the CTS runner will use these classes, either directly or through standard Android/JUnit integration. In order for these classes to work with CTS they need to be able to skip execution, i.e. 'run' the tests in order to fire events but to not actually execute the tests themselves. This was previously done using a special parameters class but this uses the 'standard', in internal Android at least, AndroidRunnerParams class. As that class is not available on the host and the host does not require the ability to skip the execution this provides a dummy implementation that never skips. This also adds @RunWith annotations to the tests during repackaging so that they can be run using standard JUnit runners. The Android.mk file has instructions on how to run using both JUnit and the ICU4J test framework. There are a number of issues with running tests under JUnit but they will be fixed in follow on changes. Bug: 22023363 Change-Id: Iac1221c12cc7194277db49b9a013d427d9533b36
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/format/TimeUnitTest.java
|
aefe4d1f8f1773ead1a52f7a5d2c9e0009353600 |
|
26-Feb-2016 |
Paul Duffin <paulduffin@google.com> |
Add repackaged version of the ICU tests Adds a new android-icu4j-tests target to build the repackaged tests. The repackages tests were generated by running the following script which was modified to repackage the tests in addition to the source and sample. tools/srcgen/generate_android_icu4j.sh Bug: 22023363 Change-Id: I3c6e65ba6a4d24055343460a023d6671585146f5
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/format/TimeUnitTest.java
|