Changeset 767a2a5 for BOOK/final-system/common

Timestamp:

Mar 1, 2014, 8:31:55 PM (11 years ago)

Author:

William Harrington <kb0iic@…>

Branches:

clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

5342ade

Parents:

8853ac5

Message:

Add conform/run-conformtest as an emphasis with posix/annexc as being ignored, and include some more teset suite failures with reasons.

File:

• BOOK/final-system/common/glibc.xml (modified) (3 diffs)

BOOK/final-system/common/glibc.xml

@@ -112 +112 @@
 
     <para os="o">The GLIBC test suite is highly dependent on certain functions of
-    the host system, in particular the kernel. The posix/annexc test normally fails
+    the host system, in particular the kernel. The <emphasis>posix/annexc</emphasis> and
+    <emphasis>conform/run-conformtest</emphasis> tests normally fail
     and you should see <literal>Error 1 (ignored)</literal> in the output. Apart
     from this, the GLIBC test suite is always expected to pass. However, in certain
@@ -123 +124 @@
 
     <itemizedlist os="p">
+      <listitem>
+        <para>The <emphasis>nptl/tst-clock2</emphasis>,
+        <emphasis>nptl/tst-attr3</emphasis>,
+        <emphasis>tst/tst-cputimer1</emphasis>, and
+        <emphasis>rt/tst-cpuclock2</emphasis>
+        tests have been known to fail.  The
+        reason is not completely understood, but indications are that minor
+        timing issues can trigger these failures.</para>
+      </listitem>
       <listitem>
         <para>The <emphasis>math</emphasis> tests sometimes fail.
@@ -137 +147 @@
       <listitem>
         <para>When running on older and slower hardware, some tests
-        can fail because of test timeouts being exceeded.</para>
+        can fail because of test timeouts being exceeded.
+        Modifying the make check command to set a TIMEOUTFACTOR is reported to
+        help eliminate these errors (e.g. <command>TIMEOUTFACTOR=16
+        make -k check</command>).</para>
+      </listitem>
+      <listitem>
+        <para>posix/tst-getaddrinfo4 will always fail due to not having a network
+        connection when the test is run.</para>
       </listitem>
     </itemizedlist>