analyze_outcomes/all.sh: add reference component and entry for coverage comparison

Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>
This commit is contained in:
Valerio Setti 2023-12-14 18:04:04 +01:00
parent efdb8261b9
commit 52ab8fa565
2 changed files with 30 additions and 0 deletions

View file

@ -1159,6 +1159,19 @@ component_test_default_cmake_gcc_asan_new_bignum () {
tests/context-info.sh
}
# This is a common component testing the full config. Its purpose is to be used
# as the "reference" for driver's acceleration tests below when possible (this
# not always the case because some reference test require extra configuration
# in addition to the default one)
component_test_full_common_reference () {
msg "build: full config (common reference)"
helper_libtestdriver1_adjust_config "full"
make
msg "test: full config (common reference)"
make test
}
component_test_full_cmake_gcc_asan () {
msg "build: full config, cmake, gcc, ASan"
scripts/config.py full

View file

@ -533,6 +533,23 @@ KNOWN_TASKS = {
],
}
}
},
'analyze_block_cipher_dispatch': {
'test_function': do_analyze_driver_vs_reference,
'args': {
'component_ref': 'test_full_common_reference',
'component_driver': 'test_full_block_cipher_psa_dispatch',
'ignored_suites': [
],
'ignored_tests': {
'test_suite_platform': [
# Incompatible with sanitizers (e.g. ASan). If the driver
# component uses a sanitizer but the reference component
# doesn't, we have a PASS vs SKIP mismatch.
'Check mbedtls_calloc overallocation',
],
}
}
}
}