Doing x.stop_sequences() is causing this UVM FATAL Item_done() called with no outstanding requests. Each call to item_done() must be paired with a previous call to get_next_item()

UVM
,
11

In reply to chr_sue:

Yes, they need to be stop manually, that’s how it’s been architected. I am afraid I can’t put my code here, so that’s why I showed you a general example. I will ask differently
how to make sure that the Driver is inactive before calling stop_sequences