Ignore:
Timestamp:
02/18/2024 11:30:10 PM (7 months ago)
Author:
Thomas Trepl <thomas@…>
Branches:
multilib, xry111/multilib
Children:
9658a0eb
Parents:
b3a55dc (diff), 5f2ba8c (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Automatic merge of trunk into multilib

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/glibc.xml

    rb3a55dc r44b216e  
    172172
    173173      <listitem>
    174         <para>Three <emphasis>nptl/tst-thread-affinity*</emphasis>
    175         tests are known to fail.</para>
    176       </listitem>
    177 
    178 <!-- Did not fail with glibc-2.38
    179       <listitem>
    180         <para><emphasis>misc/tst-ttyname</emphasis>
    181         is known to fail in the LFS chroot environment.</para>
    182       </listitem>
    183 -->
    184 
    185       <!-- https://sourceware.org/pipermail/libc-alpha/2022-August/141567.html -->
    186       <listitem>
    187         <para>The <emphasis>stdlib/tst-arc4random-thread</emphasis>
    188         test is known to fail if the host kernel is relatively old.</para>
    189       </listitem>
    190 
    191       <listitem>
    192174        <para>Some tests, for example
    193         <emphasis>nss/tst-nss-files-hosts-multi</emphasis>,
    194         are known to fail on relatively slow systems due to an internal
    195         timeout.</para>
     175        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> and
     176        <emphasis>nptl/tst-thread-affinity*</emphasis>
     177        are known to fail due to a timeout (especially when the system is
     178        relatively slow and/or running the test suite with multiple
     179        parallel make jobs).  These tests can be identified with:</para>
     180
     181        <!-- TODO: Using nodump for freeze.  Change it to role="test" after
     182             12.1 release so jhalfs can list these in the log.  -->
     183        <screen role="nodump"><userinput>grep "Timed out" -l $(find -name \*.out)</userinput></screen>
     184
     185        <para>It's possible to re-run a single test with enlarged timeout
     186        with
     187        <command>TIMEOUTFACTOR=<replaceable>&lt;factor&gt;</replaceable>
     188        make test t=<replaceable>&lt;test name&gt;</replaceable></command>.
     189        For example, <command>TIMEOUTFACTOR=10 make test
     190        t=nss/tst-nss-files-hosts-multi</command> will re-run
     191        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> with ten times
     192        the original timeout.</para>
    196193      </listitem>
    197194
    198195      <listitem>
    199196        <para>Additionally, some tests may fail with a relatively old CPU
    200         model or host kernel version.</para>
     197        model (for example
     198        <emphasis>elf/tst-cpu-features-cpuinfo</emphasis>) or host kernel
     199        version (for example
     200        <emphasis>stdlib/tst-arc4random-thread</emphasis>).</para>
    201201      </listitem>
    202202    </itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.