| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 4 | %general-entities;
|
|---|
| 5 | ]>
|
|---|
| 6 | <sect1 id="prepare-abouttestsuites">
|
|---|
| 7 | <title>About the Test Suites</title>
|
|---|
| 8 | <?dbhtml filename="abouttestsuites.html"?>
|
|---|
| 9 |
|
|---|
| 10 | <para>Most packages provide a test suite. Running the test suite for a
|
|---|
| 11 | newly built package is a good idea because it can provide a <quote>sanity
|
|---|
| 12 | check</quote> indicating that everything compiled correctly. A test suite
|
|---|
| 13 | that passes its set of checks usually proves that the package is
|
|---|
| 14 | functioning as the developer intended. It does not, however, guarantee
|
|---|
| 15 | that the package is totally bug free.</para>
|
|---|
| 16 |
|
|---|
| 17 | <para>Some test suites are more important than others. For example,
|
|---|
| 18 | the test suites for the core toolchain packages—GCC, Binutils, and
|
|---|
| 19 | Glibc—are of the utmost importance due to their central role in a
|
|---|
| 20 | properly functioning system. The test suites for GCC and Glibc can
|
|---|
| 21 | take a very long time to complete, especially on slower hardware, but
|
|---|
| 22 | are strongly recommended.</para>
|
|---|
| 23 |
|
|---|
| 24 | <note><para>Experience has shown that there is little to be gained
|
|---|
| 25 | from running the test suites in <xref
|
|---|
| 26 | linkend="chapter-temporary-tools"/>. There can be no escaping the fact
|
|---|
| 27 | that the host system always exerts some influence on the tests in that
|
|---|
| 28 | chapter, often causing inexplicable failures. Because the tools built
|
|---|
| 29 | in <xref linkend="chapter-temporary-tools"/> are temporary and
|
|---|
| 30 | eventually discarded, we do not recommend running the test suites in
|
|---|
| 31 | <xref linkend="chapter-temporary-tools"/> for the average reader. The
|
|---|
| 32 | instructions for running those test suites are provided for the
|
|---|
| 33 | benefit of testers and developers, but they are strictly
|
|---|
| 34 | optional.</para></note>
|
|---|
| 35 |
|
|---|
| 36 | <para>A common issue with running the test suites for Binutils and GCC
|
|---|
| 37 | is running out of pseudo terminals (PTYs). This can result in a high
|
|---|
| 38 | number of failing tests. This may happen for several reasons, but the
|
|---|
| 39 | most likely cause is that the host system does not have the
|
|---|
| 40 | <systemitem class="filesystem">devpts</systemitem> file system set up
|
|---|
| 41 | correctly. This issue is discussed in greater detail in <xref
|
|---|
| 42 | linkend="chapter-temporary-tools"/>.</para>
|
|---|
| 43 |
|
|---|
| 44 | <para>Sometimes package test suites will fail, but for reasons which the
|
|---|
| 45 | developers are aware of and have deemed non-critical. Consult the logs located
|
|---|
| 46 | at <ulink url="&test-results;"/> to verify whether or not these failures are
|
|---|
| 47 | expected. This site is valid for all tests throughout this book.</para>
|
|---|
| 48 |
|
|---|
| 49 | </sect1>
|
|---|
| 50 |
|
|---|
