Changeset 44b216e
- Timestamp:
- 02/18/2024 11:30:10 PM (7 months ago)
- 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. - Location:
- chapter08
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/gcc.xml
rb3a55dc r44b216e 194 194 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 195 195 196 <para><!--Two tests named <filename>pr104610.c</filename> and 197 <filename>pr69482-1.c</filename> are known to fail because the test 198 files does not account for the 199 <parameter>- -enable-default-ssp</parameter> option.--> 200 <!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 --> 201 Eight gcc tests (out of over 185,000), data-model-4.c, pr56837.c, 202 and six "analyzer" tests are known to fail. 203 204 One libstdc++ test (out of over 15000), copy.cc, is known to fail. 205 206 For g++, 21 tests (out of approximately 250,000), 14 "AddressSanitizer*" 207 tests and 7 interception-malloc-test-1.C tests, are known to fail. 196 <para> 197 Eight gcc tests (out of over 185,000): 198 <!-- https://gcc.gnu.org/PR106375 --><filename>pr56837.c</filename> 199 and seven tests in the <filename class='directory'>analyzer</filename> 200 directory are known to fail. 201 202 <!-- https://gcc.gnu.org/PR109353 --> 203 One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is 204 known to fail. 205 206 For g++, 21 tests (out of approximately 250,000): 14 207 <quote>AddressSanitizer*</quote> 208 tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are 209 known to fail. 208 210 209 211 Additionally, several tests in the 210 212 <filename class='directory'>vect</filename> directory are known to fail 211 213 if the hardware does not support AVX.</para> 212 <!-- 213 <para> 214 With Glibc-2.39, the gcc analyzer tests named 215 <filename>data-model-4.c</filename> and 216 <filename>conftest-1.c</filename> 217 are known to fail. 218 In the asan tests, several tests in <filename>asan_test.C</filename> 219 are known to fail. 220 The test named <filename>interception-malloc-test-1.C</filename> 221 is known to fail. 222 </para> 223 --> 214 224 215 <para>A few unexpected failures cannot always be avoided. The GCC developers 225 216 are usually aware of these issues, but have not resolved them yet. 226 217 Unless the test results are vastly different from those at the above URL, 227 218 it is safe to continue.</para> 228 229 <!--note><para>230 On some combinations of kernel configuration and AMD processors231 there may be more than 1100 failures in the gcc.target/i386/mpx232 tests (which are designed to test the MPX option on recent233 Intel processors). These can safely be ignored on AMD234 processors. These tests will also fail on Intel processors if MPX support235 is not enabled in the kernel even though it is present on the CPU.236 </para></note-->237 219 238 220 <para>Install the package:</para> -
chapter08/glibc.xml
rb3a55dc r44b216e 172 172 173 173 <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.38179 <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>192 174 <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><factor></replaceable> 188 make test t=<replaceable><test name></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> 196 193 </listitem> 197 194 198 195 <listitem> 199 196 <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> 201 201 </listitem> 202 202 </itemizedlist>
Note:
See TracChangeset
for help on using the changeset viewer.