-
Notifications
You must be signed in to change notification settings - Fork 3k
Handle NVStore tests in a low memory environment #7746
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
Conversation
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.
Looks fine for me. Approved
@davidsaada After applying this patch, the MOTE_L152RC still hard faults for the nvstore tests:
|
@bentcooke If you could connect the board to a raas node, I may have a look at this error from remote. |
@davidsaada it is on a raas node now... address provided by email. |
65f03c9
to
8f17daa
Compare
Rebased following merge of #7670 (as both modify the NVstore tests). |
7412310
to
dbff75e
Compare
Rebased again. |
@0xc0170 @kjbracey-arm Can you please review? As the problem in MOTE_L152RC board has long been resolved. |
@0xc0170 @kjbracey-arm Would appreciate a review here, as this PR resolves a few open issues. |
Hi |
dbff75e
to
744300f
Compare
Ah yes. Sorry about that. Whole NVStore directory has moved. Rebased now. |
0a05f3c
to
2ebf9ff
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.
Tested OK with DISCO_L072
/morph build |
Build : SUCCESSBuild number : 3093 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2702 |
Test : FAILUREBuild number : 2882 |
2ebf9ff
to
999042d
Compare
Fixed test issues in problematic board. |
/morph build |
Build : SUCCESSBuild number : 3129 Triggering tests/morph test |
Test : SUCCESSBuild number : 2931 |
Exporter Build : SUCCESSBuild number : 2737 |
Description
Previous fix to NVStore tests measured how much memory is available for threads (in the multi thread tests) and lowered number of threads accordingly. This was problematic in two aspects:
Therefore, this PR simply checks each and every memory allocation in these tests (using std::nothrow), and skips the remainder of the test (without failing it) if memory can't be allocated.
Pull request type