- 17 May, 2010 1 commit
-
-
Jesse Wilson authored
Adapted from master: https://android-git.corp.google.com/g/50612 Change-Id: I24cde108f1dd70532ff217545445cdc0b2650a48
-
- 04 May, 2010 1 commit
-
-
Peter Hallam authored
Merge xml except xmlpull and kxml into luni
-
- 30 Apr, 2010 1 commit
-
-
Jean-Baptiste Queru authored
Change-Id: I0dcadda241e7fd2a7429f9dd43d1ff5e945e5467
-
- 28 Apr, 2010 1 commit
-
-
Guang Zhu authored
* applying emma instrumentation causes OOM in dx * test packages don't need emma instrumentation anyway, it's the package under test that needs to be processed by emma Change-Id: I8e65d3750aae716c52fb98d0b8cd41a748344516
-
- 27 Apr, 2010 1 commit
-
-
Peter Hallam authored
-
- 23 Apr, 2010 1 commit
-
-
Peter Hallam authored
Change-Id: Ib4356b3cd57490df8ff246ea6a4bc1c269ba848b
-
- 16 Apr, 2010 1 commit
-
-
Elliott Hughes authored
Also move our ICU tests into our little tree of tests. Bug: 2596471 Change-Id: I73b53d74c26ef9bf670f12cac58b51ba61eefead
-
- 11 Mar, 2010 1 commit
-
-
Guang Zhu authored
emma library is used for collecting code coverage. Current pain point is that for collecting code coverage, developers either need to include emma as a local static library, or change BOOTCLASSPATH to include emma which includes hacking boot image and reflashing it. With this change, emma will be integrated into core.jar if EMMA_INSTRUMENT flag is on, so pushing the updated framework.jar and perform a runtime restart will make emma globally available to all code coverage tests. This change will only affect code coverage builds. Change-Id: I097254835ef4817d068e8946ecbec60135e1f515
-
- 26 Feb, 2010 1 commit
-
-
Elliott Hughes authored
The JDBC driver is from a different source (http://www.ch-werner.de/javasqlite/overview-summary.html) and is only really needed for testing. Bug 2468870 asks that we don't eagerly register the native methods for these classes. That bug is fixed by this change. Bug 2198667 asks that we stop shipping this JDBC driver as part of the base system. That bug is not addressed by this change: the classes and native code are now in their own, separate, .jar and .so files -- so they'll be easier to remove in future -- but for now those files are still in /system/framework and /system/lib respectively. Bug: 2468870 Bug: 2198667
-
- 22 Feb, 2010 2 commits
-
-
Elliott Hughes authored
(I removed the unused parameter from the wrong macro!)
-
Elliott Hughes authored
-
- 20 Feb, 2010 1 commit
-
-
Elliott Hughes authored
-
- 19 Feb, 2010 1 commit
-
-
Elliott Hughes authored
I started off with a mission to remove uses of dalvik.annotation.* (stuff like @TestTargetNew and other useless junk that just makes it harder to stay in sync with upstream). I wrote a script to go through tests showing me the diff between what we have and what upstream has, thinking that in cases where upstream has also added tests, I may as well pull them in at the same time... ...but I didn't realize how close we were to having dx fill its 1.5GiB heap. After trying various alternatives, I decided to bite the bullet and break core-tests up into one .jar per module. This adds parallelism back into this, the slowest part of our build. (I can do even better, but I'll do that in a separate patch, preferably after we've merged recent changes from master.) Only a couple of dependencies were problematic: the worthless TestSuiteFactory which already contained a comment suggesting we get rid of it, and the fact that some tests -- most notably the concurrent ones -- also contained main methods that started the JUnit tty-based TestRunner. (In the long run, we want to be running the harmony tests directly from a pristine "svn co" of upstream, using DalvikRunner. But this will be a big help in the meantime, and starts the work of getting our current copy of the tests into a state where we can start to extract any meaningful changes/additions we've made.)
-
- 11 Dec, 2009 1 commit
-
-
Jesse Wilson authored
we'll need to fix a few things before the UI for this is nice.
-
- 26 Oct, 2009 1 commit
-
-
Dan Bornstein authored
native code, and make each have a set of rules for building on the host. I also tightened up how sub.mk processing works and documented it a little better. Change-Id: I8a7a4c5697b2f22c4d69941dba381d6452200911
-
- 29 Apr, 2009 1 commit
-
-
Aaron Kushner authored
file outside of the Android build directory and was not getting cleaned up after the build.
-
- 03 Apr, 2009 1 commit
-
-
Jorg Pleumann authored
the RI so that the required test annotation classes are copied over from core.jar. Means we don't have to maintain duplicate versions of these classes (and there will be less verifier complaints), so these are going away in the process. Original author: jorgp Merged from: //branches/cupcake/... Original author: android-build Automated import of CL 144390
-
- 02 Apr, 2009 2 commits
-
-
Jorg Pleumann authored
the RI so that the required test annotation classes are copied over from core.jar. Means we don't have to maintain duplicate versions of these classes (and there will be less verifier complaints), so these are going away in the process. Original author: jorgp Merged from: //branches/cupcake/... Automated import of CL 144230
-
Jorg Pleumann authored
the RI so that the required test annotation classes are copied over from core.jar. Means we don't have to maintain duplicate versions of these classes (and there will be less verifier complaints), so these are going away in the process. BUG=1285921 Automated import of CL 144229
-
- 04 Mar, 2009 2 commits
-
-
The Android Open Source Project authored
-
The Android Open Source Project authored
-
- 16 Jan, 2009 1 commit
-
-
The Android Open Source Project authored
-
- 21 Oct, 2008 1 commit
-
-
The Android Open Source Project authored
-