[erlang-questions] Cover compilation breaks running node

Roger Lipscombe roger@REDACTED
Mon Jun 3 16:06:29 CEST 2019

I'm attempting to use ct_run -cover (per
http://erlang.org/doc/apps/common_test/cover_chapter.html) to get
coverage information from an Erlang node.

I've got a coverspec file that looks like this:

{nodes, ['the_server@REDACTED']}.
{incl_dirs_r, ["path/to/_rel/the_server/lib"]}.
{export, "cover.coverdata"}.

...and I'm running it like this (abridged):

ct_run -cover cover.spec -erl_args -pa path/to/_rel/the_server/lib/*/ebin

After a long wait while it cover compiles 900 modules, it finally runs
my CT test, but it fails because the remote node has been screwed up.
I get a bunch of function_clause and badrecord errors and everything's
entirely broken.

The remote node finally gets stuck in a loop continually complaining
about {badarg,[{ets,update_count,[cover_internal_data_table etc...

Does anyone have a working example of getting coverage from a remote
Erlang node while running ct_run?

Potentially related: can I cover-compile the modules ahead of time,
when I build the release (I'm using relx)?

More information about the erlang-questions mailing list