Problems getting code coverage work in TeamCity 2.0

Hi!

We're on the bleeding edge, running TeamCity 2.0, and we've tried to get code coverage
to work. I check the Enable code coverage checkbox in the admin pages, touched a file
to get a new checkout of all our code, compile, and unit tests all runs fine, but at the
end of the result we see this:

: EMMA: Create Report (5s)
: Unable to find /opt/buildAgent/work/Agent/cc-Spring/coverage.em, cannot create EMMA report
: Publishing artifacts (<1s)
: Artifacts path coverage.ec not found
: Artifacts path coverage.em not found
: Artifacts path coverage.txt not found
: Artifacts path coverage/coverage.zip not found

Any idea what this could be?

Mats

8 comments
Comment actions Permalink

Mats,

Thank you for the report!

Seems there are problems with gathering code coverage data under Linux systems. I've filed corresponding issue into our Jira: http://www.jetbrains.net/jira/browse/TW-2427

Hope, it will be investigated and fixed soon.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Our machine is actually a Solaris box, but the error seems to be the same.

Does this mean we have to wait till TeamCity 2.0.1?

Mats

0
Comment actions Permalink

Mats,

I hope the fix will be available in the next minor released version or even earlier in one of the EAP builds. However, the issue should be investigated in detail to say for sure.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Mats,

Could you please describe the machine running TeamCity agent? Is it 64 bit? If you have several build agents, do coverage results fail on all of them?

Coverage does run on some boxes, so I try to figure out what is the difference.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

It is an Intel 32-bit Solaris box. We've ordered a Wintel box,
so we'll move the whole of TeamCity to it.

Mats

0
Comment actions Permalink

Oh, and it is only one box. Sorry.

Mats

0
Comment actions Permalink

Hi Mats,

Please make sure that if you have ANT_HOME variable defined on the Solaris box
with build agent, it points to Ant 1.6.5+ . Or simply undefine this variable before starting
TeamCity build agent.

HTH,

KIR

0
Comment actions Permalink

Mats,

We tracked down the problem that reproduced in our environment: the cause was incorrect version of the ANT used (TeamCity's works with Ant 1.6.5 and 1.7)

Could you please check what Ant version is used in your case? This can be seen from the agent's log. You can also look for ANT_HOME environment variable listed in the "Environment variables" of the agent details - if there is a value, it is used.

To use bundled Ant, please add ANT_HOME environment variable to the build configuration on the "Properties and environment variables" page and set it to "../plugins/ant".

Does it help? If not, it seems we will need more information including logs of the agent.

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.