Patricia Shanahan wrote:
On 11/19/2010 10:06 AM, Sim IJskes - QCG wrote:
On 11/19/2010 06:20 PM, Apache Hudson Server wrote:
See<https://hudson.apache.org/hudson/job/River-trunk-QA-windows/7/>
[java] # of tests started = 1410
[java] # of tests completed = 1410
[java] # of tests skipped = 46
[java] # of tests passed = 1363
[java] # of tests failed = 47
https://hudson.apache.org/hudson/job/River-trunk-QA-windows/ws/jtsk/trunk/qa/result/index.html
Some tests failed on policy permissions (so it looks), any change that
this is windows related? slash vs backslash and driveletter?
I have run the first failing test,
com/sun/jini/test/impl/start/ActivateWrapperActivateDescTest.td, under
WindowsXP, and reproduced the failure. The test passes on an identical
checkout, compiled and run with the same JDK version, on a Ubuntu
VirtualBox.
That creates a strong presumption that we are indeed dealing with a
Windows related issue, such as the horrible Windows file naming.
The first error in the log is:
[java] com.sun.jini.qa.harness.TestException: Unexpected
exception starting service; nested exception is:
[java] Problem creating service for sharedGroupImpl; nested
exception is:
[java] exception constructing object; nested exception is:
[java] java.lang.SecurityException: ProtectionDomain
ProtectionDomain (file:/C:/apache2/River/lib/group.jar <no signer
certificates>)
[java] null
[java] <no principals>
The failure is during set-up, so it is quite likely that a lot of
tests are affected by the same problem.
Any advice on how to check the signer certificates?
Thanks,
Patricia
Your failure isn't caused by <no signer certificates>, that's just
information printed from the ProtectionDomain, did the failing
ProtectionDomain list the Permissions?
What was the Permission that failed?
When ProtectionDomain.toString is called, it merges the dynamic
Permissions from the policy with the static Permissions in the
ProtectionDomain and prints them all out, useful for debugging.
Peter.
