KVSTORE tests: move directories

[jeromecoutant]

Summary of changes

I am working with Windows environment and git bash.
Got build issues with kvstore tests and test name length

Impact of changes

None, same test but with a more simple name

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

Can you add also a reason for this move to the commit message?

I would even rename the directory where main.cpp test is, to shorter as it has all prefix device_key_... same as the parent, not needed , just tbd enough in that case? same for the whitebox prefix in the second test.

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[jeromecoutant]

I would even rename the directory where main.cpp test is, to shorter as it has all prefix device_key_... same as the parent, not needed , just tbd enough in that case? same for the whitebox prefix in the second test.

OK

Before PR:
storage/kvstore/direct_access_devicekey/tests/TESTS/direct_access_devicekey/direct_access_devicekey_tdb/main.cpp
storage/kvstore/securestore/tests/TESTS/securestore/securestore_whitebox/main.cpp

With this PR:
storage/kvstore/tests/TESTS/direct_access_devicekey/direct_access_devicekey_tdb/main.cpp
storage/kvstore/tests/TESTS/securestore/securestore_whitebox/main.cpp

New proposition?
storage/kvstore/tests/TESTS/direct_access_devicekey/tdb/main.cpp
storage/kvstore/tests/TESTS/securestore/whitebox/main.cpp

[jeromecoutant]

Can you add also a reason for this move to the commit message?

done

[jeromecoutant]

ping

[0xc0170]

CI started

This however just avoids the main issue ,but hopefully soon we got CMake and components and response files to battle the length.

@ARMmbed/mbed-os-core please review

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️

[evedon]

Thanks @jeromecoutant we'll watch for the test name length.

[LDong-Arm]

@jeromecoutant Hi, I wonder if your mbed-os repo is checked out in a directory that's already deep? It's said that Windows has a path length limit of 256 characters, whereas the test even before renaming had only 112 characters.

Maybe the installation path/home directory of git bash is already quite deep? (This can be even deeper for WSL.) In this case the directories above mbed-os might already take quite some characters?