-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix issue when TDBStore has varying erase sizes between areas. (Backport) #12653
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
In some cases, it is possible that every erase unit in area 0 has the same size, but they are still different than in area 1. Remove the flag for varying erase sizes and instead check from flash, what is the erase size of the current unit.
This has already been approved for 5.15.2. |
CI started Note: dynamic test will most likely fail, will be fixed today |
Test run: FAILEDSummary: 2 of 7 test jobs failed Failed test jobs:
|
@0xc0170 could you retrigger the CI if the dynamic memory tests are now stable? |
CI restarted |
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
I restarted tests, there were usb failures |
mmm still seeing the USB failures... |
This needs a fix to how the USB tests are run (@jamesbeyond will raise shortly) |
test restarted |
Started new CI job |
Test run: SUCCESSSummary: 9 of 9 test jobs passed |
Summary of changes
This is a backport of #12558 to
mbed-os-5.15
In some cases, it is possible that every erase unit in area 0
has the same size, but they are still different than in area 1.
Remove the flag for varying erase sizes and instead check from
flash, what is the erase size of the current unit.
Impact of changes
Migration actions required
Documentation
None
Pull request type
Test results
Reviewers
@ARMmbed/mbed-os-storage
@soleilplanet
@adbridge