Changeset ee714d3 for chapter04/abouttestsuites.xml
- Timestamp:
- 06/09/2020 09:26:11 PM (4 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 79524a0
- Parents:
- b99b7d3
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/abouttestsuites.xml
rb99b7d3 ree714d3 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>Running the test suites in <xref linkend="chapter-temporary-tools"/> 28 <para>Running the test suites in <xref linkend="chapter-cross-tools"/> 29 and <xref linkend="chapter-temporary-tools"/> 29 30 is impossible, since the programs are compiled with a cross-compiler, 30 31 so are not supposed to be able to run on the build host.</para> 31 32 </note> 32 33 33 <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 34 35 is running out of pseudo terminals (PTYs). This can result in a high 35 36 number of failing tests. This may happen for several reasons, but the
Note:
See TracChangeset
for help on using the changeset viewer.