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
Currently, for FI experiments, we check whether the response from the device matches the expected response defined in the config file. However, for some tests, we return random data. Here, this simple check does not work and needs to be replaced by a more complex analysis. As this analysis depends on the actual test, we should add a feature to the FI scripts such that we can bypass this check and do the analysis afterwards.
The text was updated successfully, but these errors were encountered:
For some tests (e.g., that return random data) comparing the response
with an expected response does not make sense. For these tests a
manual analysis needs to be conducted. This commit detects these tests
and bypass the response comparion.
CloseslowRISC#382
Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
added a commit
to nasahlpa/ot-sca
that referenced
this issue
Dec 6, 2024
For some tests (e.g., that return random data) comparing the response
with an expected response does not make sense. For these tests a
manual analysis needs to be conducted. This commit detects these tests
and bypass the response comparion.
CloseslowRISC#382
Signed-off-by: Pascal Nasahl <[email protected]>
Currently, for FI experiments, we check whether the response from the device matches the expected response defined in the config file. However, for some tests, we return random data. Here, this simple check does not work and needs to be replaced by a more complex analysis. As this analysis depends on the actual test, we should add a feature to the FI scripts such that we can bypass this check and do the analysis afterwards.
The text was updated successfully, but these errors were encountered: