Prevent stack overflow from general_block_device test.

[korjaa]

This test was failing randomly on NUCLEO_F412ZG using SDCard (https://jira.arm.com/browse/IOTSTOR-828).

Description

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

Release Notes

[ciarmcom]

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

[korjaa]

Related ticket https://jira.arm.com/browse/IOTSTOR-828

[cmonr]

https://jira.arm.com/browse/IOTSTOR-828?focusedCommentId=3981373

[cmonr]

CI started.

[0xc0170]

@korjaa Why is this not targeting master but release branch?

[davidsaada]

We have modified this test to address these issues. Does it still happen in the latest master?
Increasing stack size will hurt boards having low memory. I don't think this change is required.

[mbed-ci]

Test run: FAILED

Summary: 1 of 4 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test

[korjaa]

@0xc0170 The tests have changed in the master branch to a shorter version (only one block operation per thread if I didn't read the log wrong) and I was not able to reproduce the issue. The block operations need to be done several times in multiple threads for the issue to show up. I feel the new tests are so short that they usually always pass.

[adbridge]

@korjaa Why is this not targeting master but release branch?

@korjaa We don't actually accept PRs directly to a release branch which is what @0xc0170 was trying to say...Please re-direct this to master and fix any issues accordingly.

[korjaa]

This PR is not valid against master as the test flow has changed in the master. However, I do still think this would useful for anyone using 5.12.x. But if patches are not accepted to releases, I'm not sure how a change like this can go in.

[0xc0170]

Based on the feedback above, this can be closed. It was addressed on master, should not be present on release branch neither.