You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output of dh -d is different from that of dh -d -v.
I'm wondering if it makes sense to let UEFI Debug dump test run dh -d -v instead. If UEFI Debug dump test runs dh -d -v, the dump logs can be directly re-used as UEFI shell command test results. It then becomes more convenient for platforms to automate the IR tests.
The text was updated successfully, but these errors were encountered:
Hi, according to Systemready IR test spec, when UEFI shell is tested, the following command should be run to dump the
dh
command output.dh -d -v
It seems like Systemready test scripts only run
dh -d
in UEFI Debug dump test case.(IR 2.1: https://github.com/ARM-software/arm-systemready/blob/v23.09_SR_REL2.0.0_ES_REL1.3.0_IR_REL2.1.0/common/config/debug_dump.nsh#L43
IR 3.0: https://github.com/ARM-software/arm-systemready/blob/v24.11_SR_REL3.0.0-BETA0_SR-DT_REL3.0.0-BETA0/common/uefi_scripts/debug_dump.nsh#L46)
The output of
dh -d
is different from that ofdh -d -v
.I'm wondering if it makes sense to let UEFI Debug dump test run
dh -d -v
instead. If UEFI Debug dump test runsdh -d -v
, the dump logs can be directly re-used as UEFI shell command test results. It then becomes more convenient for platforms to automate the IR tests.The text was updated successfully, but these errors were encountered: