Changeset 751a13d


Ignore:
Timestamp:
02/15/2018 05:21:30 PM (4 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, 8.2, 8.2-rc1, 8.3, 8.3-rc1, 8.3-rc2, 8.4, 8.4-rc1, 9.0, 9.0-rc1, 9.1, 9.1-rc1, cross-chap5, ml-11.0, multilib, old-trunk, trunk, xry111/git-transition, xry111/glibc-2.34, xry111/tester-nohack, xry111/usr-move
Children:
5ec731c, 60d91a0
Parents:
a3c628a
Message:

Touch up discussions of regression test failures in a few packages

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

Location:
chapter06
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • chapter06/automake.xml

    ra3c628a r751a13d  
    5959make -j4 check</userinput></screen>
    6060
    61     <para>Three tests are known to fail in the LFS environment:
    62     check12.sh, subobj.sh, and check12-w.sh.</para>
     61    <para>Two tests are known to fail in the LFS environment:
     62    check12.sh and check12-w.sh.</para>
    6363
    6464    <para>Install the package:</para>
  • chapter06/gcc.xml

    ra3c628a r751a13d  
    127127    <para>A few unexpected failures cannot always be avoided. The GCC developers
    128128    are usually aware of these issues, but have not resolved them yet.
    129     In particular, five tests in the libstdc++ test suite are known to fail
     129    In particular, six tests in the libstdc++ test suite are known to fail
    130130    when running as the root user as we do here.
    131131    Unless the test results are vastly different from those at the above URL,
  • chapter06/glibc.xml

    ra3c628a r751a13d  
    161161
    162162      <listitem>
     163        <para><emphasis>misc/tst-ttyname</emphasis>
     164        is known to fail in the LFS chroot environment.</para>
     165      </listitem>
     166
     167      <listitem>
    163168        <para><emphasis>posix/tst-getaddrinfo4</emphasis> and
    164169        <emphasis>posix/tst-getaddrinfo5</emphasis>
    165170        may fail on some architectures.</para>
    166171      </listitem>
    167 
     172<!--
    168173      <listitem>
    169174        <para>The <emphasis>rt/tst-cputimer1</emphasis> and
     
    189194        malloc/tst-malloc-usable and nptl/tst-cleanupx4. </para>
    190195      </listitem>
    191 
     196-->
    192197    </itemizedlist>
    193198
Note: See TracChangeset for help on using the changeset viewer.