in reply to Re^3: Creating coverage big report
in thread Creating coverage big report

You were right. I opened the GUI second time and then it failed.
Another error I'm having is: 
/tools/bin/check_status_file.pl -f steps
malformed JSON string, neither array, object, number, string or atom, 
+at character offset 0 (before "=\x{f3}rl\x{4}\x{0}(...") at /usr/pkgs
+/perl/5.14.1/lib64/module/default/x86_64-linux/Devel/Cover/DB/IO/JSON
+.pm line 33
BEGIN failed--compilation aborted at /tools/bin/check_status_file.pl l
+ine 2

[download]
Do you have idea why I'm having? Also, can the coverage module get the a makefile with proper structure of the scripts I want to get usage from?

Replies are listed 'Best First'.
Re^5: Creating coverage big report
by jcb (Parson) on Oct 03, 2019 at 23:49 UTC

    You have multiple versions of perl installed, with different sets of modules available. (Your 5.26 has Sereal but your 5.14 does not.) This is causing Devel::Cover to try to use different database formats for different runs, which of course are incompatible. Try setting the environment variable DEVEL_COVER_DB_FORMAT to either "JSON" or "Storable" to force a consistent database format.

[reply]
[d/l]
      Thank you for your help. I set the env to JSON but I still have the same error.
      Is it possible to make the coverage module pass PERL5OPT only to spescific scripts? That way, the perl scripts of flow runner tool will not be reflected by it
[reply]

        After changing the format, you will have to delete the old database.

        And no, the coverage module is being loaded by setting PERL5OPT so you will need to either filter those from the report (as explained in the manpage for cover) or just ignore them.

[reply]

In Section Seekers of Perl Wisdom