cederom commented on PR #3174:
URL: https://github.com/apache/nuttx-apps/pull/3174#issuecomment-3272918829

   Thank you for for the tests and test fixes @wangchdo all works now, tested 
on updated `sim:ostest` with `CONFIG_SCHED_EVENTS` enabled :-)
   ```
   (..)
   user_main: scheduler lock test
   sched_lock: Starting lowpri_thread at 97
   sched_lock: Set lowpri_thread priority to 97
   sched_lock: Starting highpri_thread at 98
   sched_lock: Set highpri_thread priority to 98
   sched_lock: Waiting...
   sched_lock: PASSED No pre-emption occurred while scheduler was locked.
   sched_lock: Starting lowpri_thread at 97
   sched_lock: Set lowpri_thread priority to 97
   sched_lock: Starting highpri_thread at 98
   sched_lock: Set highpri_thread priority to 98
   sched_lock: Waiting...
   sched_lock: PASSED No pre-emption occurred while scheduler was locked.
   sched_lock: Finished
   
   End of test memory usage:
   VARIABLE  BEFORE   AFTER
   ======== ======== ========
   arena     3effff8  3effff8
   ordblks         6        7
   mxordblk  3e74f98  3e95fa8
   uordblks    88660    55ca8
   fordblks  3e77998  3eaa350
   
   user_main: nxevent test
   
   End of test memory usage:
   VARIABLE  BEFORE   AFTER
   ======== ======== ========
   arena     3effff8  3effff8
   ordblks         7        7
   mxordblk  3e95fa8  3e95fa8
   uordblks    55ca8    55ca8
   fordblks  3eaa350  3eaa350
   
   Final memory usage:
   VARIABLE  BEFORE   AFTER
   ======== ======== ========
   arena     3effff8  3effff8
   ordblks         1        7
   mxordblk  3ebb1e8  3e95fa8
   uordblks    44e10    55ca8
   fordblks  3ebb1e8  3eaa350
   user_main: Exiting
   ostest_main: Exiting with status 0
   ```
   
   ```
   $ grep CONFIG_SCHED_EVENTS .config
   CONFIG_SCHED_EVENTS=y
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to