Correct way to clean up UVM objects

[sjalloq]

I've been using the register model I created and having now added more tests to a single file, I noticed I'm getting warnings that more than one uvm_reg_block have been instanced with the same name.

Am I supposed to be cleaning up each test somehow? Is there a particular helper method I should call?

Cheers.

[tpoikela]

Unfortunately the original UVM did not support this kind of use case. It is always one test per simulator run. The issue is that UVM creates a global object of type UVMRoot outside user code, which is needed to execute your UVMTest and create the component hierarchy etc. This is something that has to be implemented. I have not estimated how much effort this would require. Fixing your issue with uvm_reg_block is part of the solution, and that could be probably fixed with small effort. Is this something that is currently blocking your work?

…

On Tue, Feb 16, 2021, 23:29 Shareef Jalloq ***@***.***> wrote: I've been using the register model I created and having now added more tests to a single file, I noticed I'm getting warnings that more than one uvm_reg_block have been instanced with the same name. Am I supposed to be cleaning up each test somehow? Is there a particular helper method I should call? Cheers. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACG7SW2CTIGWO2ZFIZZ2Q73S7LPS5ANCNFSM4XXFR33Q> .

[sjalloq]

Thanks for the info. No, it's not blocking me as I can simply keep to a single test per file. I just wasn't sure I was using everything correctly.