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

The error is occurring during the import of Devel::Cover which occurs before actually reading the script. Is your flow runner tool making a different cover_db unrelated to Devel::Cover for its own uses? If not, simply delete (rm -r) "/tests/cover_db" and any similar directories that appear in later errors. If so, try setting DEVEL_COVER_OPTIONS to "-db /PATH/TO/COVERAGE/DB" to specify a path that the flow runner will not be using.

You can merge multiple databases by simply mentioning all of them on the command line for cover. You can use the -write NEWDB option to write the merged database or simply merge the databases in-memory and immediately produce a report.

Replies are listed 'Best First'.
Re^4: Creating coverage big report
by ovedpo15 (Pilgrim) on Oct 03, 2019 at 23:38 UTC
    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
    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?

      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.

        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