|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1399 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 1399.
Report 1399 Actions
Problem Report Number 1399 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0681 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published 1996-07-25 08:00 Product Standard Internationalised System Calls and Libraries Extended (UNIX 95) Certification Program The Open Brand certification program Test Suite VSU version 4.1.0 Test Identification CAPIbase/flockf 3 Problem Summary TSD4U.00134 This test may fail on slower implementations because the test does not wait long enough for the test to finish. Problem Text
We observed that this test case has a hard-coded timeout that does
not allow for slower systems. Normally we see a tet_getvar for
VSU_MACHINE_PERFORMANCE and then that value is assigned to a variable
"performance". The variable is then used as a multiplier of some
fixed constant timeout value. In this case we see the following code
in flockf33.c:
-----------------------------------------------------------------------
EFORK;
wait_for(pid, (2*MAX_TIME_TO_RUN));
tet_infoline("TEST: All the locks set by child are removed");
tet_infoline(" after child has terminated");
-----------------------------------------------------------------------
There is no provision in the wait_for arguments for an adjustable
performance number. Sometimes the test does succeed but often
it fails and runs out of time (see journal entry provided).
When I increased the multiplier value from 2*MAX_TIME_TO_RUN to
(4*MAX_TIME_TO_RUN), the test case always succeeds:
-----------------------------------------------------------------------
10|1 /tset/CAPIbase/flockf/flockf3 16:39:06|TC Start, scenario ref 0-1
15|1 1.10 1|TCM Start
400|1 3 1 16:39:07|IC Start
200|1 1 16:39:07|TP Start
520|1 1 953417760 1 1|SPEC1170TESTSUITE CASE 3
520|1 1 953417760 1 2|All advisory-mode locks placed on a file by a call to
520|1 1 953417760 1 3|int lockf(int fildes, int function, off_t size) shall
520|1 1 953417760 1 4|be removed when the process exits.
520|1 1 1657405477 1 1|PREP: Open the data file
520|1 1 1657405477 1 2|PREP: Fork a child
520|1 1 249364486 1 1|PREP: Issue the locks
520|1 1 1657405477 2 1|TEST: All the locks set by child are removed
520|1 1 1657405477 2 2| after child has terminated
520|1 1 1657405477 123 1|CLEANUP: Close file
220|1 1 0 16:40:12|PASS
410|1 3 1 16:40:12|IC End
80|1 0 16:40:12|TC End
900|16:40:12|TCC End
---------------------------------------------------------------------Test Output
10|1 /tset/CAPIbase/flockf/flockf3 17:07:07|TC Start, scenario ref 0-1
15|1 1.10 1|TCM Start
400|1 3 1 17:07:08|IC Start
200|1 1 17:07:08|TP Start
520|1 1 712769546 1 1|SPEC1170TESTSUITE CASE 3
520|1 1 712769546 1 2|All advisory-mode locks placed on a file by a call to
520|1 1 712769546 1 3|int lockf(int fildes, int function, off_t size) shall
520|1 1 712769546 1 4|be removed when the process exits.
520|1 1 269549574 1 1|PREP: Open the data file
520|1 1 269549574 1 2|PREP: Fork a child
520|1 1 788529154 1 1|PREP: Issue the locks
520|1 1 269549574 2 1|ERROR: wait_for: Timed-out waiting for child to exit.
520|1 1 269549574 2 2|TEST: All the locks set by child are removed
520|1 1 269549574 2 3| after child has terminated
520|1 1 269549574 123 1|CLEANUP: Close file
220|1 1 1 17:08:00|FAIL
410|1 3 1 17:08:00|IC End
80|1 0 17:08:00|TC End
900|17:08:00|TCC EndReview Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
We agree this is a test suite deficiency in the test
suite version(s) listed.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion
This is an agreed Test Suite Deficiency.
Problem Reporting System Options:
- View Report 1399
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority