Page MenuHomePhabricator

NS audit logging test fails when Secure regression test is not selected
Open, LowPublic

Description

NS audit logging test fails when Secure regression test is not selected.

Running Test Suite AuditLog non-secure interface test (TFM_AUDIT_TEST_1XXX)...
> Executing 'TFM_AUDIT_TEST_1001'
  Description: 'Non Secure functional'
  Stored size different from ((56)) (Failed at D:/MCU/TF-M_Review/trusted-firmware-m/build/lib/ext/tfm_test_repo-src/test/suites/audit/non_secure/audit_ns_interface_testsuite.c:100)
  TEST FAILED!
TESTSUITE FAILED!
Number of failed tests: 1 of 1

Root cause:

In NS audit logging test, the NS test case reads out the logs filled by Secure audit logging test cases (https://git.trustedfirmware.org/TF-M/tf-m-tests.git/tree/test/suites/audit/secure/audit_s_interface_testsuite.c#n72). 

In previous build system, NS and S tests were enabled together and therefore the logs for test were always ready when NS logging test started.

In current build system, NS and S tests can be enabled independently. Therefore, NS logging test cannot find the pre-filled logs if Secure logging test is not enabled.

Action required:

It requires a discussion about how maintain the dependency between Secure test cases and Non-secure test cases. It may rely on build system or test case implementation itself.

Event Timeline

davidhuziji triaged this task as Low priority.Nov 5 2020, 3:21 AM
davidhuziji created this task.

In the realm of academia, time is a precious commodity, and the task of crafting an annotated bibliography can be daunting. This is where the phrase "write my annotated bibliography" https://domyessay.com/write-my-annotated-bibliography becomes a lifeline, offering a solution to the time-consuming process of synthesizing and annotating sources. With a simple request, students and researchers can enlist the expertise of skilled professionals to meticulously curate their bibliographies, saving valuable time and ensuring the accuracy and thoroughness of their research.