Changeset 37e35d2 for chapter04/abouttestsuites.xml
- Timestamp:
- 06/29/2020 07:55:01 AM (4 years ago)
- Branches:
- multilib-10.1
- Children:
- c4804e8
- Parents:
- d4fdde6
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/abouttestsuites.xml
rd4fdde6 r37e35d2 19 19 20 20 <para>Some test suites are more important than others. For example, 21 the test suites for the core toolchain packages—GCC, Binutils, and22 Glibc—are of the utmost importance due to their central role in a23 properly functioning system. The test suites for GCC and Glibc can21 the test suites for the core toolchain packages—GCC, binutils, and 22 glibc—are of the utmost importance due to their central role in a 23 properly functioning system. The test suites for GCC and glibc can 24 24 take a very long time to complete, especially on slower hardware, but 25 25 are strongly recommended.</para> 26 26 27 27 <note> 28 <para>Experience has shown that there is little to be gained from running 29 the test suites in <xref linkend="chapter-temporary-tools"/>. There can be 30 no escaping the fact that the host system always exerts some influence on 31 the tests in that chapter, often causing inexplicable failures. Because 32 the tools built in <xref linkend="chapter-temporary-tools"/> are temporary 33 and eventually discarded, we do not recommend running the test suites in 34 <xref linkend="chapter-temporary-tools"/> for the average reader. The 35 instructions for running those test suites are provided for the benefit of 36 testers and developers, but they are strictly optional.</para> 28 <para>Running the test suites in <xref linkend="chapter-cross-tools"/> 29 and <xref linkend="chapter-temporary-tools"/> 30 is impossible, since the programs are compiled with a cross-compiler, 31 so are not supposed to be able to run on the build host.</para> 37 32 </note> 38 33 39 <para>A common issue with running the test suites for Binutils and GCC34 <para>A common issue with running the test suites for binutils and GCC 40 35 is running out of pseudo terminals (PTYs). This can result in a high 41 36 number of failing tests. This may happen for several reasons, but the
Note:
See TracChangeset
for help on using the changeset viewer.