| 0585c04e4930e6811cb7322f522bb0b807991da7 |
|
07-Jun-2017 |
Igor Murashkin <iam@google.com> |
android: Add support for 1.8 javac and desugar
Using --toolchain jdk will now pass the correct dx minimum api level
(enabling it to use default methods, method handles, etc).
Vogar also now calls desugar before dx to convert invoke-dynamic lambdas
into anonymous inner class lambdas (because Android does not have
a LambdaMetafactory).
Test: art/tools/run-libcore-tests.sh --mode=host
Test: art/tools/run-libcore-tests.sh --mode=device
Test: vogar --toolchain jdk --mode activity --no-multidex libcore/luni/src/test/java/libcore/java/lang/ShortTest.java
Test: vogar --toolchain jdk --benchmark --mode device libcore/benchmarks/src/benchmarks/InvokeInterface.java
Test: java -cp ${ANDROID_BUILD_TOP}/out/host/linux-x86/framework/vogar-tests.jar org.junit.runner.JUnitCore vogar.AllTests
Bug: 36902714
Bug: 37461882
Change-Id: I9553e8304c269cd7e4e2b989729d785852e85f4e
/external/vogar/src/vogar/android/AndroidSdk.java
|
| a6b957f25de87ad5287d4d187ea8ae4d8292306b |
|
23-May-2017 |
Paul Duffin <paulduffin@google.com> |
Ignore virtualdeviceknownfailures.txt in default expectations
After the work to consolidate the multiple libcore/expectations/
files (excluding virtualdeviceknownfailures.txt) into a single
knownfailures.txt file this change defaults to using the
knownfailures.txt rather than scanning the libcore/expectations/
directory for all .txt files.
That prevents us from picking up the
virtualdeviceknownfailures.txt expectations file by default.
Tested by running test in virtualdeviceknownfailures.txt and
knownfailures.txt and one not in either to ensure that they
build correctly.
Bug: 35863862
Test: Run art/tools/buildbot-build.sh -j30 --host
Change-Id: I946a0e844c7b5714877a81aac653ceb2c96af6ae
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 388fcad5269758e893c6982fa9e4c2fbb474460a |
|
14-Feb-2017 |
Neil Fuller <nfuller@google.com> |
Adding multidex support to vogar
--multidex now exists to pass the necessary flags from vogar to
dx / Jack for (native) multi-dex. This flag is true by default
but can be disabled with --no-multidex.
Primary testing was to run the command line below with a
.jack that Jack is reporting as over the 65k limit with
--no-multidex / --multidex.
vogar --classpath out/target/product/angler/obj/JAVA_LIBRARIES/core-tests_intermediates/classes.jack \
libcore.java.lang.StringTest
The change was confirmed with convoluted manual testing for
--toolchain jdk --language J17 (legacy case using dx).
Also, the vogar tests were run:
java -cp ${ANDROID_BUILD_TOP}/out/host/linux-x86/framework/vogar-tests.jar \
org.junit.runner.JUnitCore vogar.AllTests
Bug: 35308152
Test: See above
Change-Id: I90527a92f11d4d38bbcaff98cd11427ae489ee2b
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 1bb8f9522536e88c44c6d1f6d781385a2ebfb8af |
|
19-Jan-2016 |
Narayan Kamath <narayan@google.com> |
Add versionCode / versionName to all aapt invocations.
The CTS test runner chokes with a mysterious error if it finds an
APK on the system without a valid version name. In particular, it
chokes on vogar test APKs (for mode=activity).
Change-Id: I835c46952ee690fd85c92b4ad254c3c354e316b9
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 9486a05651c37e5cecc0889b398b2c837929b18c |
|
15-Jan-2016 |
Neil Fuller <nfuller@google.com> |
Add --toolchain jack support for target
Testing suggests it works on target as well
as on host.
Change-Id: I2fbebb1ec0e21d02e078226e55f589976679ae7d
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 7029503206e4c89fe167c3389c1062d89cf35c52 |
|
19-Nov-2015 |
Paul Duffin <paulduffin@google.com> |
Refactoring to make more testable
Prior to making a change in the behaviour to fix an issue with
the quoting of command line arguments this refactors the
existing code and adds some tests to illustrate the existing
behaviour. This will minimize the chances that the fix will
break existing code.
The changes are explained below in more detail.
This applied a couple of common refactorings to a number of
classes:
* Where classes were creating a lot of subsidiary objects in
their constructor I switched to using the dependency injection
pattern (i.e. passing in parameters to the constructor). That
makes it easier for tests to override the behaviour.
* Where classes were being given a huge object (e.g. Run) but
only required a small number of it's fields I replaced the Run
constructor parameter with the individual parts.
LocalTarget - Replaced Run with Log, Mkdir, Rm.
Run - Passed in more parameters into the constructor, moved the
code that created those objects into Vogar.run(). Also, make the
vogarJar() method work when running from a class directory to
allow it to work from within IDEA as well as when running from
jars.
SshTarget - Removed a bit of duplication of the command line
prefix used to run a script remotely.
Target - Method defaultDeviceDir() was removed and the
implementations were made static and accessed directly from
Vogar. That is necessary to break a dependency cycle; AdbTarget
required AndroidSdk, which required DeviceFileCache, which
required runnerDir, which required Target.defaultDeviceDir().
Previously, that was broken by passing the DeviceFileCache to
the AndroidSdk after construction using the setCaches() method
but that has been removed as part of this refactoring.
Vogar - Made the constructor and parseArgs(String[]) visible for
testing. Moved some of the code from Run's constructor here to
create the values to be passed into its expanded constructor.
TargetType was added to encapsulate the defaultDeviceDir() for
each Target implementation class. That allowed the cycle
described in Target to be broken.
AdbTarget - Replaced Run with individual fields. Moved
functionality from AndroidSdk that's only used by this class
into here (waitForDevice(), ensureDirectory(File), remount(),
rm(File), forwardTcp(int), push() and pull()). Bringing in
push() also required moving the pushCache from AndroidSdk as
well. Added DeviceFilesystem as a parameter to avoid having to
have a reference to AndroidSdk.
AndroidSdk - Moved logic that runs shell commands to calculate
the compilationClasspath and androidJarPath out of the
constructor and into a static method to allow tests to pass
dummy values straight into the constructor. Marked constructor
as VisibleForTesting. Removed setCaches(..) method and
pushCache, passed the HostFileCache straight into the
constructor, marking the dexCache field as final. Added explicit
exception when can't find platforms directory rather than
NullPointerException. Moved methods that are only used by either
AdbTarget or DeviceFileCache into those classes.
DeviceFileCache - Replaced AndroidSdk with DeviceFileSystem and
moved cp(File, File) and mv(File, File) from AndroidSdk into
here.
DeviceRuntime - Added a Supplier<String> parameter to provide
the device user name in order to allow tests to provide their
own. That is needed because otherwise the test will attempt
to connect to a device to determine the user name.
Command - Added method to access the args for testing, moved the
special processing of "-c" option from start() into a method
called from the constructor. That allows the test to verify the
processing of that without actually executing the command.
Cleaned up unused workingDirectory method and some minor
warnings.
Added some tests and fixed a compile issue with the
JUnitRunnerTest.
Change-Id: Ib1676ee19a4f0e7a8944b2708a6dbe3899d1d292
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 96a958d12e94ff61201d5584bcde922072b9ee2c |
|
02-Oct-2015 |
Rayhaan Jaufeerally <rayhaan@google.com> |
Remove bogus path to adb.
Use null instead of a path that does not exist as a placeholder.
Change-Id: I85968b4614e659f856893a88d3289f6dd4d37362
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 05ae91d2449f66381c5c828ee25189618ac2b5a8 |
|
02-Oct-2015 |
Rayhaan Jaufeerally <rayhaan@google.com> |
Fix to avoid npe when no parent file.
AndroidSdk was doing many getParentFile calls. These can return null.
A safer method was made which does null checks at each stage.
Change-Id: I7b97ecea6a2361f64bda2d3a20d4ae38161c31a1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 7021ab7bc4cf980ca3bb5a955a97a499d998ae30 |
|
30-Sep-2015 |
Rayhaan Jaufeerally <rayhaan@google.com> |
Improve robustness of path finding with OUT_DIR.
Restructuring of the logic to find where built libraries are,
especially in cases with the OUT_DIR environment variable set,
as well as just using ANDROID_BUILD_TOP.
Change-Id: I3c5abefff383d107c09cfe0c79683d2da96260ca
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 62106fdd69bfaef4605713eca9e62888402ff2f5 |
|
30-Sep-2015 |
Rayhaan Jaufeerally <rayhaan@google.com> |
Fix: uninstall task for adb return code, path to android jar.
Now that ADB seems to provide correct return codes, the uninstall
task fails if the app has not been previously installed. Vogar
runs the uninstall task to make sure it is not already there
so if the app is not found, this causes mode activity to fail.
Also fix the hardcoded path to the prebuilt android android.jar
to work from anywhere, not just the root of the repository.
This works based on the ANDROID_BUILD_TOP environment variable
which envsetup/lunch sets.
Thid change also updates vogar to work with modern relasees of
the SDK. The code looking for paths in the sdk has not been updated
and was assuming the structrure is how it was in gingerbread.
Change-Id: I84354939c646106c091eacc7dd7fbf62170a5695
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 4a1d4baa4c447b2569a507f1bd8924ebf05395c6 |
|
29-Sep-2015 |
Neil Fuller <nfuller@google.com> |
More non-zero exit code fixes
Waiting for the device can return a non-zero
exit code.
Bug: 24250996
Change-Id: I622d2f1dbb0864ea65833a94f6182282caa1bcf5
/external/vogar/src/vogar/android/AndroidSdk.java
|
| f22fe9e961a0a40db1e65229f3ad36ac9326adde |
|
21-Sep-2015 |
Nicolas Geoffray <ngeoffray@google.com> |
Use dx instead of adb for looking up sdk paths.
adb is not useful for host testing.
Change-Id: I65c56a5c31acf797322efb9787ac7cf360c22563
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 3fd1cf5ff629b06b63f09b79508ec290af07267f |
|
21-Sep-2015 |
Neil Fuller <nfuller@google.com> |
Fix vogar target ls / rm tasks in the event of errors
The latest aosp/master adbd appears to report adb shell exit codes
properly.
vogar was previously relying on this not being the case.
It is possible that recent commit 99a9b24d3c broke the clean up task
behavior, but that doesn't appear to explain all the breaks.
Older devices (e.g. L-MR1) still return exit code 0 for command
failures.
This change returns the behavior to ignoring exit codes for the adb
shell tasks. Because the behavior is device-version specific there
isn't much point relying on the new exit-code behavior because vogar
would not function on the old devices.
Bug: 24250996
Change-Id: Iae7c992320c5e2caa6bdb3473a8d2536947c3ca2
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 83909fb7735168d513557d6433e76ae6ffd7ea26 |
|
21-Sep-2015 |
Neil Fuller <nfuller@google.com> |
Fix vogar when OUT_DIR is not set
Commit 128163bc broke it. Commit af11af97e was a follow up
to fix host but did not fix it for target.
Change-Id: Ibd206117a42628d52a137d12c94527f1e9e5dcb0
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 128163bc9658aad4a0b331ff9a777a7719d8c459 |
|
18-Sep-2015 |
Alex Light <allight@google.com> |
Make vogar work if one uses OUT_DIR
Change-Id: I19824d792d5dcbed32846912fb36654894fcc0ac
/external/vogar/src/vogar/android/AndroidSdk.java
|
| fca99ba6a930cd7a36b1807c0201f49a80cadcf6 |
|
13-Jul-2015 |
Rayhaan Jaufeerally <rayhaan@google.com> |
Experimental support for jack on host mode.
This includes adding a --toolchain={jack,jdk} option which chooses what
to compile sources with. Currently only works with host mode and pending
on b/22382563 to be able to properly compile code with dependencies on
the surrounding package. This depends on the prebuilt jack jar file in
AOSP.
Change-Id: Id4d5eaa51318009fd8a147e4c548be3c62f9c5aa
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 9e81cc65e6995960f87b267f17eebce7cabf46a8 |
|
26-Jun-2015 |
Nicolas Geoffray <ngeoffray@google.com> |
Remove apache-xml-hostdex, we don't include it in core.oat.
Change-Id: I169b9ccf5480ec93d6335e71e94b65181be0e987
/external/vogar/src/vogar/android/AndroidSdk.java
|
| e77f107f2afff07ab916f51b8847fd69ef210261 |
|
21-Jan-2015 |
Neil Fuller <nfuller@google.com> |
Remove default resource dirs
The resource defaults only work when the user is in their repo root.
This leads to confusing different behavior based on the users current
working directory (this is still true of other flags even after this
change) and their mode.
Those resources are included in the core-tests-support target.
The resources in luni/src/test/resources include a .class file which
causes problems for dx if you include both the core-tests.jar *and* the
default resources are found.
The best approaches are probably:
make -j32 core-tests-support
vogar --mode <host|device> --classpath out/target/common/obj/JAVA_LIBRARIES/core-tests-support_intermediates/javalib.jar <Test .java file>
or
make -j32 core-tests
vogar --mode <host|device> --classpath out/target/common/obj/JAVA_LIBRARIES/core-tests_intermediates/javalib.jar <name of Test class>
Bug: 19081566
Change-Id: Id4335cb81c2c6b21c540d43250f087df9c80fb74
/external/vogar/src/vogar/android/AndroidSdk.java
|
| ab130e4323645a4ce682eb2b871b6b22ca2e5d3a |
|
01-Dec-2014 |
Nicolas Geoffray <ngeoffray@google.com> |
Only loop on /sdcard when waiting for tmpdir to be ready.
/sdcard is a mount point, so we special case it. For other
directories, we assume they are not.
Change-Id: I1d01fb9a61103ca002460d2e786d4bd35f99256d
/external/vogar/src/vogar/android/AndroidSdk.java
|
| c620846e4044b3b3a8abfc42ddba4adca4e545d9 |
|
05-Aug-2014 |
nfuller@google.com <nfuller@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Adding back support for Dalvik.
Laying groundwork for 64-bit ART support (--var)
Fixing app_process / activity modes.
Refactoring / renaming classes to better
reflect their purpose.
--mode device and --mode host are for ART-only
releases.
--mode device_dalvik and --mode host_dalvik are
for Dalvik releases.
--mode device_art_kitkat and --mode host_art_kitkat
are for running ART on KitKat releases. Host mode
appears broken, not sure why.
--mode app_process is ART-specific now unless run with
an SDK.
--mode activity didn't appear to work. It works for
simple tests now with ART or with an SDK.
L introduced some changes to System property
behavior which broke TestEnvironment and have been
worked around.
git-svn-id: http://vogar.googlecode.com/svn/trunk@299 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 50e898cf2b0a57fe7eddb02efc5df5658a03b322 |
|
27-Jun-2014 |
nfuller@google.com <nfuller@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Update vogar to use core-libart instead of core on
device and host
The core library was deleted from AOSP recently, and the
host build defaulted to using ART some time ago.
git-svn-id: http://vogar.googlecode.com/svn/trunk@298 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| c69effc4a5ea207ecbf690f70025cf88c3706a1c |
|
01-Mar-2014 |
limpbizkit <limpbizkit@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Use adb to find the Android SDK.
git-svn-id: http://vogar.googlecode.com/svn/trunk@297 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 9316ee39ff443a7d60e1cbbd98b7dfa561a9a454 |
|
01-May-2013 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Add conscrypt to Android BOOTCLASSPATH lists
git-svn-id: http://vogar.googlecode.com/svn/trunk@292 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 0985b4917009b393c73c8bb20218fcbaad90629b |
|
05-Apr-2013 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Add okhttp to Android BOOTCLASSPATH lists
git-svn-id: http://vogar.googlecode.com/svn/trunk@289 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| c3487a4caaec6650f3db68c7891ebc0b55c485ea |
|
07-Mar-2013 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
src/vogar/android/AndroidSdk.java: fix "--mode activity", at least from the root of a build tree. Tests that require a Context still fail, but this is a step forward:
junit.framework.AssertionFailedError: Context is null. setContext should be called before tests are run
at junit.framework.Assert.assertNotNull(Assert.java:218)
at android.test.AndroidTestCase.testAndroidTestCaseSetupProperly(AndroidTestCase.java:46)
git-svn-id: http://vogar.googlecode.com/svn/trunk@287 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 5379730d1295c75e2b7b1c6d193e74ba5f54cf17 |
|
04-Dec-2012 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Automatically add libcore resource directories to the runtime classpath.
Note that I added a new flavor of classpath. You might think I could have
just reused the existing --classpath, but that's supplied at compile time
as well as run time, and there might be all kinds of confusing files in
the resource tree that shouldn't be shown to the compiler. (This is certainly
the case with libcore. You can't build with the resource directories on the
compile time classpath.)
git-svn-id: http://vogar.googlecode.com/svn/trunk@285 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| a0e9a4c9feae886800147c9786c753fdb18b74b9 |
|
03-Dec-2012 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Make it possible to run tests that use MockWebServer from within libcore/.
Previously you had to be in the root of an Android tree because we were
using pathnames relative to the current directory.
git-svn-id: http://vogar.googlecode.com/svn/trunk@284 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 5bb07a69fb7cefb6861584ea8a4279c439988e84 |
|
09-Jul-2012 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
src/vogar/android/AndroidSdk.java: automatically make MockWebServer available if you're running in an Android tree. (So more libcore tests are runnable by default.)
git-svn-id: http://vogar.googlecode.com/svn/trunk@279 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 0eb0936e90bf11463c8ee937ca996d7bd654a098 |
|
07-Dec-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Get most of running on a device via SSH working.
Run on a device like this:
vogar --mode device --ssh 192.168.149.198:2222 SocketTest.java
Currently this is failing because dalvikvm segfaults when invoked via SSH. I suspect it might be a problem with the SSH server running with either the wrong environment or the wrong privileges. I continue to investigate
git-svn-id: http://vogar.googlecode.com/svn/trunk@266 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 3671608cddf45a9fd12c38b62ecf3f42488e94d9 |
|
18-May-2011 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Ignore non-numeric SDK versions
git-svn-id: http://vogar.googlecode.com/svn/trunk@256 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| da0e7eec779bc04c3a6e2bed5943d6d24ed0ca59 |
|
22-Apr-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Properly set user.dir for device processes.
git-svn-id: http://vogar.googlecode.com/svn/trunk@252 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 16edacf67341c54c5c9bf620ef801a83b001f795 |
|
20-Apr-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Now that we've crossed into double-digit platform names, we can't rely on string sorting to pick the newest.
git-svn-id: http://vogar.googlecode.com/svn/trunk@251 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 4b226442a94355095b746b896911eef47e38e569 |
|
25-Feb-2011 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
src/vogar/android/AndroidSdk.java:
src/vogar/Vogar.java: compile against the hostdex jar files when we're in "--mode host".
git-svn-id: http://vogar.googlecode.com/svn/trunk@237 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| dcd73a925922aab31fb62c101b0f6431f287ca9c |
|
25-Feb-2011 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
src/vogar/android/AndroidSdk.java: drop support for pre-gingerbread SDK trees, but free "vogar --mode host" from the need for an adb binary. Even quicker host builds ahoy!
git-svn-id: http://vogar.googlecode.com/svn/trunk@236 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 113ce61778b29f3d013c58cfb080f3e88ac405df |
|
22-Jan-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Manually sync vogar's copy of the dalvikvm boot classpath with reality.
git-svn-id: http://vogar.googlecode.com/svn/trunk@228 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| b8e5c25c980d23184f5065816dd9824401f734ad |
|
03-Jan-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Permit .zip files on the classpath!
git-svn-id: http://vogar.googlecode.com/svn/trunk@224 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| fe4b051c17bfc90dfeabca55ba5ace511cfb9bcc |
|
30-Dec-2010 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Fix varargs compile warnings
git-svn-id: http://vogar.googlecode.com/svn/trunk@222 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| b5c5c44d0c0a01c278cdac68ae23646682eb8ef7 |
|
19-Dec-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Inject the log rather than looking it up statically. This is needed for other apps that want to reuse the ExpectationStore but not the rest of Vogar!
git-svn-id: http://vogar.googlecode.com/svn/trunk@219 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| ae324821175dc34bd18d04656934c27f42e72048 |
|
16-Dec-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Support building with the reorganized gingerbread SDK.
git-svn-id: http://vogar.googlecode.com/svn/trunk@216 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| f343228f6d88cf9ca2e7279ec1808ee2a91c5b18 |
|
14-Sep-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Using new .jar locations for host builds.
git-svn-id: http://vogar.googlecode.com/svn/trunk@156 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| ce1223de05f8d4d34f1607b11043c7f04ce00e12 |
|
23-Jul-2010 |
jsharpe@google.com <jsharpe@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Have vogar automatically pull XML files that it finds in the temporary directory after the test/benchmark has terminated. This is mainly to retrieve Caliper failure output.
The device-version is a bit lamer (no directory recursing, except a special-cased "caliper-results") since unlike on the host, there isn't currently a great way of checking if a given file is a directory or not (that I know of). This could be rememdied by improving androidSdk.ls() to check file metadata.
git-svn-id: http://vogar.googlecode.com/svn/trunk@137 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|
| 969d5622a380e2f2f9ebdfbf7a22cbb3e031125b |
|
22-Jul-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Move all Android-specific classes to their own package.
git-svn-id: http://vogar.googlecode.com/svn/trunk@133 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/android/AndroidSdk.java
|