Changeset c91dd5b for chapter02/abouttestsuites.xml
- Timestamp:
- 02/11/2004 10:02:10 PM (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, 12.2, 12.2-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_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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- a0b689e
- Parents:
- 5cd6caa
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/abouttestsuites.xml
r5cd6caa rc91dd5b 6 6 built package is generally a good idea, as it can provide a nice sanity check 7 7 that everything compiled correctly. A test suite that passes its set of checks 8 usually proves that the package is functioning mostly as the developer 9 intended. It does not, however, guarantee that the package is totally bug 10 free.</para> 8 usually proves that the package is functioning as the developer intended. It 9 does not, however, guarantee that the package is totally bug free.</para> 11 10 12 11 <para>Some test suites are more important than others. For example, the test 13 suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C14 library) -- are of the utmost importance due to their central role in a 15 properly functioning system. But be warned, the test suites for GCC and Glibc 16 can take a very longtime to complete, especially on slower hardware.</para>12 suites for the core toolchain packages -- GCC, Binutils, and Glibc -- are of 13 the utmost importance due to their central role in a properly functioning 14 system. But be warned, the test suites for GCC and Glibc can take a very long 15 time to complete, especially on slower hardware.</para> 17 16 18 <para>Experience has shown us that there is little to be gained from running 19 the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no escaping the 20 fact that the host system always exerts influence on the tests in that chapter, 21 often causing weird and inexplicable failures. Not only that, the tools built 22 in <xref linkend="chapter-temporary-tools"/> are temporary and eventually discarded. For the 23 average reader of this book we recommend <emphasis>not</emphasis> to run the 24 test suites in <xref linkend="chapter-temporary-tools"/>. The instructions for running those 25 test suites are still provided for the benefit of testers and developers, but 26 they are strictly optional for everyone else.</para> 17 <note><para>Experience has shown us that there is little to be gained from running 18 the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no 19 escaping the fact that the host system always exerts some influence on the 20 tests in that chapter, often causing weird and inexplicable failures. Not only 21 that, the tools built in <xref linkend="chapter-temporary-tools"/> are 22 temporary and eventually discarded. For the average reader of this book we 23 recommend <emphasis>not</emphasis> to run the test suites in <xref 24 linkend="chapter-temporary-tools"/>. The instructions for running those test 25 suites are still provided for the benefit of testers and developers, but they 26 are strictly optional for everyone else.</para></note> 27 27 28 <para>As you progress through the book and encounter the commands to run the 29 various test suites, we'll guide you on the relative importance of the test 30 suite in question, so that you can decide for yourself whether to run that one 31 or not.</para> 28 <para>A common problem when running the test suites for Binutils and GCC is 29 running out of pseudo terminals (PTYs for short). The symptom is a very high 30 number of failing tests. This can happen for several reasons, but the most 31 likely cause is that the host system doesn't have the 32 <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in 33 more detail later on in <xref linkend="chapter-temporary-tools"/>.</para> 32 34 33 <note><para>A common problem when running the test suites for Binutils and GCC 34 is running out of pseudo terminals (PTYs for short). The symptom is an 35 unusually high number of failing tests. This can happen for a number of 36 reasons. Most likely is that the host system doesn't have the 37 <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in 38 more detail later on in <xref linkend="chapter-temporary-tools"/>.</para></note> 35 <para>Sometimes package test suites will give false failures. You can 36 consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these 37 failures are normal. This applies to all tests throughout the book.</para> 39 38 40 39 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.