Jump to content
Sign in to follow this  

UVM 1.2 report_summarize()

Recommended Posts

HI :

  I am aware in Accellera UVM1.2 uvm_report_server, report_summarize(), there is below uvm_info at end of the function. 

	     // Andrew  f_display(file, `UVM_STRING_QUEUE_STREAMING_PACK(q));

I would like to know the motivation of doing so. It is not backward compatible with UVM-1.1X. 

  1. we have +UVM_VERBOSITY=UVM_NONE for regression run and we do want to see the summary of test.  

  2. we customized  compose_report_message,   based on UVM_1.2. it gave me a funny output : i.e 


--- UVM Report Summary ---

** Report counts by severity
UVM_INFO :    7
UVM_ERROR :    1
UVM_FATAL :    1
** Report counts by id
[RNTST]     1
[mycfg]     1
[myenv]     6
[mytest]     1
 : reporter


Share this post

Link to post
Share on other sites
Most methods in verilog Program including the uvm_report_object are delegated to an internal instance of a
uvm_report_handler, which stores the reporting configuration and determines
whether an issued message should be displayed based on that configuration.
Then, to display a message, the report handler delegates the actual
formatting and production of messages to a central UVM Report sample.

A report consists of an id string, severity, verbosity level, and the textual
message itself. They may optionally include the filename and line number from
which the message came. If the verbosity level of a report is greater than the
configured maximum verbosity level of its report object, it is ignored.
If a report passes the verbosity filter in effect, the report's action is
determined. If the action includes output to a file, the configured file
descriptor(s) are determined.

    can be set for (in increasing priority) severity, id, and
           (severity,id) pair. They include output to the screen UVM_DISPLAY,
           whether the message counters should be incremented UVM_COUNT, and
           whether a $finish should occur UVM_EXIT.

            The following provides the default actions assigned to
                           each severity. These can be overridden by any of the set_*_action methods.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this