[test-triage] aes_csr_aliasing failed with a specific seed

nbdd0121 commented 1 month ago

Hierarchy of regression failure

Block level

Failure Description

UVM_FATAL (csr_utils_pkg.sv:577) [csr_utils::csr_spinwait] timeout aes_reg_block.status.output_valid (addr=) == has 1 failures:

Test aes_csr_aliasing has 1 failures.

    3.aes_csr_aliasing.84105785674347362896286000055267534643521993528206053114351133552424673505349
    Line 286, in log /container/opentitan-public/scratch/os_regression/aes_masked-sim-xcelium/3.aes_csr_aliasing/latest/run.log

      UVM_FATAL @ 10076153718 ps: (csr_utils_pkg.sv:577) [csr_utils::csr_spinwait] timeout aes_reg_block.status.output_valid (addr=0x7de41e84) == 0x0
      UVM_INFO @ 10076153718 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
      --- UVM Report catcher Summary ---

Steps to Reproduce

GitHub Revision: 01a208901a5b8c29dc74f8a500b64b6b2cb5cf4c
dvsim invocation command to reproduce the failure, inclusive of build and run seeds: util/dvsim/dvsim.py hw/ip/aes/dv/aes_masked_sim_cfg.hjson -i aes_csr_aliasing --build-seed 50418669159766293903157726892781832882154091083197082086235277423705989875584 --seeds 84105785674347362896286000055267534643521993528206053114351133552424673505349

This is not a regression, but a specific seed that triggers the failure.

Tests with similar or related failures

No response

hayleynewton commented 4 weeks ago

aes_csr_aliasing - 100%

vogelpi commented 2 weeks ago

This is an automated CSR test and there was one single failure within the last 2 months. We have higher priority things to investigate right now. I am moving this to M7 as part of V3.

lowRISC / opentitan