-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport 2.28: Record the outcome of each test case in compat.sh #7897
Backport 2.28: Record the outcome of each test case in compat.sh #7897
Conversation
Signed-off-by: Yanray Wang <[email protected]>
If the environment variable MBEDTLS_TEST_OUTCOME_FILE is set, the test outcome file records each test case in a single line with the format of PLATFORM;CONFIGURATION;compat;TEST CASE DESCRIPTION;RESULT;[CAUSE] - CONFIGURATION comes from MBEDTLS_TEST_CONFIGURATION to record configuration of each test case - PLATFORM is either set by users or calculated from test platform - RESULT is one of PASS, FAIL or SKIP. If test case fails, srv_out/cli_out follows as FAILURE CAUSE. Signed-off-by: Yanray Wang <[email protected]>
Signed-off-by: Yanray Wang <[email protected]>
@yanrayw This is the requested backport. In 2.28 mbedtls_config.h does not exist. I hope I dealt with this correctly, please let me know otherwise. |
Please remember to set labels on your PRs - see https://confluence.arm.com/pages/viewpage.action?pageId=562698953 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me except a minor issue.
Adjust where to set absolute path for MBEDTLS_TEST_OUTCOME_FILE as it's supposed to set its absolute path after all possible value assignment. Signed-off-by: Yanray Wang <[email protected]>
fa89b02
to
5659981
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for doing the backport.
LGTM, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Faithful backport, LGTM.
@lpy4105 It looks like you have just left a comment rather than submitting it as a review officially. I am not sure if @yanrayw is technically allowed to review given he authored the original PR, so could you please officially submit as a review, and then we can mark it approved. (Also, please let me know if I am wrong about this...)
|
Description
Backport of PR #7136
PR checklist
Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")
Notes for the submitter
Please refer to the contributing guidelines, especially the
checklist for PR contributors.