- Timestamp:
- 09/21/2003 07:10:45 AM (21 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, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 39dbad2
- Parents:
- 76d113f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/abouttestsuites.xml
r76d113f rebd8ee2 12 12 <para>Some test suites are more important than others. For example, the test 13 13 suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C 14 library) -- are of the utmost importance due to their central positioningin a14 library) -- are of the utmost importance due to their central role in a 15 15 properly functioning system. But be warned, the test suites for GCC and Glibc 16 16 can take a very long period of time to complete, especially on slower … … 22 22 run it or not.</para> 23 23 24 <note><para>A common problem when running the test suites for Binutils and GCC 25 is running out of pseudo terminals (PTYs for short). The symptom is an unusually 26 high number of failing tests. This can happen for any number of reasons. Most 27 likely is that the host system doesn't have the <emphasis>devpts</emphasis> file 28 system set up correctly. We'll discuss this in more detail later on in Chapter 29 5.</para></note> 30 24 31 </sect1> 25 32
Note:
See TracChangeset
for help on using the changeset viewer.