| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="ch-preps-abouttestsuites">
|
|---|
| 9 | <?dbhtml filename="abouttestsuites.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <title>About the Test Suites</title>
|
|---|
| 12 |
|
|---|
| 13 | <para>Most packages provide a test suite. Running the test suite for a
|
|---|
| 14 | newly built package is a good idea because it can provide a <quote>sanity
|
|---|
| 15 | check</quote> indicating that everything compiled correctly. A test suite
|
|---|
| 16 | that passes its set of checks usually proves that the package is
|
|---|
| 17 | functioning as the developer intended. It does not, however, guarantee
|
|---|
| 18 | that the package is totally bug free.</para>
|
|---|
| 19 |
|
|---|
| 20 | <para>Some test suites are more important than others. For example,
|
|---|
| 21 | 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 | take a very long time to complete, especially on slower hardware, but
|
|---|
| 25 | are strongly recommended.</para>
|
|---|
| 26 |
|
|---|
| 27 | <note>
|
|---|
| 28 | <para>Running the test suites in <xref linkend="chapter-cross-tools"/>
|
|---|
| 29 | and <xref linkend="chapter-temporary-tools"/>
|
|---|
| 30 | is pointless; since the test programs are compiled with a cross-compiler,
|
|---|
| 31 | they probably can't run on the build host.</para>
|
|---|
| 32 | </note>
|
|---|
| 33 |
|
|---|
| 34 | <para>A common issue with running the test suites for binutils and GCC
|
|---|
| 35 | is running out of pseudo terminals (PTYs). This can result in a large
|
|---|
| 36 | number of failing tests. This may happen for several reasons, but the
|
|---|
| 37 | most likely cause is that the host system does not have the
|
|---|
| 38 | <systemitem class="filesystem">devpts</systemitem> file system set up
|
|---|
| 39 | correctly. This issue is discussed in greater detail at
|
|---|
| 40 | <ulink url="&lfs-root;lfs/faq.html#no-ptys"/>.</para>
|
|---|
| 41 |
|
|---|
| 42 | <para>Sometimes package test suites will fail for reasons which the
|
|---|
| 43 | developers are aware of and have deemed non-critical. Consult the logs located
|
|---|
| 44 | at <ulink url="&test-results;"/> to verify whether or not these failures are
|
|---|
| 45 | expected. This site is valid for all test suites throughout this book.</para>
|
|---|
| 46 |
|
|---|
| 47 | </sect1>
|
|---|
