Virtual sequence finishes and driver stops sending transactions to DUT

UVM
1

Hi,
My virtual sequence(called from the test) finishes and at the same time driver stops pushing transactions to DUT. Can one of you point me to the most reliable way to make sure that all the driver transactions are sent to DUT?

I tried several methods of raise/drop obj or timeout or adding drain time but I am missing something.

Thank you.

2

In reply to UVM_learner6:

Using a drain time is the best way to extend your simulation time after your sequences have completed. You will need to show your code so that others can provide feedback.