-
Notifications
You must be signed in to change notification settings - Fork 3k
enable MOTE_L152 for OS5 #7534
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
enable MOTE_L152 for OS5 #7534
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.
Gonna ask that the tabs be replaced with spaces.
Otherwise, looks good and should be able to start CI.
@ARMmbed/mbed-os-storage Thoughts on possible rememdies for the NVstore and IAR filesystem issues? @bentcooke Mind mentioning the issue number here? |
96c309e
to
a31b31d
Compare
@cmonr tabs removed! What issue are you referring to? |
@bentcooke I was asking about the issues referenced in the PR description. |
@bentcooke Thanks. For reference though, this will need to pass all tests before it can be brought in. |
@bentcooke In reference to #7557 (comment), would you mind making a comment here once that PR is ready so we can track the dependency? |
@bentcooke This is fine, since they're seperate commits. @ARMmbed/mbed-os-storage @ARMmbed/mbed-os-hal Could y'all take a look at the small test changes? |
@cmonr How can we get this moving again? |
@bentcooke Still waiting on @mbed-os-hal and @ARMmbed/mbed-os-storage to take a look at the test changes. I recall there being some lengthy discussion about the test timings, so I want to get their input on the chance. In the meanwhile, I think we can start CI since enabling Mbed OS 5 might bring up some issues to correct in the meanwhile. /morph build |
@davidsaada is there a better way to run these tests? |
@@ -23,6 +23,11 @@ | |||
|
|||
using namespace utest::v1; | |||
|
|||
// TODO HACK, replace with available ram/heap property | |||
#if defined(TARGET_MTB_MTS_XDOT) || defined(TARGET_MOTE_L152RC) |
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.
Excluding specific boards is probably not the best way to handle these failures.
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.
That is correct, TODO HACK shall be removed
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.
I agree that this is not ideal, but I was following precedent set here:
dcd0e6b#diff-4e5d26193a7c8cf8e05e95d7775dcf84
@dannybenor et al. Excluding specific platforms from tests is probably not the best way to solve these problems. |
Followed up on #7746 |
@davidsaada @bentcooke I'm not sure I follow the latest comments. Has work migrated to another PR? Is this one good to go? |
Not exactly. Wasn't fond of some the changes here, specifically all the ones excluding this platform from failing tests. The failing BD tests were fixed in other PRs. The NVStore test, however, keeps failing on hard fault, something which needs to be debugged. |
@bentcooke
|
4ad2e19
to
c075a5e
Compare
c075a5e
to
42a49a5
Compare
@davidsaada The fork has been rebased, commit omitting target removed and retested. It appears that all tests are now passing after the rebase and applying the fix from #7746. Thanks for the help with this one! I have updated the top comment in this thread with the new logs and comments. |
@davidsaada Please review again |
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 great now. Thanks.
/morph build |
Build : SUCCESSBuild number : 2895 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2520 |
Test : SUCCESSBuild number : 2646 |
Description
Enabling OS5 support for the MOTE_L152RC target. This supersedes the now closed #6250.
Pull request type
Test logs from mbed-os v5.9.2:
MOTE_L152RC_GCC_20180716-163839.log
MOTE_L152RC_IAR_20180717-111451.log
MOTE_L152RC_ARM_20180717-111451.log
NVStore
test failures appear to be heap related (32K RAM) and similar to comments on #7127. Needs further investigation.fixed! Depends on #7746IAR Filesystem
test failures are also likely due to lack of heap and this target should have these tests disabled. Issue #6008.fixed with rebase.lpticker test
failures being reported in separate issue.fixed with commit "Increase max func exec time to allow slower sys clock" in this PR@dudmuck
Updated logs showing all previously failing tests now passing:
MOTE_L152RC_ARM_20180822-111451.log
MOTE_L152RC_GCC_20180822-163839.log
MOTE_L152RC_IAR_20180822-111451.log
Dependent PR: #7746