Skip to content

CI tests failing for filesystem tests on targets with 32K RAM #6008

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.

Sign up for GitHub

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

Jump to bottom
Closed
ashok-rao opened this issue Feb 4, 2018 · 4 comments
Closed

CI tests failing for filesystem tests on targets with 32K RAM #6008

ashok-rao opened this issue Feb 4, 2018 · 4 comments
Labels
type: bug

Comments

@ashok-rao
Copy link
Contributor

Description

  • Type: Enhancement | Question
  • Related PR: #5975
  • Priority: Major

Enhancement

Some of the targets with 32K RAM seems to be failing the heap block device tests

Suggested enhancement
Can the tests be modified to use less heap on resource constrained devices?

Pros
Useful for many smaller targets with limited RAM.

Question

How to?
Is there an option to include something like "special, low memory" tests that could may be selected based on a macro (similar to that being done for SD driver tests now) and built / ran only for a few selected targets?
@ashok-rao ashok-rao mentioned this issue Feb 4, 2018
Merged
2 tasks
@ashok-rao
Copy link
Contributor Author

ashok-rao commented Feb 4, 2018 •
edited by adbridge
Loading

@geky @theotherjimmy @cmonr @0xc0170 .. this issue is for tracking the specific test changes made for xDOT as part of #5975 ..
[Mirrored to Jira]

@geky geky mentioned this issue Feb 13, 2018
Merged
@bentcooke bentcooke mentioned this issue Jul 17, 2018
Merged
@cmonr
Copy link
Contributor

cmonr commented Jul 18, 2018 •
edited by adbridge
Loading

Is there an option to include something like "special, low memory" tests that could may be selected based on a macro (similar to that being done for SD driver tests now) and built / ran only for a few selected targets?

This sounds like something that @ARMmbed/mbed-os-storage just brought in.
[Mirrored to Jira]

@davidsaada
Copy link
Contributor

davidsaada commented Jul 18, 2018 •
edited by adbridge
Loading

This sounds like something that @ARMmbed/mbed-os-storage just brought in.

Indeed. #7465 handles it.
[Mirrored to Jira]

@cmonr cmonr mentioned this issue Jul 18, 2018
Merged
@ARMmbed ARMmbed deleted a comment from ciarmcom Oct 2, 2018
@adbridge
Copy link
Contributor

adbridge commented Oct 4, 2018

Internal Jira reference: https://jira.arm.com/browse/IOTSTOR-454

@ciarmcom ciarmcom closed this as completed Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@cmonr @0xc0170 @adbridge @ciarmcom @ashok-rao @davidsaada