Skip to content
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

LittleFS test only works for specific device parameters #54726

Closed
decsny opened this issue Feb 10, 2023 · 1 comment
Closed

LittleFS test only works for specific device parameters #54726

decsny opened this issue Feb 10, 2023 · 1 comment
Assignees
Labels
area: File System area: Tests Issues related to a particular existing or missing test bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale

Comments

@decsny
Copy link
Member

decsny commented Feb 10, 2023

Describe the bug
The tests/subsys/fs/littlefs test only works for platforms with certain block sizes and counts. One can see in the clean_statvfs function that this test will check for these parameters and fail the assertions there if the device does not meet these specific requirements. If these assertions are removed, the test will most likely fail later because the device runs out of space or some other problem due to the fact that the test is written for a very specific set of parameters, and is not useful to test most platforms.

Expected behavior
Expected to be able to test littlefs on any device regardless of block size and count etc

Impact
Not easy to test LittleFS on most platforms in zephyr except with the sample

@decsny decsny added the bug The issue is a bug, or the PR is fixing a bug label Feb 10, 2023
@nordicjm nordicjm added area: File System area: Tests Issues related to a particular existing or missing test labels Feb 13, 2023
@laurenmurphyx64 laurenmurphyx64 added the priority: low Low impact/importance bug label Feb 14, 2023
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Apr 16, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: File System area: Tests Issues related to a particular existing or missing test bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

4 participants