.. include:: ../../../../shared/links.rst .. include:: ../shared/include.rst .. _understanding-xbtest-messages: ########################################################################## Understanding xbtest messages ########################################################################## The |Application software| outputs messages into log files. Each message is generated with the format `` :: :: :: ``. The following table describes these message fields, separated by "``::``". .. table:: Message fields +----------------+----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Example | Description | +================+==================================+=========================================================================================================================================================================================================+ | ```` | ``INFO`` | Possible severities are: | | | | | | | | * ``INFO``: General information about the progress of a test; for example, the start of a particular step of the test sequence. | | | | * ``STATUS``: Message showing intermediate progress of a test; for example, measurements. | | | | * ``WARNING``: Message that does not alter the progress of the test. User action might be taken or might be reserved. | | | | * ``CRIT_WARN``: Message that does alter the progress or the results of the test. User action is strongly recommended. | | | | * ``PASS``: Message returned in the case of successful check. | | | | * ``ERROR``: Message returned in the case of failed check. This does not interrupt any test cases or tests. | | | | * ``FAILURE``: The only message level which aborts all test cases/tests. For example, in cases of: | | | | | | | | * SW/HW incompatibility. | | | | * Test JSON file typo or wrong settings/members. | | | | * User interruption: ``CTRL+C``. | | | | * Another interrupt: for example, card reset. | | | | | +----------------+----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | ```` | ``GEN_039`` | Unique identifier for a message. | | | | The ID is formed as follows: ``_``, where: | | | | | | | | * ````: One string as a 3-letter code which identifies the type of the message: | | | | | | | | * ``GEN``: (general) message not specific to any test case. | | | | * ``ITF``: (interface) message related to device interface (for example OpenCL) and Test JSON file. | | | | * ``JPR``: JSON file parser. | | | | * ``MGT``: (management) control and safety features. | | | | * ``CMN``: (common) used by different test cases. | | | | * ``VER``: |Verify| test case specific. | | | | * ``DMA``: |DMA| test case specific. | | | | * ``P2P``: |P2P CARD| and |P2P NVME| test cases specific. | | | | * ``MEM``: |Memory| test case specific. | | | | * ``PWR``: |Power| test case specific. | | | | * ``ETH``: |GT MAC|, |GT PRBS| and |GT LPBK| test cases specific. | | | | | | | | * ````: One number per type. This is a unique 3-digit number identifying the message. | | | | | +----------------+----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | ```` | ``GENERAL`` | Identifier of the message originator. | | | | In most case it is composed by a single level ``
``, but it can also be composed by different levels: | | | | ``
:: <2nd header>`` or even ``
:: <2nd header> :: <3rd header>``: | | | | | | | | * ``
``: Originator. For example, ``POWER`` messages originate from the |Power| test case. | | | | * ``<2nd header>``: This second header is used to distinguish each individual message when multiple test cases of same type can run in parallel. For example: | | | | | | | | * **|Memory| test cases**: Multiple memory types identified by ````, for example ``HBM``, ``DDR``. | | | | * **|GT MAC| test cases**: Multiple GT lanes identified by ``Lane[]`` with ```` the index of the lane. | | | | | | | | * ``<3rd header>``: This third header is used in |Memory| test case to distinguish each individual message when multiple memory of same type can run in parallel. | | | | For example: | | | | | | | | * **DDR memory type**: ```` is used, for example ``DDR[0]``, ``DDR[1]``. | | | | | +----------------+----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | ```` | ``Start of session at: