SHIVAM DEOLANKAR commented on a discussion on testsuites/validation/tc-intr-set-priority.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_151637 > } > > sc = rtems_interrupt_set_priority( vector, priority ); > + > + /* > + * Some BSPs support full uint32_t priority range > + * UINT32_MAX may be valid. > + */ > + if ( !ctx->valid_priority && sc == RTEMS_SUCCESSFUL ){ I tried narrowing down the failing transaction `InvPrio` by disabling it and the test passed clearly and then implemented current fix to preserve validation on BSPs. It should skip `RTEMS_INVALID_PRIORITY` validation path when `attr.maximum_priority == UINT32_MAX` since this is the case we are targeting. This confirms the test is working after applying the fix resulting in `RtemsIntrReqSetPriority:F:0`, suite `F:0` {width=900 height=589} -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_151637 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
