switching the order of the addTest() calls in the All.java packages
makes the problem go away in my environment (classes, SANE, ibm15 jvm) -
at least in my smaller test case - I haven't tried the full suite.
If we can't find real fix soon, I would be ok with checking temporary
change to switch the order of the tests, to eliminate the encryption
suite error noise.
Daniel John Debrunner wrote:
Kathey Marsden wrote:
Daniel John Debrunner wrote:
I don't see any reason to disable working tests, the Encryption suite.
Would you object to my moving it before the upgrade suite to avoid
whatever is going on with running the upgrade tests first and keeping
the bug open for investigation. I am guessing it is related to
something funny happening with the class loaders in that test, leaving
us without the correct privileges and not a derby problem.
I don't think it's a class loader problem. I believe it's related to the
way the test harness sets up security managers. I'm looking at a fix now.
Dan.
