lupyuen commented on PR #16343:
URL: https://github.com/apache/nuttx/pull/16343#issuecomment-2865646471

   Sorry @Fix-Point could you check why this PR is crashing OSTest on Arm64 
Avaota-A1 T527 and RISC-V SG2000? Thanks!
   
   ### Arm64 Avaota-A1 SBC (Allwinner T527)
   
   https://gitlab.com/lupyuen/nuttx-build-log/-/snippets/4841520#L1381
   
   ```
   waiter_main: Waiting on semaphoredump_assert_info: Current Version: NuttX  
0.0.0 e97ec75fbc May  9 2025 16:08:46 arm64
   dump_assert_info: Assertion failed (_Bool)0: at file: signest.c:115 task: 
ostest process: ostest 0xc000195c 
   
   signest_test: Started interfere_main pid=61
   signest_dump_assert_info: Current Version: NuttX  0.0.0 e97ec75fbc May  9 
2025 16:08:46 arm64
   dump_assert_info: Assertion failed (_Bool)0: at file: signest.c:115 task: 
ostest process: ostest 0xc000a8b8 
   
   test: Simple case:
     Total signalled 1180  Odd=580 Even=600
     Total handled   1180  Odd=580 Even=600
     Total nested    0    Odd=0   Even=0  
   waiter_action: Delivered to wrong TID 12, expected 58
   waiter_action: Delivered to wrong TID 61, expected 58
   ```
   
   ### RISC-V Oz64 SBC (Sophgo SG2000)
   
   https://gitlab.com/lupyuen/nuttx-build-log/-/snippets/4841523#L1087
   
   ```
   waiter_main: Waiting on semaphoredump_assert_info: Current Version: NuttX  
0.0.0 e97ec75fbc May  9 2025 16:20:58 risc-v
   dump_assert_info: Assertion failed (_Bool)0: at file: signest.c:115 task: 
ostest process: ostest 0xc000001a 
   
   signest_test: Started interfere_main pid=55
   signest_test: Simple case:
     Total signalled 1240  Odd=620 Even=620
     Total handled   1240  Odd=620 Even=620
     Total nested    0    Odd=0   Even=0  
   waiter_action: Delivered to wrong TID 11, expected 54
   ostest_main: Exiting with status 256
   ```
   


-- 
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