- Timestamp:
- Mar 1, 2014, 8:31:55 PM (11 years ago)
- Branches:
- clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- 5342ade
- Parents:
- 8853ac5
- Location:
- BOOK/final-system
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/final-system/common/glibc.xml
r8853ac5 r767a2a5 112 112 113 113 <para os="o">The GLIBC test suite is highly dependent on certain functions of 114 the host system, in particular the kernel. The posix/annexc test normally fails 114 the host system, in particular the kernel. The <emphasis>posix/annexc</emphasis> and 115 <emphasis>conform/run-conformtest</emphasis> tests normally fail 115 116 and you should see <literal>Error 1 (ignored)</literal> in the output. Apart 116 117 from this, the GLIBC test suite is always expected to pass. However, in certain … … 123 124 124 125 <itemizedlist os="p"> 126 <listitem> 127 <para>The <emphasis>nptl/tst-clock2</emphasis>, 128 <emphasis>nptl/tst-attr3</emphasis>, 129 <emphasis>tst/tst-cputimer1</emphasis>, and 130 <emphasis>rt/tst-cpuclock2</emphasis> 131 tests have been known to fail. The 132 reason is not completely understood, but indications are that minor 133 timing issues can trigger these failures.</para> 134 </listitem> 125 135 <listitem> 126 136 <para>The <emphasis>math</emphasis> tests sometimes fail. … … 137 147 <listitem> 138 148 <para>When running on older and slower hardware, some tests 139 can fail because of test timeouts being exceeded.</para> 149 can fail because of test timeouts being exceeded. 150 Modifying the make check command to set a TIMEOUTFACTOR is reported to 151 help eliminate these errors (e.g. <command>TIMEOUTFACTOR=16 152 make -k check</command>).</para> 153 </listitem> 154 <listitem> 155 <para>posix/tst-getaddrinfo4 will always fail due to not having a network 156 connection when the test is run.</para> 140 157 </listitem> 141 158 </itemizedlist> -
BOOK/final-system/x86/glibc.xml
r8853ac5 r767a2a5 103 103 <itemizedlist os="p"> 104 104 <listitem> 105 <para>The <emphasis>nptl/tst-clock2</emphasis>, 106 <emphasis>nptl/tst-attr3</emphasis>, 107 <emphasis>tst/tst-cputimer1</emphasis>, and 108 <emphasis>rt/tst-cpuclock2</emphasis> 109 tests have been known to fail. The 110 reason is not completely understood, but indications are that minor 111 timing issues can trigger these failures.</para> 112 </listitem> 113 <listitem> 105 114 <para>The <emphasis>math</emphasis> tests, at least on i686, fail in 106 115 the <emphasis>test-double</emphasis> and <emphasis>test-idouble</emphasis> … … 120 129 <listitem> 121 130 <para>When running on older and slower hardware, some tests 122 can fail because of test timeouts being exceeded.</para> 131 can fail because of test timeouts being exceeded. 132 Modifying the make check command to set a TIMEOUTFACTOR is reported to 133 help eliminate these errors (e.g. <command>TIMEOUTFACTOR=16 134 make -k check</command>).</para> 135 </listitem> 136 <listitem> 137 <para>posix/tst-getaddrinfo4 will always fail due to not having a network 138 connection when the test is run.</para> 123 139 </listitem> 124 140 </itemizedlist>
Note:
See TracChangeset
for help on using the changeset viewer.