mirror of
https://gitee.com/openharmony/third_party_littlefs
synced 2024-11-23 14:59:50 +00:00
77e3078b9f
It's interesting how many ways block devices can show failed writes: 1. prog can error 2. erase can error 3. read can error after writing (ECC failure) 4. prog doesn't error but doesn't write the data correctly 5. erase doesn't error but doesn't erase correctly Can read fail without an error? Yes, though this appears the same as prog and erase failing. These weren't all simulated by testbd since I unintentionally assumed the block device could always error. Fixed by added additional bad-black behaviors to testbd. Note: This also includes a small fix where we can miss bad writes if the underlying block device contains a valid commit with the exact same size in the exact same offset. |
||
|---|---|---|
| .. | ||
| test_alloc.toml | ||
| test_attrs.toml | ||
| test_badblocks.toml | ||
| test_dirs.toml | ||
| test_entries.toml | ||
| test_exhaustion.toml | ||
| test_files.toml | ||
| test_format.toml | ||
| test_interspersed.toml | ||
| test_move.toml | ||
| test_orphans.toml | ||
| test_paths.toml | ||
| test_relocations.toml | ||
| test_seek.toml | ||
| test_truncate.toml | ||