Use objections in uvm phase functions? (or just tasks) in UVM (Pre-IEEE) Methodology and BCL Forum Posted March 5, 2015 · Report reply Thanks a lot. I didn't realize that an objection to ending a phase meant extending the time only. I thought the lack of an objection might mean that the phase could end anytime, even between delta cycles at the same time. (I'm not sure if delta cycle is the proper term there.) So, all functions that are called at the start of one of the uvm run phases (before any time consuming events) will be guaranteed to complete. And any uvm run phase which has no time consuming elements needs no objections. Right? (I'm not saying I have a reason for such measures. I am just checking.) thanks again for spelling it out for me Perhaps it's just me, but I don't think the uvm_users_guide_1.1.pdf is clear enough about this. "each phase" to me means "every phase". (see below) Also, I didn't read "activity" below as meaning something that consumes time. snippet from uvm_users_guide_1.1.pdf: 3.11 Managing End of Test UVM provides an objection mechanism to allow hierarchical status communication among components. There is a built-in objection for each phase, which provides a way for components and objects to synchronize their testing activity and indicate when it is safe to end the phase and, ultimately, the test. In general, the process is for a component or sequence to raise a phase objection at the beginning of an activity that must be completed before the phase stops and to drop the objection at the end of that activity. Once all of the raised objections are dropped, the phase terminates.