Repository navigation
[Enhancement] The SBMR log missing should be identified as WARNING if the SBMR test is not set to true. #709
Description
@sunnywang-arm @chetan-rathore @gtossk2 for vis.
Reacted by Chetan Singh
{{ message }}
@sunnywang-arm @chetan-rathore @gtossk2 for vis.
Activity
chetan-rathore commentedon Mar 26, 2026
@anncheng-arm The SBMR is getting reported as part of recommended as currently ACS is missing option to determine if the run is for Server or not. Since for non server runs SBMR is not mandatory, it is treated as recommended suite.
ACS should have a config option for server run and based on that have final result determination.
sunnywang-arm commentedon Jul 10, 2026
@chetan-rathore
How about updating the parser to use SBSA enablement as an indicator for a server run?
In practice, it does not seem meaningful to run SBSA without also considering SBMR and BBSR. If SBSA tests are enabled, we can reasonably treat the run as targeting a physical server and include SBMR in the final result determination.
Cc @anncheng-arm
sunnywang-arm commentedon Jul 29, 2026
Just FYI, another unexpected outcome would be that a server system is reported as compliant even though some required logs (such as the BBSR and SBMR logs shown in the screenshot) are missing.