-
Notifications
You must be signed in to change notification settings - Fork 3k
Limiting the thread stack for parallel threads test #3484
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
Limiting the thread stack for parallel threads test #3484
Conversation
Previously, the RTOS threads test was conditionally change the thread stack size for all test cases based on the target. Now, it uses the default stack size for all targets when threads are created serially, and uses a 512 byte stack for the threads that are created in parallel.
/morph test |
+1 for technical terminology |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Now we need to do this with the rest of the codebase 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, and it apparently didn't break on any platform.
I fixed it in features_cmsis5 branch, but using default stack size (4k by default but can be change per platform). |
@VeliMattiLahtela Please restart CI ? looks like it;s not progressing. |
|
Needs to be green :-) I restarted the job |
Description
Previously, the RTOS threads test would conditionally change the thread stack size for all test cases based on the target. Now, it uses the default stack size for all targets when threads are created serially, and uses a 512 byte stack for the threads that are created in parallel.
Also, this should remove the last failing test case on the ARCH_PRO platform :)
Status
READY
Migrations
If this PR changes any APIs or behaviors, give a short description of what API users should do when this PR is merged.
NO
Todos
Notes to Reviewers
Requesting reviews by @c1728p9 and @geky since they are familiar with all things RTOS and stack-sizey (yes that's a technical term)
Also requesting a review by @pan- as this may affect some of the BLE platforms/constrained mbeds.