Updated glibc text concerning potential test failures

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7673 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2006-07-15 03:26:14 +00:00
parent 3db5b786e0
commit a0ec8699f4
4 changed files with 27 additions and 22 deletions

View File

@ -35,6 +35,16 @@
</itemizedlist>
</listitem>
-->
<listitem>
<para>July 15, 2006</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Updated text concerning test failures in
glibc to describe the most recent results.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 13, 2006</para>
<itemizedlist>

View File

@ -128,27 +128,22 @@ cd ../glibc-build</userinput></screen>
<screen><userinput>make -k check 2&gt;&amp;1 | tee glibc-check-log
grep Error glibc-check-log</userinput></screen>
<para>On at least i686 you can expect to see failures in the
<emphasis>test-double </emphasis> and <emphasis>test-idouble</emphasis>
math tests with gcc-&gcc-version;, as well as an expected (ignored)
failure in <emphasis> posix/annexc</emphasis>. These two failures in
the math tests appear to be harmless.</para>
<para>The Glibc test suite is highly dependent on certain functions of
the host system, in particular the kernel. In certain circumstances,
some failures are unavoidable. This is a list of the most common
issues:</para>
<para>You will probably see an expected (ignored) failure in the
<emphasis>posix/annexc</emphasis> test. In addition the Glibc test suite
is somewhat dependent on the host system. This is a list of the most
common issues:</para>
<itemizedlist>
<listitem>
<para>The <emphasis>math</emphasis> tests sometimes fail in other
tests when running on systems where the CPU is not a relatively
new genuine Intel or authentic AMD. Certain optimization settings
are also known to be a factor here.</para>
<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>
</listitem>
<listitem>
<para>The <emphasis>gettext</emphasis> test sometimes fails due to
host system issues. The exact reasons are not yet clear.</para>
<para>The math tests sometimes fail when running on
systems where the CPU is not a relatively new genuine Intel or
authentic AMD processor.</para>
</listitem>
<listitem>
<para>If you have mounted the LFS partition with the
@ -157,8 +152,8 @@ grep Error glibc-check-log</userinput></screen>
use the <parameter>noatime</parameter> option while building LFS.</para>
</listitem>
<listitem>
<para>When running on older and slower hardware, some tests
can fail because of test timeouts being exceeded.</para>
<para>When running on older and slower hardware or on systems under
load, some tests can fail because of test timeouts being exceeded.</para>
</listitem>
</itemizedlist>

View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "SVN-20060713">
<!ENTITY releasedate "July 13, 2006">
<!ENTITY version "SVN-20060715">
<!ENTITY releasedate "July 15, 2006">
<!ENTITY milestone "6.2">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->

View File

@ -490,10 +490,10 @@
<!ENTITY udev-ch6-du "6.8 MB">
<!ENTITY udev-ch6-sbu "0.1 SBU">
<!ENTITY udev-config "udev-config-20060712">
<!ENTITY udev-config "udev-config-20060715">
<!ENTITY udev-config-size "4 KB">
<!ENTITY udev-config-url "http://www.linuxfromscratch.org/lfs/downloads/development/&udev-config;.tar.bz2">
<!ENTITY udev-config-md5 "43817b01e0ae8de3cec31e8c395c6a00">
<!ENTITY udev-config-md5 "TBD-udev-config-md5">
<!ENTITY udev-config-home " ">
<!ENTITY util-linux-version "2.12r">