| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE section [
|
|---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 4 | %general-entities;
|
|---|
| 5 | ]>
|
|---|
| 6 | <section xmlns="http://docbook.org/docbook-ng"
|
|---|
| 7 | xmlns:xlink="http://www.w3.org/1999/xlink"
|
|---|
| 8 | xml:id="prepare-abouttestsuites">
|
|---|
| 9 | <title>About the test suites</title>
|
|---|
| 10 | <?dbhtml filename="abouttestsuites.html"?>
|
|---|
| 11 |
|
|---|
| 12 | <para>Most packages provide a test suite. Running the test suite for a newly
|
|---|
| 13 | built package is generally a good idea, as it can provide a nice sanity check
|
|---|
| 14 | that everything compiled correctly. A test suite that passes its set of checks
|
|---|
| 15 | usually proves that the package is functioning as the developer intended. It
|
|---|
| 16 | does not, however, guarantee that the package is totally bug free.</para>
|
|---|
| 17 |
|
|---|
| 18 | <para>Some test suites are more important than others. For example, the test
|
|---|
| 19 | suites for the core toolchain packages -- GCC, Binutils, and Glibc -- are of
|
|---|
| 20 | the utmost importance due to their central role in a properly functioning
|
|---|
| 21 | system. But be warned, the test suites for GCC and Glibc can take a very long
|
|---|
| 22 | time to complete, especially on slower hardware.</para>
|
|---|
| 23 |
|
|---|
| 24 | <note><para>Experience has shown us that there is little to be gained from running
|
|---|
| 25 | the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no
|
|---|
| 26 | escaping the fact that the host system always exerts some influence on the
|
|---|
| 27 | tests in that chapter, often causing weird and inexplicable failures. Not only
|
|---|
| 28 | that, the tools built in <xref linkend="chapter-temporary-tools"/> are
|
|---|
| 29 | temporary and eventually discarded. For the average reader of this book we
|
|---|
| 30 | recommend <emphasis>not</emphasis> to run the test suites in
|
|---|
| 31 | <xref linkend="chapter-temporary-tools"/>. The instructions for running those test
|
|---|
| 32 | suites are still provided for the benefit of testers and developers, but they
|
|---|
| 33 | are strictly optional for everyone else.</para></note>
|
|---|
| 34 |
|
|---|
| 35 | <para>A common problem when running the test suites for Binutils and GCC is
|
|---|
| 36 | running out of pseudo terminals (PTYs for short). The symptom is a very high
|
|---|
| 37 | number of failing tests. This can happen for several reasons, but the most
|
|---|
| 38 | likely cause is that the host system doesn't have the
|
|---|
| 39 | <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
|
|---|
| 40 | more detail later on in <xref linkend="chapter-temporary-tools"/>.</para>
|
|---|
| 41 |
|
|---|
| 42 | <para>Sometimes package test suites will give false failures. You can
|
|---|
| 43 | consult the LFS Wiki at <link xlink:href="&wiki-root;"/> to verify that these
|
|---|
| 44 | failures are normal. This applies to all tests throughout the book.</para>
|
|---|
| 45 |
|
|---|
| 46 | </section>
|
|---|
