[Bug regex/1178] New: posix regex tests timeout on PII 180MHz

["brandon_peirce at hotmail dot com" <sourceware-bugzilla at sources dot redhat dot com>]

The timeouts are too short to complete two of the tests on a PII 180MHz box. 
Increase the timeouts for these 2 tests and the entire glibc test suite 
completes successfully (so I must have done something right :-).
posix/bug-regex24.c: increase from 30 to 45 sec (takes 41 on my box)
posix/tst-regex2.c: increase from 20 to 35 sec (takes 31 on my box)

Follows patch against release 2.3.4 to increase timeout to a minimum needed for 
successfull completion of tests.

___ Start of patch ___
diff -u glibc-2.3.4/posix/bug-regex24.c glibc/posix/bug-regex24.c
--- glibc-2.3.4/posix/bug-regex24.c     2004-11-15 22:59:15.000000000 +0100
+++ glibc/posix/bug-regex24.c   2005-08-06 11:06:15.000000000 +0200
@@ -55,6 +55,6 @@
   return result;
 }

-#define TIMEOUT 30
+#define TIMEOUT 45
 #define TEST_FUNCTION do_test ()
 #include "../test-skeleton.c"
diff -u glibc-2.3.4/posix/tst-regex2.c glibc/posix/tst-regex2.c
--- glibc-2.3.4/posix/tst-regex2.c      2004-12-10 01:40:08.000000000 +0100
+++ glibc/posix/tst-regex2.c    2005-08-06 11:05:45.000000000 +0200
@@ -244,6 +244,6 @@
   return 0;
 }

-#define TIMEOUT 20
+#define TIMEOUT 35
 #define TEST_FUNCTION do_test ()
 #include "../test-skeleton.c"
___ End of patch ___

-- 
           Summary: posix regex tests timeout on PII 180MHz
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: normal
          Priority: P3
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: brandon_peirce at hotmail dot com
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1178

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.