Investigate [warn] Could not instrument [EmptyTree$/null]. No position.

[RadoBuransky]

I can see following warning in logs:
[warn] Could not instrument [EmptyTree$/null]. No position.

I believe that the parsing logic needs an update. Need to investigate. This happens for a Play app.

[sksamuel]

0.95.6 has better information, so the log on that version will be able to
tell me what is wrong.

On 9 January 2014 05:12, Rado Buranský [email protected] wrote:

I can see following warning in logs:
[warn] Could not instrument [EmptyTree$/null]. No position.

I believe that the parsing logic needs an update. Need to investigate.
This happens for a Play app.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5
.

[sksamuel]

Did the latest release fix this ?

[nmccready]

I am on 0.98.2 maven plugin via 0.98.4 scalac-scoverage-plugin and this error is still happening.

[ssundell]

Same here. sbt-scoverage-plugin 0.98.4 and getting the same warning. I originally thought it didn't instrument anything, but I haven't had a chance to really try and debug on what's actually happening.

For what it's worth, it's a multi-project SBT build, running on Scala 2.10 and SBT 0.13, using Build.scala instead of build.sbt, and to make matters a bit more interesting, we're forking tests. The end result is that it appears we run no statements whatsoever.

[fommil]

we're seeing this in the https://github.com/ensime/ensime-server CI runs as well.

I'm guessing its mostly harmless, since coverage is reporting sensible things, so is there a way to silence this?

[sksamuel]

There's no way to silence it at moment, but I suppose I should remove that
warning. It was basically a debug for me to find areas where I had not yet
covered the AST.

On 2 July 2014 21:58, Sam Halliday [email protected] wrote:

we're seeing this in the https://github.com/ensime/ensime-server CI runs
as well.

I'm guessing its mostly harmless, since coverage is reporting sensible
things, so is there a way to silence this?

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[agustina-biscayart-olx]

Is this fixed? I'm using the latest release and I'm getting this error.

[sksamuel]

It's not really a bug, it's a leftover. I'll remove it from the next
release.

On 26 January 2015 at 18:47, Agustina Biscayart [email protected]
wrote:

Is this fixed? I'm using the latest release and I'm getting this error.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[reid-spencer]

Still seeing this in 1.0.4 btw, with a scala Play application.

[natemurthy]

Also seeing this running sbt coverage test with Play! plugin 2.4.2 and scoverage plugin 1.1.0:

[info] [info] Beginning coverage instrumentation
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
...

[fmayer-tstllc]

I am still seeing this with sbt-scoverage 1.3.3. It's about a third of the log output when running tests.

[Chuwiey]

+1

[jorgedfbranco]

I'm still seeing this all over with 1.3.5.

[imarios]

Still see it in 1.5.0 :)

[sukumarinbox]

Hello All I am using

1. Jenkins
   Jenkins ver. 1.625.18.3 (CloudBees Jenkins Enterprise 15.11)
2. scoverage plugin:
   SbtPlugin("org.scoverage" % "sbt-scoverage" % "1.5.0")
3. sbt version
   sbt-0.13.9
4. sbt settings:
   [process_args] java_version = '1.8.0_111'
   # Executing command line:
   java
   -Xms4096m
   -Xmx4096m
   -XX:ReservedCodeCacheSize=512m
   -XX:MaxMetaspaceSize=1024m
   -jar

when i issue sbt coverage test coverageReport from jenkins
I am getting the below issue
[info] [info] Beginning coverage instrumentation
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.
[info] [warn] Could not instrument [EmptyTree$/null]. No pos.

And the same if i try to do command line (linux) i am getting coverage

Could any one help me here. Thanks in advance

[artekzet]

Which version solves this problem?