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

Merge multiple coverge reports #51

Open
Divya2030 opened this issue Dec 29, 2020 · 4 comments
Open

Merge multiple coverge reports #51

Divya2030 opened this issue Dec 29, 2020 · 4 comments

Comments

@Divya2030
Copy link

Hi,
i have generated multiple coverage xml files using vsc.write_coverage_db("cov.xml")
. How to merge multiple xml files. is there any method to merge multiple xml files?

@edcote
Copy link
Contributor

edcote commented Apr 23, 2021

I don't know if this is supported by pyvsc.

Maybe https://github.com/amiq-consulting/fc4sc/tree/master/tools/coverage_merge

.... would work for you?

If you have access to a VCS license, you can convert to .vdb format using:

Usage: covimport -readucis ucis.xml -dbname snps.vdb [-mapfile map.file] [-default_bin_as_user] [-help]

@rbarzic
Copy link

rbarzic commented Nov 9, 2021

I've tried the tools/coverage_merge/merge.py utility from https://github.com/amiq-consulting/fc4sc but it does seem to work with UCIS files generated by pyvsc, apparently because the xml files do not include range information for coverpoints.

merge.py around line 158

def merge_bin_hits(self, bin, binMergeElement, parent_query):
        """ Sum the bin ranges' hit counts """
        # merge hits for bins which are present in both the parsed DB and mergeDBtree
        totalhits = 0
        for range in self.findall_ucis_children(bin, "range"):

Any idea on how to add this information to the UCIS files generated by pyvsc ?

@mballance
Copy link
Member

Clearly this has taken a bit of lower priority, given that I (and others that I know) are taking the pyVSC coverage data directly into commercial-EDA flows for manipulation. Let me invest a bit more time here...

@rbarzic
Copy link

rbarzic commented Nov 9, 2021

Thank you Matthew. Our team is trying to do the exact opposite, i.e. not relying on any commercial tool for the functionnal coverage. As we are using cocotb with multiple tests spread over a few files, merging of coverage data is critical for us

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

4 participants