| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |/
|
|
|
|
| |
Use the same technique frameworks/base uses when building external/apache-http
to build the dalvik_jtreg dependencies. This is ugly, but seems to keep the
host and device builds off each others' toes.
|
| |
|
|
| |
we'll need to fix a few things before the UI for this is nice.
|
| |
|
|
| |
Also fixing the number of threads used by the driver.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
will compile a focused set of tests, install them on the device, and
run them.
There are still some features missing in the current test runner:
- it requires JUnit to be compiled manually "mmm external/junit". I'm
trying to figure out why our build system cannot find it.
- it requires the full test suite already be on the device. This is
necessary for the support test files and annotations. I intend to
create a follow up change to move those into a smaller target.
For now "mmm dalvik snod" will build these.
- JUnit test expectations are at the class level, not the method level.
I don't yet have a mechanism to introspect the .java file from JUnit
to get its method-level detail.
- jtreg tests can only be run as a directory, not as a single test.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
* changes:
Suppressing an invalid test that's checking implementation details.
|
| | | |
|
| |/
|
|
| |
This fixes 2 broken tests in RandomAccessFile, and possibly others.
|
| |\
| |
| |
| |
| | |
* changes:
Fixing a simple concurrency issue in the jtreg runner.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
| |
This is the absolute least amount of sanitization that will work.
I'll consider adding more as necessary; currently I'm not too
interested in spending the time to make this perfect.
|
| |
|
|
|
|
|
| |
This change adds some unfortunate code duplication between
the jtreg runner and the CoreTestSuite runner. I'd like to
eventually loop back and create a unified test runner for
either type of test.
|
| |
|
|
|
| |
Also fixing some problems with the Android.mk which was
pointing at an old version of the Run class.
|
| |\
| |
| |
| |
| | |
* changes:
Supporting expected results for the jtreg test runner.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is necessary to suppress false positives when dalvik
intentionally differs from the RI. This came up in the fix
for issue 2224903.
Also adding additional features to the jtreg runner to make
it useful as an iterative development tool:
- debugger support, to debug through running tests
- verbose output, to aid in diagnosing hangs
Also adding a few ".expected" files for known test failures.
Hopefully this is scalable.
Renaming Run to TestRun and extracting Result as a top-level enum.
|
| |\ \
| |/
|/|
| |
| | |
* changes:
Update logging to r820767
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
|
|
Much of the work of the tool is managing three versions of our code:
- the current Harmony code
- the current Dalvik code
- the common ancestor, an older version of Harmony
The tool calls out to the command line to perform the actual filesystem
work. Eventually I'd like to support all of our modules, and also
gathering diffs to send upstream to Harmony.
|
