| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've pretty much taken the upstream ResourceBundle implementations
as-is, putting back our string-to-locale conversion, removing a bit
of duplication and non-free, non-spec EBCDIC support, and hard-coding
the text of the MissingResourceExceptions (since harmony's changed
its message catalog from ours, so I had to touch those bits of the
code anyway).
(Why haven't I bothered to pay much attention to the resource bundle
implementations? Because I already rewrote our only code that was
using them to not use them, and third-party developers should be
using Android's resource system instead. There's very little chance
anyone needs Java resource bundles. I paid some attention to Properties,
because they're still somewhat useful.)
Also remove various unused messages, and update our tests. I've mostly
_not_ taken the upstream tests, because it would require a lot of work
that we'll be doing anyway when we switch to using their test suite
properly.
I ran the jtreg tests we're able to run, and the normal-case ones (plus
the stress test) seemed okay.
Bug: 2497395
Change-Id: I91606df0dc1a45e6974fbb27a0d334af87254f0b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
as known failures." into eclair
Merge commit 'ffea5cebcb45bb58d61b903f4e04c45f48442c86'
* commit 'ffea5cebcb45bb58d61b903f4e04c45f48442c86':
Mark libcore cert tests using expired certs as known failures.
|
| | |
| |
| |
| |
| |
| | |
Bug 2322662
Change-Id: If35a5a75f664535bd4eb97cf11a6afe5b0e5b4a9
|
| | |
| |
| |
| | |
This replaces PrefsTester and is more general purpose.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Squashed commit of the following:
commit e3083dde77b71fa817c8a52d9edafcb6325cfc25
Author: Elliott Hughes <enh@google.com>
Date: Fri Oct 9 13:10:11 2009 -0700
security_dalvik
commit 0fc0101e5dbfb3e3044702579ab8087a4e07984a
Author: Elliott Hughes <enh@google.com>
Date: Fri Oct 9 13:09:48 2009 -0700
security_527399
|
| |/
|
|
|
|
| |
Also rewriting SupportExec to use ProcessBuilder rather
than Runtime.exec(). Changed callers to use the ProcessBuilder
directly rather than calling-through chained methods.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Since ClassLoader.isAncestorOf has been fixed these tests now succeed.
So they can be reactivated.
BUG=1732214
|
| |
|
|
|
|
|
|
| |
don't work properly in the CTS environment for
some reason.
BUG=1285921
Automated import of CL 148447
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the CTS, but worked fine in run-core-tests:
- One cert test needs isolation, because
it destroys the security provider.
- The Thread.sleep() tests were too flaky.
- Tests that tried to open a temporary DEX
file failed in the CTS because we do not
have access to the system DEX cache. We
are now simply creating our own.
The Java plan in the CTS should now pass
fully. Yippie!
BUG=1285921
Automated import of CL 147896
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
core tests work better in the CTS
environment. Some tests had to be
marked broken either because they
either expose different behavior
than in run-core-tests or they
take too much time (beyond the
CTS' timeout).
BUG=1285921
Automated import of CL 147838
|
| |
|
|
|
|
|
| |
Some tests are still failing in the cts host environment. This CL fixes most of them in the security module
BUG=1285921
Automated import of CL 147660
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Some need to be marked broken, because
they take too long (or even forever) due
to implementation problems. Some need
to take into account differences between
the CTS environment and the Dalvik VM,
so they succeed in both cases.
BUG=1285921
Automated import of CL 147464
|
| |
|
|
|
|
| |
BUG=1285921
Automated import of CL 145288
|
| |
|
|
|
|
|
| |
adding lots of missing headers in the process).
BUG=1285921
Automated import of CL 143458
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
