| e1833aa2673d4f975ad35e7a39317feeea922fe1 |
|
23-Feb-2017 |
Sebastien Hertz <shertz@google.com> |
Fix warnings of JDWP tests
This CL fixes general warning issues:
- Adds missing @Override annotations
- Adds parameterized types for generic classes (List, Iterator, ...)
- Removes unused imports
- Removes declared method exceptions which are not thrown
- Adds @SuppressWarning annotations in debuggee classes (like when a
symbol is not used in the code but is accessed through debugger)
- Makes inner classes static when possible
More specific issues (related to design, ...) will be addressed in
separate CLs.
Test: art/tools/run-jdwp-tests.sh --mode=host --variant=X64
Change-Id: I83709f5d76b2a8c9268cd11dd7884982d5d06f2d
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/share/JDWPUnitDebuggeeProcessWrapper.java
|
| 4372c1a37417b2231fa39ce152d1861595a12332 |
|
27-Aug-2015 |
Sebastien Hertz <shertz@google.com> |
JDWP: fail test if debuggee does not exit normally
Makes a test fail if the debuggee exits with an error. This prevents
from passing a test while the debuggee aborts (during runtime
shutdown for instance).
By default, we expect the debuggee to exit with code 0. The tests
related to VirtualMachine.Exit command (that forces the runtime to
exit with a given error code) can specify a different exit code with
JDWPUnitDebuggeeProcessWrapper.setExpectedExitCode method.
Bug: 22907762
Bug: 17941266
Change-Id: I1acd4a4251d8cb3a335e581aef1792ea1049ba74
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/share/JDWPUnitDebuggeeProcessWrapper.java
|
| 5f0a23683aa603d8c50b6dd071a565821b76067b |
|
10-Dec-2011 |
Elliott Hughes <enh@google.com> |
Add harmony's jdwp tests.
Change-Id: I1c0e70cd9e07244fe422a4f77f3727b55ec28402
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/share/JDWPUnitDebuggeeProcessWrapper.java
|