• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. How to add regression coverage to another in vManager?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 11516
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to add regression coverage to another in vManager?

ArielElia95
ArielElia95 over 3 years ago

Hello,

I'm running regressions to collect coverage, and I want to manage it with vManager and a vPlan.

Now, I'm running all kinds of tests, and each one fills ups their covergroups.

After doing a regression, I'm doing "collect runs".

Now let's say I have coverage for item_a and coverage for item_b.

item_a has 2 covergroups: item_a_cg1. item_a_cg2.

item_b has 3 covergroups: item_b_cg1, 2 and 3 likewise.

I did 1 regression that filled up item_a_cg1, item_b_cg2 and item_b_cg3 with some percentage.

Now I did another regression that filled up item_a_cg2 and item_b_cg1 and also item_b_cg3 again.

Now I want to merge these regressions so I'll the total percentage for each item, and each covergroup.

How can I do that?

I tried doing "export merge" but it didn't work as I intended.

Thanks

  • Cancel
  • StephenH
    StephenH over 3 years ago

    Simply select all the sessions (regressions) and press the metrics button, vManager will do the merge for you automatically.

    You can find help for this kind of question at https://support.cadence.com/vmanager/ - we have lots of good documentation as well as short videos covering different topics around coverage analysis, planning, ranking etc.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ArielElia95
    ArielElia95 over 3 years ago

    That's what I thought I should do, but for some reason one of the covergroups is still 0% although in one of the sessions it was filled.

    It looks like it shows only one of the sessions.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 3 years ago in reply to ArielElia95

    You might have merge conflicts that prevent the different tests from merging, e.g. if the definition of the covergroups has changed between each session.

    Check the vManager logs for any information about problems with the merge.

    Also, from the metrics window you can look at the left side bar to see the current "Context info". You might need to expand the side bar first, to see the context info button (an "i" in a circle). When the context info window pops up it should list all the sessions in the context, plus the coverage files it used (I had to redact the screenshot here but the file list is under the greyed-out area).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ArielElia95
    ArielElia95 over 3 years ago in reply to StephenH

    In the context info, the selected sessions appear there.

    I did 2 regression: the first with 10 runs, the other one with 50 runs of the same test only with a constraint around a variable.

    So there shouldn't be any conflict I think.

    Maybe I'm not collecting the runs as I should? For example, I had 4/10 tests ran, but when I do collect runs from the "scope/tempdir" directory I have only 1 run that shows as passed.

    When collecting runs from the "scope" directory, it shows 11 runs and all as passed.

    Edit:

    Ok I think I know what the problem is.

    When running a regression, the files in the "tempdir" are deleted for the new regression to finish.

    I thought that when I do "collect runs", the data is saved within the vmanager, and when I'll do again "collect runs" after another regression that I ran, the old data will be saved in the previous session, and the new data with the new "collect" I'll do, and then I can look at both of them.

    So, how can I have the old data saved?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information