Update descriptions for some test failures.

This commit is contained in:
Bruce Dubbs 2024-02-14 15:41:22 -06:00
parent d93d11b5ba
commit 28614cdda5
3 changed files with 18 additions and 6 deletions

View File

@ -177,15 +177,20 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
files does not account for the files does not account for the
<parameter>- -enable-default-ssp</parameter> option.--> <parameter>- -enable-default-ssp</parameter> option.-->
<!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 --> <!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 -->
Two tests named <filename>copy.cc</filename> and Eight gcc tests (out of over 185,000), data-model-4.c, pr56837.c,
<filename>pr56837.c</filename> are known to fail. and six "analyzer" tests are known to fail.
<!-- https://gcc.gnu.org/PR107855#c6 -->
One libstdc++ test (out of over 15000), copy.cc, is known to fail.
For g++, 21 tests (out of approximately 250,000), 14 "AddressSanitizer*"
tests and 7 interception-malloc-test-1.C tests, are known to fail.
Additionally, several tests in the Additionally, several tests in the
<filename class='directory'>vect</filename> directory are known to fail <filename class='directory'>vect</filename> directory are known to fail
if the hardware does not support AVX.</para> if the hardware does not support AVX.</para>
<!--
<para> <para>
With Glibc-2.38, the analyzer tests named With Glibc-2.39, the gcc analyzer tests named
<filename>data-model-4.c</filename> and <filename>data-model-4.c</filename> and
<filename>conftest-1.c</filename> <filename>conftest-1.c</filename>
are known to fail. are known to fail.
@ -194,7 +199,7 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
The test named <filename>interception-malloc-test-1.C</filename> The test named <filename>interception-malloc-test-1.C</filename>
is known to fail. is known to fail.
</para> </para>
-->
<para>A few unexpected failures cannot always be avoided. The GCC developers <para>A few unexpected failures cannot always be avoided. The GCC developers
are usually aware of these issues, but have not resolved them yet. are usually aware of these issues, but have not resolved them yet.
Unless the test results are vastly different from those at the above URL, Unless the test results are vastly different from those at the above URL,

View File

@ -163,6 +163,11 @@ esac</userinput></screen>
is known to fail in the LFS chroot environment.</para> is known to fail in the LFS chroot environment.</para>
</listitem> </listitem>
<listitem>
<para>Three <emphasis>nptl/tst-thread-affinity*</emphasis>
tests are known to fail.</para>
</listitem>
<!-- Did not fail with glibc-2.38 <!-- Did not fail with glibc-2.38
<listitem> <listitem>
<para><emphasis>misc/tst-ttyname</emphasis> <para><emphasis>misc/tst-ttyname</emphasis>

View File

@ -74,6 +74,8 @@
<screen><userinput remap="test">make check</userinput></screen> <screen><userinput remap="test">make check</userinput></screen>
<para>One test in the "ps" tests is known to fail.</para>
<para>Install the package:</para> <para>Install the package:</para>
<screen><userinput remap="install">make install</userinput></screen> <screen><userinput remap="install">make install</userinput></screen>