#124 EclEmma Snapshot Does not display results

closed-works-for-me
nobody
JaCoCo (32)
5
2014-08-25
2012-04-30
No

I upgraged to EclEmma Snapshot 2.1.2.201204281655 (per suggestion for bug 3522048), using Eclipse Indigo (w/ Java 1.6) but when I run emma, there is no output in the JUnit view, nor is code highlighted with coverage info. The tests may well be executing, as the "busy" spinner displays for a short time, but no errors or indication of the results exists - aside from an entry in the JUnit View's "Test Run History", which, upon selecting, will clear the JUnit results.

Uninstalling EclEmma and re-installing 2.1.1 will get it working again, but without the fix for bug 3509409

Bug 3522048: https://sourceforge.net/tracker/?func=detail&atid=883354&aid=3522048&group_id=177969
Bug 3509409: https://sourceforge.net/tracker/?func=detail&atid=883351&aid=3509409&group_id=177969

Discussion

  • Marc R. Hoffmann

    This is strange, I just verified with Eclipse 3.7.2 and everything works fine. Are there any errors in the Eclipse log?

     
  • Chad McHenry

    Chad McHenry - 2012-04-30

    Only after exiting eclipse did I find the error:

    Steps to reproduce:
    1. open eclipse
    2. [optional] run tests to verify all pass
    3. run tests via EclEmma
    4. wait sufficient time, but observe no results. Check log: empty
    5. exit eclipse. Check log to find the following error:

    !SESSION 2012-04-30 13:47:02.727 -----------------------------------------------
    eclipse.buildId=M20120208-0800
    java.version=1.6.0_31
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Framework arguments: -product org.eclipse.epp.package.java.product
    Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product

    !ENTRY com.mountainminds.eclemma.core 4 5013 2012-04-30 13:49:52.973
    !MESSAGE Error while dumping coverage data (code 5013).
    !STACK 0
    java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.io.DataInputStream.readByte(Unknown Source)
    at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:80)
    at com.mountainminds.eclemma.internal.core.ExecutionDataDumper.dump(ExecutionDataDumper.java:49)
    at com.mountainminds.eclemma.internal.core.launching.AgentServer.run(AgentServer.java:114)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

     
  • Marc R. Hoffmann

    This log message means that the target JVM did not come up properly or died unexpectedly. This would also explain why the JUnit view stays empty. I have no idea what is going on, especially as I can't reproduce this behavior. May I ask you to do some tests for me:

    - Can you see the target process, e.g. in the Debug view? Is it terminated?
    - Is it possible to run a minimal HelloWorld test?

    Many thanks.

     
  • Chad McHenry

    Chad McHenry - 2012-04-30

    Yes, the process is there, and is live. Terminating it manually causes the following error dialog:

    'com.mountainminds.eclemma.interna..core.launching.AgentServer' has encountered a problem.
    Error while dumping coverage data (code 5013)
    Connection reset

    Followed by the error:

    No coverage data has been collected during this coverage session.
    Please do not terminate the Java process manually from Eclipse.

    The eclipse log then shows the same error as previously reported.

    Could it be that org.jacoco.core.data.ExecutionDataReader.read() never sees the end of the data stream it's trying to read? This seems consistent, as though the stream were being closed first, when the process is terminated, causing the Error.

    I'll work on a minimal project which reproduces it.

     
  • Marc R. Hoffmann

    Unfortunately I haven't found any environment to reproduce this. Please try again with release 2.1.2.

     
  • Marc R. Hoffmann

    • status: open --> closed-works-for-me
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks