limit coverage inside souce code directory.

[linux-test-project]

limit coverage inside souce code directory.

[calidion]

@totoc1001 @myrgy

you can check code here.

https://github.com/vigcoin/coin

the error info can be found here:

https://circleci.com/gh/vigcoin/coin/43

[oberpar]

You need to add a pattern for the "tests" directory to the lcov --remove call.

[oberpar]

You're using this command line:

lcov --remove temp.info "/usr/include/*" "./include/*" "./tests/*"

Note that lcov does not expand the "." in this command line to mean the current working directory. I would assume that the paths in the coverage data file are in absolute form, so that the relative "." will not match anything (since there's no absolute directory named ".").

Try specifying the path in absolute form. Something like the following should remove all occurrences of tests and include sub-directories (which may be more than you intended).

lcov --remove temp.info "/usr/include/*" "*/include/*" "*/tests/*"

[myrgy]

Hi @calidion ,

you can remove that files using lcov --remove coverage.info excludes_pattern

[calidion]

@myrgy
it seems not working.
I use

lcov --remove coverage.info '/usr/include/*' './include/*'

but /usr/include still in the generated html.

[myrgy]

>>lcov --remove coverage.info '/usr/include/*' './include/*'  --output-file coverage2.info
>>genhtml coverage2.info

Im my case I'm creating a new filtered file. But according to lcov manual it should work with original file as well. I would recommend you play with generated DB using command line.

  -r tracefile pattern
       --remove tracefile pattern
              Remove data from tracefile.

              Use this switch if you want to remove coverage data for  a  par‐
              ticular  set  of files from a tracefile. Additional command line
              parameters will be interpreted as shell wildcard patterns  (note
              that  they  may  need  to  be escaped accordingly to prevent the
              shell from expanding them first).  Every file entry in tracefile
              which matches at least one of those patterns will be removed.

              The  result of the remove operation will be written to stdout or
              the tracefile specified with -o.

              Only one of  -z, -c, -a, -e, -r, -l, --diff or --summary may  be
              specified at a time.

It should work since I have exactly the same set up in my projects.

[calidion]

not working.

cmd:

lcov --remove temp.info '/usr/include/*' './include/*' --output-file coverage.info

result:

Writing data to coverage.info
lcov: ERROR: cannot write to coverage.info!

[totoc1001]

Hello, not sure the * is interpreted when using simple quotes. Whether use double quotes or lcov --remove temp.info /usr/include/\* ./include/\* --output-file coverage.info this is the way I generally use it Thomas Le mer. 17 oct. 2018 à 14:54, Eric <[email protected]> a écrit :

…

not working. cmd: lcov --remove temp.info '/usr/include/*' './include/*' --output-file coverage.info result: Writing data to coverage.info lcov: ERROR: cannot write to coverage.info! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEhNOpixFt11R2iwubGpACn6ZLQVKUF2ks5ulyiRgaJpZM4XjQqU> .

[calidion]

thanks.

I solved by double quotes and redirection.

lcov --remove temp.info "/usr/include/*" "./include/*" > coverage.info

[myrgy]

you may use --output-file instead of redirection.

[calidion]

--output-file seems not working.

[calidion]

confirmed.

> lcov --remove temp.info "/usr/include/*" "./include/*" --output-file coverage.info
Deleted 289 files
Writing data to coverage.info
lcov: ERROR: cannot write to coverage.info!

[myrgy]

Just in case - does this file exist? In my script I remove all files after coverage generation.

[calidion]

I have tested this case. Have no relevance.

[myrgy]

Unfortunately I have no idea why it doesn't work for you.
Try to study lcov manual pages.
Seems like you call is correct:

       lcov -r|--remove tracefile pattern
            [-o|--output-file tracefile] [--checksum] [--no-checksum]
            [-q|--quiet] [--config-file config-file] [--rc keyword=value]

so issue might be related to wrong working dir and some restriction issues.
Looks like --output-file works fine for @totoc1001. So I assume that you have some local issue.

[calidion]

@myrgy

I don't know why.
the output temp.info is ok.

[myrgy]

I checked my script - we are using --quiet flag. and in general that's all difference.

COMMAND ${LCOV_PATH} --quiet --remove ${Coverage_NAME}.info ${Coverage_EXCLUDES} --output-file ${Coverage_NAME}.info.cleaned

[totoc1001]

how do you generate you ${Coverage_NAME}.info file? do you have errors when generating this file? If for instance do something like: lcov xx -d . -c -o ${Coverage_NAME}.info &>/dev/null, then your info file will be create but it might be corrupted and because of the log trashing, you will not know it did not work well. check the way you generated your info file. If you have errors, rather than trashing the output, use --ignore-errors option Le jeu. 18 oct. 2018 à 10:10, Alex Dalshov <[email protected]> a écrit :

…

I checked my script - we are using --quiet flag. and in general that's all difference. COMMAND ${LCOV_PATH} --quiet --remove ${Coverage_NAME}.info ${Coverage_EXCLUDES} --output-file ${Coverage_NAME}.info.cleaned — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEhNOjQZaRcCbe_VH1sOT2bh-624-mrpks5umDeDgaJpZM4XjQqU> .

[myrgy]

it's sequenced with other lcov command as a cmake custom target. As a result if lcov fails - I'll notice that, otherwise it should work.

[totoc1001]

I'm not sure, if you don't check the logs you don't know it fails, you will have an info file generated anyway... the info file is created as soon as the process starts. I've had the same issue before ignoring the error... Maybe it's linked :) Le jeu. 18 oct. 2018 à 10:53, Alex Dalshov <[email protected]> a écrit :

…

it's sequenced with other lcov command as a cmake custom target. As a result if lcov fails - I'll notice that, otherwise it should work. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEhNOhfpgnMH5G5yOPVfM1bdbAdM18k3ks5umEGBgaJpZM4XjQqU> .

[myrgy]

Thank you @totoc1001. I'll take a look or at least will disable --quiet.

[totoc1001]

don't know if it's normal but you still have 'simple quotes #!/bin/bash -eo pipefail cd build && lcov --capture --directory src --output-file temp.info && lcov --remove temp.info --output-file '/usr/include/*' './include/*' coverage.info && lcov --list coverage.info Le jeu. 18 oct. 2018 à 11:17, Eric <[email protected]> a écrit :

…

@totoc1001 <https://github.com/totoc1001> @myrgy <https://github.com/myrgy> you can check code here. https://github.com/vigcoin/coin the error info can be found here: https://circleci.com/gh/vigcoin/coin/43 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEhNOrZou4mXObpXvA1tSco1qdjk_YGuks5umEdFgaJpZM4XjQqU> .

[calidion]

try

./build-debug.sh

[calidion]

@myrgy @totoc1001

https://codecov.io/gh/vigcoin/coin

totally confused:
tests folder is still included

[calidion]

@oberpar still not working.

[calidion]

@oberpar
Thank you very much.
That's what exactly i want

[calidion]

It works on mac os too：）

[calidion]

LCOV - coverage.info.pdf