Chandan U created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1066
Project:Branches: Chandanuvm/rtems:chandan/psxmsgq05-priority-coverage to rtems/rtos/rtems:main Author: Chandan U **Problem** At the moment, we don’t have a dedicated POSIX test that checks the MQ_PRIO_MAX boundary and how priority-based insertion behaves in POSIX message queues. So there isn’t explicit coverage for the valid priority range, out-of-range rejection, or ordering semantics. **What Changed** Added a new test psxmsgq05 which exercises priority handling in POSIX message queues. The test covers: - Printing and confirming the MQ_PRIO_MAX value provided by the toolchain. - Verifying that priorities greater than MQ_PRIO_MAX are rejected with EINVAL. - Sending messages across the full valid range 0 .. MQ_PRIO_MAX. - Checking receive ordering when mixed priorities are queued. - Confirming FIFO behavior when multiple messages share the same priority. **How Tested** Built for SPARC/ERC32 and ran on the SIS simulator. **Command used:** `/path/to/rtems-test --rtems-bsp=erc32-sis \ build/sparc/erc32/testsuites/psxtests/psxmsgq05.exe` Test completed successfully. Output includes the printed MQ_PRIO_MAX value and all validation steps. ``` *** BEGIN OF TEST PSXMSGQ 5 *** *** TEST VERSION: 7.0.0.fb67bc866feae0f0788075f2830b01c60f47d66e-modified *** TEST STATE: EXPECTED_PASS *** TEST BUILD: *** TEST TOOLS: 15.2.0 20250808 (RTEMS 7, RSB 72f17919581ef21a523cb2c5b3e566e10fe20d8d, Newlib 038afec1) Init - MQ_PRIO_MAX = 32 Init - Open message queue Init - Validate accepted priorities 0..MQ_PRIO_MAX Init - Validate mq_send rejects MQ_PRIO_MAX + 1 with EINVAL Init - Validate mixed-priority receive ordering Init - Validate FIFO ordering for equal priorities Init - Close and unlink message queue *** END OF TEST PSXMSGQ 5 *** ``` -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1066 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
