Coverage fails, but suite runs fine!

[marchof]

To me, this looks like it might not be an issue with EclEmma, but since I'm not seeing this error except when running coverage I thought I'd start here. I'm semi-familiar with what this error means in general in Java, which makes me wonder why I'm only seeing it when running coverage.

If anyone knows a tip for tracking it down, let me know!

[marchof]

Indeed, this looks strange. Can you please check the Eclipse log for additional information or a related stack trace? The Eclipse log file is located here

<your workspace>/.metadata/.log

[lucasyvas]

I'm afraid it's quite unhelpful:

!ENTRY org.eclipse.jdt.core 4 -1 2015-08-17 13:37:22.150
!MESSAGE 'if' is not a valid Java identifier

I'm running EclEmma 2.3.2.201409141915 and Eclipse Luna (as per current project requirement)

[marchof]

We also use EclEmma on Eclipse Luna -- without any issue.

If open the Coverage launch dialog (with Coverage as...) you can select the source folders and libraries which are on scope for coverage analysis. Can you please narrow down the scope to see which source folder / library is affected? Maybe you can create a reproducer this way.

[lucasyvas]

I spent a few days pouring over it all, as it's a large code base. I'm curious to see what the root cause is, but I opted to run it in batch and merge afterwards, which worked fine surprisingly. The top level JUnit seems to make it throw a fit. A little strange, but maybe the workspace is gimped since another one of our developers could not reproduce the issue.

[marchof]

Currently exceptions stack traces of internal errors get mostly lost. The reason is usage of CoreException.getStatus() method:

http:https://help.eclipse.org/luna/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/runtime/CoreException.html#getStatus()