PRIM_ALERT Simulation Results

Friday November 28 2025 17:08:43 UTC

GitHub Revision: 1ac1583

Branch: master

Testplan

Simulator: VCS

Test Results

Stage	Name	Tests	Max Job Runtime	Simulated Time	Passing	Total	Pass Rate
V1	prim_alert_request_test	prim_async_fatal_alert	0.530s	31.037us	14	20	70.00
		prim_async_alert	0.500s	10.896us	20	20	100.00
		prim_sync_fatal_alert	0.500s	25.294us	20	20	100.00
		prim_sync_alert	0.490s	9.867us	20	20	100.00
V1	prim_alert_test	prim_async_fatal_alert	0.530s	31.037us	14	20	70.00
		prim_async_alert	0.500s	10.896us	20	20	100.00
		prim_sync_fatal_alert	0.500s	25.294us	20	20	100.00
		prim_sync_alert	0.490s	9.867us	20	20	100.00
V1	prim_alert_ping_request_test	prim_async_fatal_alert	0.530s	31.037us	14	20	70.00
		prim_async_alert	0.500s	10.896us	20	20	100.00
		prim_sync_fatal_alert	0.500s	25.294us	20	20	100.00
		prim_sync_alert	0.490s	9.867us	20	20	100.00
V1	prim_alert_integrity_errors_test	prim_async_fatal_alert	0.530s	31.037us	14	20	70.00
		prim_async_alert	0.500s	10.896us	20	20	100.00
		prim_sync_fatal_alert	0.500s	25.294us	20	20	100.00
		prim_sync_alert	0.490s	9.867us	20	20	100.00
V1		TOTAL			74	80	92.50
V2	prim_alert_init_trigger_test	prim_async_fatal_alert	0.530s	31.037us	14	20	70.00
		prim_async_alert	0.500s	10.896us	20	20	100.00
		prim_sync_fatal_alert	0.500s	25.294us	20	20	100.00
		prim_sync_alert	0.490s	9.867us	20	20	100.00
	Unmapped tests	prim_async_fatal_alert_with_3_cycles_skew	0.520s	30.659us	19	20	95.00
		TOTAL			93	100	93.00

Coverage Results

Coverage Dashboard

SCORE	LINE	COND	TOGGLE	FSM	BRANCH	ASSERT
95.19	100.00	100.00	100.00	89.29	95.83	86.05

Failure Buckets

• Offending 'ping_ok_o' has 3 failures:

  • Test prim_async_fatal_alert has 2 failures.

    • 1.prim_async_fatal_alert.106752418485724191280811656503298049923723786778827676314767592115906416857448
      Line 97, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/1.prim_async_fatal_alert/latest/run.log

            Offending 'ping_ok_o'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_receiver.sv(312) @ 29886000: reporter [ASSERT FAILED] PingResponse1_A
        Starting assertion attempts at time 29936435ps: level = 0 arg = i_alert_receiver.PingDiffOk_A (from inst prim_alert_tb (src/lowrisc_dv_prim_alert_sim_0.1/tb/prim_alert_tb.sv:254))
        [prim_alert_seq] Ping signal integrity error sequence finished!
      

    • 15.prim_async_fatal_alert.56485705343387376232709035213515178586976472986842029478827055672555805363596
      Line 97, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/15.prim_async_fatal_alert/latest/run.log

            Offending 'ping_ok_o'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_receiver.sv(312) @ 29121000: reporter [ASSERT FAILED] PingResponse1_A
        Starting assertion attempts at time 29161332ps: level = 0 arg = i_alert_receiver.PingDiffOk_A (from inst prim_alert_tb (src/lowrisc_dv_prim_alert_sim_0.1/tb/prim_alert_tb.sv:254))
        [prim_alert_seq] Ping signal integrity error sequence finished!
      

  • Test prim_async_fatal_alert_with_3_cycles_skew has 1 failures.

    • 7.prim_async_fatal_alert_with_3_cycles_skew.110020685895457953071355579646991740017386473232872165264499714146909862050322
      Line 97, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/7.prim_async_fatal_alert_with_3_cycles_skew/latest/run.log

            Offending 'ping_ok_o'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_receiver.sv(312) @ 31271000: reporter [ASSERT FAILED] PingResponse1_A
        Starting assertion attempts at time 31291153ps: level = 0 arg = i_alert_receiver.PingDiffOk_A (from inst prim_alert_tb (src/lowrisc_dv_prim_alert_sim_0.1/tb/prim_alert_tb.sv:254))
        [prim_alert_seq] Ping signal integrity error sequence finished!
      

• Offending 'alert_o' has 3 failures:

  • Test prim_async_fatal_alert has 3 failures.

    • 3.prim_async_fatal_alert.45738739386141808305296000055075456813957985491852763801219150162483629860068
      Line 97, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/3.prim_async_fatal_alert/latest/run.log

            Offending 'alert_o'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_receiver.sv(320) @ 28955000: reporter [ASSERT FAILED] Alert_A
        Starting assertion attempts at time 29034820ps: level = 0 arg = i_alert_receiver.PingDiffOk_A (from inst prim_alert_tb (src/lowrisc_dv_prim_alert_sim_0.1/tb/prim_alert_tb.sv:254))
        [prim_alert_seq] Ping signal integrity error sequence finished!
      

    • 5.prim_async_fatal_alert.48519053690683508595884445415036202069101807530039843451330643880088460463346
      Line 97, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/5.prim_async_fatal_alert/latest/run.log

            Offending 'alert_o'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_receiver.sv(320) @ 29086000: reporter [ASSERT FAILED] Alert_A
        Starting assertion attempts at time 29145720ps: level = 0 arg = i_alert_receiver.PingDiffOk_A (from inst prim_alert_tb (src/lowrisc_dv_prim_alert_sim_0.1/tb/prim_alert_tb.sv:254))
        [prim_alert_seq] Ping signal integrity error sequence finished!
      

    • ... and 1 more failures.

• Offending '$rose(alert_tx_o.alert_p)' has 1 failures:

  • Test prim_async_fatal_alert has 1 failures.

    • 13.prim_async_fatal_alert.42175283772641390625544417595456546614642878685660256976241648295102468174059
      Line 83, in log /nightly/current_run/scratch/master/prim_alert-sim-vcs/13.prim_async_fatal_alert/latest/run.log

            Offending '$rose(alert_tx_o.alert_p)'
        UVM_ERROR src/lowrisc_prim_alert_0/rtl/prim_alert_sender.sv(334) @ 26497000: reporter [ASSERT FAILED] PingHs_A
        [prim_alert_seq] Ping request sequence[0] finished!
        [prim_alert_seq] Ping request sequence[1] finished!
        [prim_alert_seq] Ping request sequence[2] finished!