Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1049 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1049.

Report 1049 Actions

    Problem Report Number 1049
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0039
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-07-02 08:00
    Expiry Date 1999-07-02
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSRT version 5.0.1
    Test Identification rt.os/mqueue/mq_send 5
    Problem Summary MSF4R.00001 The implementation does not support the required functionality for threads with PTHREAD_SCOPE_PROCESS.
    Problem Text
    This request is for the following test failures:

    /tset/rt.os/mqueue/mq_send/T.mq_send 5
    /tset/rt.os/mqueue/mq_receive/T.mq_receive 4
    /tset/rt.os/semaphores/sem_post/T.sem_post 3
    /tset/rt.os/semaphores/sem_post/T.sem_post 5

    The XSH5 specification states that the if there is more than one thread
    (whose scheduling policy is SCHED_FIFO/SCHED_RR) waiting for a named
    semaphore or message queue, the thread with the highest priority that
    has been waiting the longest will be unblocked.

    We are seeking a MSF for a known fault in our implementation. The
    above assertion does work for threads whose contention scope is
    PTHREAD_SCOPE_SYSTEM (system scope threads) and as such applications
    desiring this behavior can use system scope threads.
    Test Output

    /tset/rt.os/mqueue/mq_send/T.mq_send 5
    200|0 5 18:45:58|TP Start
    520|0 5 00002658 2 1|For SCHED_FIFO unblocked thread was incorrect,
    expected thread with priority 10 got 1
    520|0 5 00002658 2 2|For SCHED_RR unblocked thread was incorrect,
    expected thread with priority 10 got 1
    520|0 5 00002658 2 3|mq_open() failed for "/vsrt_mqueue", errno = 24 (EMFILE)
    520|0 5 00002645 2 1|child process timed out
    220|0 5 1 18:46:38|FAIL
    410|0 5 1 18:46:38|IC End

    /tset/rt.os/mqueue/mq_receive/T.mq_receive 4
    400|0 4 1 18:52:06|IC Start
    200|0 4 18:52:06|TP Start
    520|0 4 00002714 2 1|For SCHED_FIFO unblocked thread was incorrect,
    expected thread with priority 10 got 1
    520|0 4 00002714 2 2|For SCHED_RR unblocked thread was incorrect,
    expected thread with priority 10 got 1
    520|0 4 00002714 2 3|mq_open() failed for "/vsrt_mqueue", errno = 24 (EMFILE)
    520|0 4 00002709 2 1|child process timed out
    220|0 4 1 18:52:47|FAIL
    410|0 4 1 18:52:47|IC End

    /tset/rt.os/semaphores/sem_post/T.sem_post 3
    200|0 3 18:55:27|TP Start
    520|0 3 00002793 2 1|For SCHED_FIFO unblocked thread was incorrect,
    expected thread with priority 10 got 1
    220|0 3 1 18:55:29|FAIL
    410|0 3 1 18:55:29|IC End

    /tset/rt.os/semaphores/sem_post/T.sem_post 5
    400|0 5 1 18:55:31|IC Start
    200|0 5 18:55:31|TP Start
    520|0 5 00002795 2 1|For SCHED_RR unblocked thread was incorrect,
    expected thread with priority 10 got 1
    220|0 5 1 18:55:33|FAIL
    410|0 5 1 18:55:33|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We are of two minds about this request.

    The submitter has not provided a rationale for this fault having a
    minor impact on application portability. It appears to us to exceed the
    scope of what is normally considered minor as it an application using
    process scope threads will not be provided the expected scheduling behavior.
    Such applications may well not be able to simply be changed to use
    system scope threads and may well not work predictably if they
    were changed.

    On the other hand we do not believe this will impact a significant number
    of applications.

    All in all we recommend a temporary waiver for a minor system fault
    be granted, with the recommendation to the submitter that this problem
    be corrected as expediently as possible.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    This request should go for a 14 day review by the Base Working Group.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    There was no disagreement with the consultant in the review period.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Minor System Fault (MSF)
    Review Conclusion
    A Temporary Waiver is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority