-
Notifications
You must be signed in to change notification settings - Fork 674
ostest: add kconfig to set priority #3330
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
Open
zzby0
wants to merge
4
commits into
apache:master
Choose a base branch
from
zzby0:ostest
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+99
−99
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xiaoxiang781216
previously approved these changes
Jan 14, 2026
Contributor
|
@zzby0 please fix: |
cederom
reviewed
Jan 14, 2026
testing/ostest/mqueue.c
Outdated
| } | ||
|
|
||
| sparam.sched_priority = (prio_min + prio_mid) / 2; | ||
| sparam.sched_priority = PRIORITY - 10; |
Contributor
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.
what if someone sets priority <= 10 for any reason? shouldn't we have a check here?
Author
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.
thanks for review :) i have added check here
e9e4b71 to
f219ca2
Compare
ostest may fail because some other task with higher priority are running, this change we use ostest priority for testcases, so that we can easily set testcase priority. Signed-off-by: yangao1 <[email protected]>
ostest sometimes fail because other threads with higher priority are running, we add ostest priority kconfig, so that we can increase ostest priority easier. Signed-off-by: yangao1 <[email protected]>
fix spelling error reported by codespellrc. Signed-off-by: guanyi3 <[email protected]>
bf3f1db to
ff81d41
Compare
Because the priority of ostest was increased, the priority of the main thread also increased. Newly created threads still used the default priority, causing the parent thread to prematurely cancel the child thread. This resulted in the child thread not being properly garbage collected, leading to a system busy loop. Signed-off-by: yangao1 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: Please adhere to Contributing Guidelines.
Summary
sometimes ostest fail because of other task with higher priority are running, this PR add kconfig to set ostest priority so that we can increase ostest priority easily.
Impact
ostest priority
Testing
ostest