In reply to Mahesh K:
One of the possible cause of a test failing is wrong use of objections. There are two possible scenarios.
a) No component raises an objection. The test ends at time 0.
b) A single component forgets to drop an objection that it has raised. The test never ends (unless a timeout mechanism has been set).
In order to debug the above scenarios the +UVM_OBJECTION_TRACE is very useful.
You will see all the objection raises/drops by any component in the log.
Regarding other causes of test failures (such as connectivity failures etc) the UVM_OBJECTION_TRACE is not going to be of much help. But I would still use it to rule
out objection failures mentioned above.
Logie Ramachandran
Verikwest Systems Inc.