Manjula Kutty wrote:
Yes first time it was empty. I tried running this by taking a new
windows with new env setting and I got a report file. But still there
some errors when I redirected the ant emma-all to an output file. It
is like this
Someone (I think Dan as part of the jmx work) made a fix at some point
to make the error output from spawned network servers visible in the ant
output, and this exposed most of the errors you are seeing. These
problems were not visible when the EMMA work was first committed, though
they have been there all the time. I've been planning to fix it but been
stalled by other things, I'll send a reply to this thread when I've
gotten around to it.
From your output I see that there are other testfailures and errors as
well, and some noise related to EMMA permissions that is not because of
the spawned network servers. Probably new tests have been added that
need to be adapted to EMMA as well, and maybe some test failures are not
related to EMMA at all.
At the very end, the <emma-all> target will force a build failure if one
or more tests failed, but this happens after all reports have been
produced. Your coverage numbers will miss input from the code that did
not have permission to write to EMMAs coverage.ec file, but should
contain all the data from the other tests.
Vemund
checkVMLevel:
START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
[junit] java.security.AccessControlException: access denied
(java.io.FilePermission coverage.ec <http://coverage.ec> read)
[junit] at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
[junit] at
java.security.AccessController.checkPermission(AccessController.java:427)
[junit] at
java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
[junit] at
java.lang.SecurityManager.checkRead(SecurityManager.java:871)
[junit] at java.io.File.exists(File.java:700)
[junit] at
com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
[junit] at
com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
[junit] at
com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
[junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
[junit] at java.lang.Thread.run(Thread.java:595)
[junit] Exception in thread "EMMA shutdown handler thread"
java.lang.RuntimeException: EMMA failed to dump coverage data:
java.security.AccessControlException: access denied
(java.io.FilePermission coverage.ec <http://coverage.ec> read)
[junit] at
com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
[junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
[junit] at java.lang.Thread.run(Thread.java:595)
[junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:
This one occured quites few times
and in the last
emma-all:
BUILD FAILED
C:\derbydev\trunk\build.xml:2199: EMMA instrumented tests failed!
Total time: 118 minutes 0 seconds
I'm attaching the full output file.
Thanks
Manjula
On 3/28/08, *Daniel John Debrunner* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Manjula Kutty wrote:
> I tried ant emma-all.
>
> The following error was on the screen
> BUILD FAILED
> C:\derbydev\trunk\build.xml:2199: EMMA instrumented tests failed!
> It didn't create any other report file
So the junit_<date> folder was empty?
Dan.
--
Thanks,
Manjula.
