Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to exclude some processes by name from coverage? #220

Closed
kannaiah opened this issue Sep 12, 2017 · 3 comments
Closed

How to exclude some processes by name from coverage? #220

kannaiah opened this issue Sep 12, 2017 · 3 comments

Comments

@kannaiah
Copy link

I have many levels of scripting on top actual test binary.
And a test binary is executed with different options by the scripts

If I can only include test process by name then I do not have to change any existing scripting for generating coverage. Otherwise I would have to handle merging of coverage reports my self.

I used --include-path but this is causing slowdown.

Thank you.

@SimonKagstrom
Copy link
Owner

SimonKagstrom commented Sep 12, 2017

Hmm.. So your scripts run kcov on some binaries which you don't want to collect coverage for?

So the name exclusion would be to simply ignore some runs? Or do I misunderstand you?

@kannaiah
Copy link
Author

kannaiah commented Sep 12, 2017

Sorry, I wasn't clear.
I was running my scripts through kcov.
I just read another ticket #177 so it might not be possible to get coverage of my tests as my top level scripts are in bash and python.

My command looks something like below
kcov ./run_my_tests.sh
and the shell script runs python script.

@SimonKagstrom
Copy link
Owner

Aha, yes, I'm afraid that isn't possible at the moment. I'm not quite sure how to implement it either, so for now I'm not investigating it further. The difficult thing is to determine what are actual Python scripts from bash (and the other way around!).

Closing as a duplicate to #177, reopen if this isn't the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants