Update known failure problems in glibc tests

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9185 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/changelog.xml

@@ -37,6 +37,15 @@
 
 -->
 
+    <listitem>
+      <para>2010-02-17</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] Update known failure problems in glibc tests.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2010-02-11</para>
       <itemizedlist>

chapter06/glibc.xml

@@ -151,16 +151,20 @@ grep Error glibc-check-log</userinput></screen>
 
     <itemizedlist>
       <!-- Check again after updating from gcc-4.1.x -->
-      <listitem>
+      <!-- Haven;t seen this in quite a while <listitem>
         <para>The <emphasis>nptl/tst-cancel1</emphasis> test will fail when
         using the 4.1 series of GCC.</para>
-      </listitem>
-      <!-- Was true in glibc-2.3.6 -->
+      </listitem> -->
+      <!-- Was true in glibc-2.3.6, rt/tst-cpuclock2 in glibc-2.11.1 -->
       <listitem>
-        <para>The <emphasis>nptl/tst-clock2</emphasis> and
-        <emphasis>tst-attr3</emphasis> tests sometimes
-        fail.  The reason is not completely understood, but indications
-        are that a heavy system load can trigger these failures.</para>
+
+        <para>The <emphasis>nptl/tst-clock2</emphasis>,
+        <emphasis>nptl/tst-attr3</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 math tests sometimes fail when running on

general.ent

@@ -1,5 +1,5 @@
-<!ENTITY version "SVN-201002016">
-<!ENTITY releasedate "February 16, 2010">
+<!ENTITY version "SVN-201002017">
+<!ENTITY releasedate "February 17, 2010">
 <!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not &ndash; -->
 <!ENTITY milestone "7.0">
 <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->