Skip to content

Conversation

@zzby0
Copy link

@zzby0 zzby0 commented Jan 14, 2026

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

@xiaoxiang781216
Copy link
Contributor

@zzby0 please fix:

❌ Missing git commit message
Used config files:
    1: .codespellrc
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/cond.c:219: excecuted ==> executed
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/cond.c:222: aquire ==> acquire
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/cond.c:222: aquires ==> acquires
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/prioinherit.c:355: midle ==> middle
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/prioinherit.c:406: exitted ==> exited
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/prioinherit.c:660: ERRROR ==> ERROR
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/signest.c:535: intefering ==> interfering
/home/runner/work/nuttx-apps/nuttx-apps/apps/testing/ostest/waitpid.c:62: exitting ==> exiting

}

sparam.sched_priority = (prio_min + prio_mid) / 2;
sparam.sched_priority = PRIORITY - 10;
Copy link
Contributor

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?

Copy link
Author

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

zzby0 and others added 3 commits January 15, 2026 15:29
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]>
@zzby0 zzby0 force-pushed the ostest branch 2 times, most recently from bf3f1db to ff81d41 Compare January 15, 2026 13:06
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]>
@zzby0 zzby0 marked this pull request as draft January 15, 2026 15:06
@zzby0 zzby0 marked this pull request as ready for review January 15, 2026 15:06
@zzby0 zzby0 marked this pull request as draft January 15, 2026 15:07
@zzby0 zzby0 marked this pull request as ready for review January 15, 2026 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants