Ignore:
Timestamp:
07/15/2006 03:26:14 AM (18 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
491d4629
Parents:
3db5b78
Message:

Updated glibc text concerning potential test failures

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter06/glibc.xml

    r3db5b78 ra0ec869  
    129129grep Error glibc-check-log</userinput></screen>
    130130
    131     <para>On at least i686 you can expect to see failures in the
    132     <emphasis>test-double </emphasis> and <emphasis>test-idouble</emphasis>
    133     math tests with gcc-&gcc-version;, as well as an expected (ignored)
    134     failure in <emphasis> posix/annexc</emphasis>.  These two failures in
    135     the math tests appear to be harmless.</para>
    136 
    137     <para>The Glibc test suite is highly dependent on certain functions of
    138     the host system, in particular the kernel. In certain circumstances,
    139     some failures are unavoidable. This is a list of the most common
    140     issues:</para>
     131    <para>You will probably see an expected (ignored) failure in the
     132    <emphasis>posix/annexc</emphasis> test.  In addition the Glibc test suite
     133    is somewhat dependent on the host system.  This is a list of the most
     134    common issues:</para>
    141135
    142136    <itemizedlist>
    143137      <listitem>
    144         <para>The <emphasis>math</emphasis> tests sometimes fail in other
    145         tests when running on systems where the CPU is not a relatively
    146         new genuine Intel or authentic AMD. Certain optimization settings
    147         are also known to be a factor here.</para>
     138        <para>The <emphasis>nptl/tst-clock2</emphasis> and
     139        <emphasis>tst-attr3</emphasis> tests sometimes
     140        fail.  The reason is not completely understood, but indications
     141        are that a heavy system load can trigger these failures.</para>
    148142      </listitem>
    149143      <listitem>
    150         <para>The <emphasis>gettext</emphasis> test sometimes fails due to
    151         host system issues. The exact reasons are not yet clear.</para>
     144        <para>The math tests sometimes fail when running on
     145        systems where the CPU is not a relatively new genuine Intel or
     146        authentic AMD processor.</para>
    152147      </listitem>
    153148      <listitem>
     
    158153      </listitem>
    159154      <listitem>
    160         <para>When running on older and slower hardware, some tests
    161         can fail because of test timeouts being exceeded.</para>
     155        <para>When running on older and slower hardware or on systems under
     156        load, some tests can fail because of test timeouts being exceeded.</para>
    162157      </listitem>
    163158    </itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.