c6428e1bcddf0c04ed9f58bf6c89a33d70f75a95 |
|
07-Jun-2017 |
Andreas Gampe <agampe@google.com> |
Vogar: Remove Android Sampling Profiler support The sampling profiler has been unmaintained and untested, and will be removed. Bug: 37272346 Test: m Test: Device boots Test: art/tools/run-libcore-tests.sh Test: java -cp ${ANDROID_BUILD_TOP}/out/host/linux-x86/framework/vogar-tests.jar org.junit.runner.JUnitCore vogar.AllTests Change-Id: I64d77244b5816ef1f605d19530b96be38f5c1bc6
/external/vogar/src/vogar/TestProperties.java
|
ac117540661a3e68d036fc5e772ba281ab8a9b55 |
|
13-May-2016 |
Paul Duffin <paulduffin@google.com> |
Improve error reporting when class cannot be run If there is an error when preparing to run a class then it reported a failure by the name of the action being performed rather than the failing class. When running an action that tries to run multiple classes that results in information being lost. This just switches to use the name of the class that fails which allows the QUALIFIED_NAME parameter to be removed. Change-Id: Id736a3014c06afb1b752ac8390cff2779fd39bf1
/external/vogar/src/vogar/TestProperties.java
|
5a0d2c2895b17899dc21f112e79cd550572846ee |
|
28-Mar-2016 |
Paul Duffin <paulduffin@google.com> |
Restrict when Caliper benchmarks are run. Caliper benchmarks will only be run when --benchmark is specified. They also will not be allowed when --mode=activity. This removes the need for the client to send the host the name of the runner that ran the tests. That was only used to check that the CaliperRunner was always run with the --benchmark option but that will always be true as the CaliperRunner is only used when --benchmark option is specified. That allows us to remove the runnerClass parameter to TargetMonitor.outcomeStarted(...). Bug: 26716337 Change-Id: I1a1e4a9e35a6dbd0424cc1ed086ee5f2b022865c
/external/vogar/src/vogar/TestProperties.java
|
cef780b87ae30112756d40ea3c639a1660fd7c29 |
|
26-Feb-2015 |
Nicolas Geoffray <ngeoffray@google.com> |
Add a --test-only option to Vogar. Option disables running caliper and classes with main. Change-Id: I5fa5221bc9842dffd1b1f676751b0b892b876449
/external/vogar/src/vogar/TestProperties.java
|
db82cde9016d812b26b6c79e375fdf60ead1d9fa |
|
02-Dec-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Redefine Environment to Target, with "AdbTarget" and "LocalTarget" implementations. This makes it possible for a new "SshTarget" implementation. git-svn-id: http://vogar.googlecode.com/svn/trunk@265 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|
1bdeb9dd8f1ab3f308c285729af007ae8970425b |
|
29-Oct-2010 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
vogar --profile support From the vogar usage message: --profile: run with a profiler to produce an ASCII hprof file. --profile-file <filename>: filename for hprof profile data. Default is: java.hprof.txt --profile-depth <count>: number of frames in profile stack traces. Default is: 4 --profile-interval <milliseconds>: interval between profile samples. Default is: 10 --profile-thread-group: profile thread group instead of single thread in dalvikvms Note --mode jvm only supports full VM profiling. Default is: false New command line arguments parsing and usage: src/vogar/Vogar.java For the RI, we pass the profile arguments via -agentlib:hprof src/vogar/JavaVm.java TestRunner now uses the new Profiler class. Also removed unnecessary args argument from run methods. src/vogar/target/TestRunner.java New abstract Profiler class and its Android implementation. When running on the RI, hprof is used outside of the TargetRunner. Because SamplingProfiler is not a public class, it is accessed via reflection from AndroidProfiler. src/vogar/target/Profiler.java src/vogar/android/AndroidProfiler.java New TestProperties for profiler options src/vogar/Mode.java src/vogar/TestProperties.java Retrieve the profiler output in the dalvikvm src/vogar/RetrievedFilesFilter.java Runner.init now takes profile so that Caliper can know to run with --debug src/vogar/target/Runner.java src/vogar/target/CaliperRunner.java src/vogar/target/JUnitRunner.java src/vogar/target/JUnit4Runner.java src/vogar/target/MainRunner.java javadoc correction src/vogar/android/EnvironmentDevice.java src/vogar/EnvironmentHost.java Caliper revision 253 lib/caliper.jar http://code.google.com/p/vogar/issues/detail?id=16 git-svn-id: http://vogar.googlecode.com/svn/trunk@194 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|
bb839669920429d0bef3c41d05e62dfa87fc1ee9 |
|
15-Jul-2010 |
bdc@google.com <bdc@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
javadoc TIMEOUT units of measure as seconds git-svn-id: http://vogar.googlecode.com/svn/trunk@129 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|
d296ba8af13d367b4a701ddeba405ee51caa05c1 |
|
19-May-2010 |
enh@google.com <enh@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
src/vogar/commands/AndroidSdk.java: src/vogar/commands/Command.java: src/vogar/Driver.java: src/vogar/Mode.java: src/vogar/target/CaliperRunner.java: src/vogar/target/JUnitRunner.java: src/vogar/target/MainRunner.java: src/vogar/target/Runner.java: src/vogar/target/TestRunner.java: src/vogar/TestProperties.java: src/vogar/Vogar.java: pass --timeout through to the JunitRunner. This isn't sufficient; try "~dalvik-prebuild/bin/run-harmony-tests --timeout 10 org.apache.harmony.nio_char.tests.java.nio.charset.AllTests tests.api.java.nio.charset.AllTests", for example. We still end up skipping a lot of tests, and when we time out, we get "Received bad XML from localhost:8787 org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.". git-svn-id: http://vogar.googlecode.com/svn/trunk@62 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|
a7a8fe1efa0fb3299d68709d60701a045bcc72f3 |
|
13-May-2010 |
jsharpe@google.com <jsharpe@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Add class analysis so that we no longer rely on file names to determine which type of test to run (e.g. junit, caliper, etc). This decision is also now made on the device side. As a result cleaned up the RunnerSpec classes, which are no longer required. git-svn-id: http://vogar.googlecode.com/svn/trunk@53 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|
7850f3f3da0099b76f09ed64d23e0a43ba4a5c76 |
|
23-Apr-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Initial checkin of vogar! git-svn-id: http://vogar.googlecode.com/svn/trunk@2 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/TestProperties.java
|