Adding Benchmark test for the test case " mq_receive: not available: block"(GCI 2018)

Shashvat Jain shashvatjain2002 at gmail.com
Mon Nov 12 04:56:32 UTC 2018


Thank you for the clarification. :)

On Mon, Nov 12, 2018 at 10:15 AM Joel Sherrill <joel at rtems.org> wrote:

>
>
> On Sun, Nov 11, 2018, 9:33 PM Shashvat Jain <shashvatjain2002 at gmail.com
> wrote:
>
>> hello ,
>> multiple test cases have been defined in a single test
>> https://git.rtems.org/rtems/tree/testsuites/psxtmtests/psxtmmq01/psxtmmq01.doc
>>
>> The task instructs me to add  a new test , just for clarification , will
>> it be right to add  the test case "mq_receive: not available: block" in
>> the same test?
>>
>
> I don't think so. It would need to follow the same multiple task blocking
> pattern used by something a mutex or semaphore unavailable and block.
>
> Answering from my phone but task blocking and unblocking tests tend to
> have multiple threads and be standalone tests
>
>  But if this case is missing, you found a legitimate one to add.
>
> --joel
>
>>
>>
>> thank you
>> --Shashvat
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181112/6acb7f37/attachment-0001.html>


More information about the devel mailing list