HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


Problem Report 1089 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 1089.


Report 1089 Actions


    Problem Report Number 1089
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0304
    Raised 1999-11-12 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSRT version 5.0.3
    Test Identification rt.os/aio/lio_listio 17
    Problem Summary PG4R.00018 Intermittent failures due to timing problems.
    Problem Text

    This request concerns the following test cases:

    4 rt.os/aio/lio_listio/T.lio_listio 9 Failed
    8 rt.os/aio/lio_listio/T.lio_listio 10 Failed
    3 rt.os/aio/lio_listio/T.lio_listio 17 Failed
    7 rt.os/aio/lio_listio/T.lio_listio 27 Failed
    3 rt.os/aio/lio_listio/T.lio_listio 44 Failed
    11 rt.os/aio/aio_fsync/T.aio_fsync 1 Failed
    11 rt.os/aio/aio_fsync/T.aio_fsync 4 Failed
    7 rt.os/aio/aio_fsync/T.aio_fsync 9 Failed

    The failures occur intermittently. The left column above shows the
    number of instances of each failure in sixteen iterations of the test.
    The failures do not occur on faster hardware implementations.

    In each case, several I/O operations are started and expected to be
    complete by the time a "sleep()", usually "sleep(2)", times out. On
    slower hardware this sometimes does not occur. The tests pass if the
    sleep() value is increased.

    Perhaps it would be best to tie all the sleep() values in the suite
    to SPEEDFACTOR or a new parameter in tetexec.cfg.

    This request also applies to cases with numerically different results:
    cases where different numbers of signals are missed but the failure
    mechanism is the same.

    Test Output

    10|0 /tset/rt.os/aio/lio_listio/T.lio_listio 10:22:16|TC Start, scenario ref 1-0
    15|0 3.2-lite 45|TCM Start
    ...
    200|0 9 10:23:29|TP Start
    520|0 9 000390808 1 1|> test with pipe
    520|0 9 000390808 2 1|> test with pty
    520|0 9 000390808 3 1|> test with tty
    520|0 9 000390808 3 2|tty testing not configured
    520|0 9 000390808 3 3|> test with pipe
    520|0 9 000390852 1 1|Expected 13 signals, received 12
    520|0 9 000390808 4 1|> test with pty
    520|0 9 000390808 5 1|> test with tty
    520|0 9 000390808 5 2|tty testing not configured
    220|0 9 1 10:23:46|FAIL
    ...
    200|2 10 10:27:53|TP Start
    520|2 10 000390960 1 1|> test with pipe
    520|2 10 000390960 2 1|> test with pty
    520|2 10 000390960 3 1|> test with tty
    520|2 10 000390960 3 2|tty testing not configured
    520|2 10 000390960 3 3|> test with pipe
    520|2 10 000391010 1 1|Expected 13 signals, received 12
    520|2 10 000390960 4 1|> test with pty
    520|2 10 000390960 5 1|> test with tty
    520|2 10 000390960 5 2|tty testing not configured
    220|2 10 1 10:28:06|FAIL
    ...
    200|4 17 10:34:07|TP Start
    520|4 17 000391113 1 1|> test with pipe
    520|4 17 000391179 1 1|Expected 25 signals, received 23
    520|4 17 000391113 2 1|> test with pty
    520|4 17 000391113 3 1|> test with tty
    520|4 17 000391113 3 2|tty testing not configured
    220|4 17 1 10:34:08|FAIL
    ...
    200|2 44 10:29:13|TP Start
    520|2 44 000390960 1 1|INFO: No limit on AIO_MAX
    520|2 44 000390960 1 2|> test with pipe
    520|2 44 000390960 2 1|> test with pty
    520|2 44 000390960 3 1|> test with tty
    520|2 44 000390960 3 2|tty testing not configured
    520|2 44 000390960 3 3|> test with pipe
    520|2 44 000390960 4 1|> test with pty
    520|2 44 000391084 1 1|request 0 is still in progress
    520|2 44 000391084 1 2|request 1 is still in progress
    520|2 44 000391084 1 3|request 2 is still in progress
    520|2 44 000391084 1 4|request 3 is still in progress
    520|2 44 000391084 1 5|request 4 is still in progress
    520|2 44 000391084 1 6|request 5 is still in progress
    520|2 44 000391084 1 7|request 6 is still in progress
    520|2 44 000391084 1 8|request 7 is still in progress
    520|2 44 000391084 1 9|request 8 is still in progress
    520|2 44 000391084 1 10|request 9 is still in progress
    520|2 44 000391084 1 11|request 10 is still in progress
    520|2 44 000391084 1 12|request 11 is still in progress
    520|2 44 000391084 1 13|request 12 is still in progress
    520|2 44 000391084 1 14|request 13 is still in progress
    520|2 44 000391084 1 15|request 14 is still in progress
    520|2 44 000391084 1 16|request 15 is still in progress
    520|2 44 000391084 1 17|request 17 is still in progress
    520|2 44 000391084 1 18|request 18 is still in progress
    520|2 44 000391084 1 19|request 19 is still in progress
    520|2 44 000391084 1 20|request 20 is still in progress
    520|2 44 000391084 1 21|request 21 is still in progress
    520|2 44 000391084 1 22|request 22 is still in progress
    520|2 44 000391084 1 23|request 24 is still in progress
    520|2 44 000390960 5 1|> test with tty
    520|2 44 000390960 5 2|tty testing not configured
    220|2 44 1 10:30:42|FAIL
    ...
    10|1 /tset/rt.os/aio/aio_fsync/T.aio_fsync 10:25:09|TC Start, scenario ref 2-0
    15|1 3.2-lite 13|TCM Start
    400|1 1 1 10:25:09|IC Start
    200|1 1 10:25:09|TP Start
    520|1 1 000390933 1 1|INFO: No limit on AIO_MAX
    520|1 1 000390933 1 2|> test with pipe
    520|1 1 000390933 2 1|> test with pty
    520|1 1 000390936 1 1|Expected 10 signals from aio_reads, received 9
    520|1 1 000390933 3 1|> test with tty
    520|1 1 000390933 3 2|tty testing not configured
    520|1 1 000390933 3 3|> test with file
    220|1 1 1 10:25:20|FAIL
    ...
    400|1 4 1 10:25:48|IC Start
    200|1 4 10:25:48|TP Start
    520|1 4 000390933 1 1|INFO: No limit on AIO_MAX
    520|1 4 000390933 1 2|> test with pipe
    520|1 4 000390933 2 1|> test with pty
    520|1 4 000390948 1 1|Expected 10 signals from aio_reads, received 9
    520|1 4 000390933 3 1|> test with tty
    520|1 4 000390933 3 2|tty testing not configured
    520|1 4 000390933 3 3|> test with file
    220|1 4 1 10:26:03|FAIL
    410|1 4 1 10:26:03|IC End
    ...
    200|1 9 10:26:17|TP Start
    520|1 9 000390933 1 1|INFO: No limit on AIO_MAX
    520|1 9 000390933 1 2|> test with pipe
    520|1 9 000390954 1 1|Expected 10 signals from aio_reads, received 9
    520|1 9 000390933 2 1|> test with pty
    520|1 9 000390933 3 1|> test with tty
    520|1 9 000390933 3 2|tty testing not configured
    520|1 9 000390933 3 3|> test with file
    220|1 9 1 10:26:32|FAIL
    410|1 9 1 10:26:32|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    There does appear to be a fault in lio_listio tests 9, 10, 17 and
    27, and in aio_fsync tests 1, 4 and 9 for which a test suite
    deficiency could be granted. However, the results for lio_listio
    test 44 do not fit the same pattern and are not explained adequately
    by the submitter's rationale. The results for this test do not
    look like a timing problem as for the other tests. Since none of
    the async I/O requests (except the cancelled one) have completed
    after 80 seconds, a more likely explanation might be that there is
    an intermittent fault on the implementation whereby cancelling one
    of the requests causes all of the others to get "stuck".

    It is recommended that this request is refused. We suggest that the
    request should be resubmitted either with lio_listio test 44 omitted
    or with further information about the cause of the failure.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused. Please see rationale and submit another request.

    Problem Reporting System Options:

     

    Back   


Contact the Certification Authority